"Client Not Visible on Network"

[RogerC]

Using Retro 4.3 on a Mac with OS 9. Has been backing up successfully (for over a year) from another Mac running AppleShare 6.x on OS 9 using TCP/IP.

 

 

 

Began to see backup failures due to error 515 (Piton protocol violations) with various notes about bad file names. Restarting the client Mac cleared up everything -- the first time. The next time around, this method of restarting the client did not work -- except it was not immediately apparent since there were no error messages or reports of unsuccessful backups.

 

 

 

While doing unrelated tasks on the Retro Mac, I noticed that the 'problem' client was not getting backed up and that there was no error since there had been no attempt to do a backup -- the client appeared to be inactive, i.e. the client is listed in the client database, but the item is dimmed out. The problem client DOES NOT appear at all in the Clients on Network window! If you try to do a client configuration you get an error about the client not being visible on the network or 'Cannot connect with client.'

 

 

 

Client software is current version.

 

The client software IS loading and is turned 'on' and is in 'Ready' status.

 

TCP/IP is functioning on both machines.

 

Pinging both the client and the Retorspect Mac is successful.

 

No problems accessing the client from various other Macs on the network (via AppleShare IP)

 

Several other clients are being backed up with no problems at all.

 

 

 

What can we do to get this problem client back and backed up?

 

 

 

Thanks in advance for any suggestions for this Retrospect novice.

 

 

[IrenaS]

Is this an AppleTalk client or TCP/IP?

 

 

 

If it's a TCP/IP client, does it have a static address or a fixed address?

 

 

 

What is the error that you get when you try to connect (the error code)?

 

 

 

A little background on the 515 error: the piton protocol is a proprietary encapsulation scheme, designed to protect Retrospect's data packets as they travel over your network. Damaged encapsulation indicates to Retrospect that the data contained within is likely corrupted.

 

 

 

515 errors are almost always caused by a router that does incidental damage to the packet as it strips or adds headers and footers that allow the packet to travel from segment to segment along the network. It's not unheard of, however, for a bad router or bad networking equipment on a specific node to cause such problems.

 

 

 

A 515 error on one machine suggests problems with that node. Try replacing transceivers, patch cables and Ethernet cards, or changing the port into which that node is plugged on the hub.

 

 

 

If you manage to determine that the 515 only occurs with a PCI Macintosh, you should make sure you are running the most recent version of Open Transport. Also make sure that machine has the most updated Ethernet drivers for its card (either built-in or PCI).

 

 

 

Irena Solomon

 

Dantz Tech Support