10.2 "server" ignores 10.2 client

[dbutenhof]

I have three Macs at home:

 

 

 

1) "Server" G4 450Mhz with an Adaptec 2906 and an APS DDS-2 DAT, Retrospect 5.0.205 Desktop.

 

2) "Client" G4 2x1Ghz with the latest (10.2-compatible) Retrospect client. Mac OS X 10.2.

 

3) "Client" iMac (Mac OS 9.2.2)

 

 

 

All connected via Airport through a "snow" (dual ethernet) Airport Basestation. The "client" G4 has been running 10.2 (and the new Retrospect client) for over a week with no problem.

 

 

 

Over this past weekend I upgraded the "server" G4 to 10.2, despite some concern over unspecific reports of SCSI card problems. (I finally decided to just see for myself, doing a scratch install on an emptied partition.) Everything's working fine for local backups, and for the iMac client. However, it doesn't see the 10.2 client at all.

 

 

 

I've had this (or a similar) problem sporadically before, when the "server" G4 was running 10.1.5 -- but it always cleared up when I restarted it. (The server, that is, not the client.) Restarting (both or either) now makes no difference: it just doesn't see the 10.2 client. The iMac (9.2.2) continues to work just fine.

 

 

 

The obvious guess is that this might be another "10.2 induced problem" for Retrospect. Could that be? I haven't had much success finding troubleshooting hints in the FAQ or knowledge base.

[CallMeDave]

In reply to:

---

I haven't had much success finding troubleshooting hints in the FAQ or knowledge base.

---

 

I think it's going to take some more information for people to troubleshoot along with you for this one.

 

 

 

- Confirm that all three machines are on the same AirPort Base Station supplied subnet?

 

 

 

- Confirm that the Retrospect Application machine has only the AirPort network port active in the Network preference pane?

 

 

 

- Confirm you have Network Client licenses for Retrospect (since Desktop does not include any)?

 

 

 

- Confirm that you have not enabled the OS X firewall from the Sharing preference pane on either OS X 10.2 machine?

 

 

 

- Confirm you can ping the client in question?

 

 

 

Dave

[dbutenhof]

I think it's going to take some more information for people to troubleshoot along with you for this one.

 

 

 

 

- Confirm that all three machines are on the same AirPort Base Station supplied subnet?

 

- Confirm that the Retrospect Application machine has only the AirPort network port active in the Network preference pane?

 

- Confirm you have Network Client licenses for Retrospect (since Desktop does not include any)?

 

- Confirm that you have not enabled the OS X firewall from the Sharing preference pane on either OS X 10.2 machine?

 

- Confirm you can ping the client in question?

 

 

Oh, good: the forum markup includes the perfect "smiley" here:

 

 

 

Yes, to all of those questions. Except, uh, one. I assumed the one thing I knew had always been true, and was certainly true when I sporadically had the same problem under 10.1.5. (Making it easy to skip double-checking this time.)

 

 

 

I actually realized what I'd done shortly after I entered the post. But I'd written it in a moment of spare time at work, and couldn't check it out. I didn't see an obvious way to delete the post, and decided not to confuse matters by speculating further before I could check.

 

 

 

So... OK, the key is that I'd done a scratch install of 10.2 on the "server". So it "helpfully" created and activated both Ethernet and Airport ports. I've always deactivated all but Airport and put it first... but of course I forgot this time.

 

 

 

I fixed it up, and now Retrospect can see the client again. Too bad, in a way. I'd always shied from reporting the occasional connection problems I'd had before, since they weren't reproducible (and so easy to work around). Since this remained on restart, I thought maybe I could actually help someone track down the problem. It's gone back into the woodwork. (And there's always the chance it was an OS problem that's been fixed in 10.2 and I'll never see it again... )

 

 

 

Thanks for the response, and sorry for the stupid question. again...