Jump to content

Retro 6.5 Win can't see Mac OS9 client


srunkel1

Recommended Posts

Just installed Retrospect Professional 6.5 on Windows XP, and client 5.1.157 on Mac OS 9.1. Client is running fine. When I try to add client in Retrospect on the Win machine, it just says "searching for backup clients..." forever. However, if I click "Test..." and enter the IP address of the client G4 machine, it immediately says "Found a backup client" and gives the specs. But -- and this blows me away -- it STILL doesn't really find it, and OKing the "found" window puts it back to searching forever.

 

As an additional note, the two computers are networked together via a DSL router. There is NO additional networking software running on the network, and the two computers CANNOT see each other via Chooser or Network Neighborhood.

 

Thoughts?

 

Link to comment
Share on other sites

Hi

 

First the basics

Make sure you can ping the mac from your PC and that they are on the same subnet.

 

Chances are the built in firewall for XP is blocking port 497. Port 497 must be open to UDP and TCP on both machines in order for the client to work.

 

Nate

Link to comment
Share on other sites

Thanks!

 

 

 

I opened 497 for UDP and TCP on my WinXP machine. But still nothing in Retrospect when it searches for clients (although, as before, it can still see the client if I enter the IP address. I have to say, this feels like a bug to me). And I can ping the Mac from the PC. Now I'm looking into what exactly a subnet is. Unfortunately, there are people (like me) who need to back up 2 computers but aren't network people by experience or training.

 

 

 

Anyway, according to Retrospect's own help, "A subnet is a group of local computers physically networked together without a router or gateway, though they may use a gateway to connect to other networks." My computers are connected via a router/gateway. Doesn't everyone use a router/gateway these days? It's an ActionTec DSL Gateway that I have to use for my DSL to work. So I guess they aren't on the same subnet. The question then becomes: how can I get it to work, knowing this?

 

-Scott

Link to comment
Share on other sites

Hi

 

I know this is frustrating but I can guarantee you it is not a bug. Subnets refer to the IP address ranges you are using. You can have two machines on the same hub that are on completely different subnets.

 

What is happening in your case is either the XP machine or your router is not properly allowing multicast data packets to move across the network. The test command works because it does not require multicast.

 

What IP addresses are you using on these machines? does the Router have any settings that you can work with? Do you use a VPN client?

 

Thanks

Nate

Link to comment
Share on other sites

Good info. It's starting to make sense. The router has address 192.168.0.1. The WinXP machine where Retrospect is running has address 192.168.0.109. The subnet mask is 255.255.255.0. The Mac OS 9 machine with the Client is 192.168.0.200.

 

 

 

The router has various settings that I can fiddle with. I can change its LAN IP address; set it as a DHCP server (currently OFF); block services; block websites; allow VPN pass through (IPSec/L2TP) which is currently OFF, it also says "PPTP pass through for use with PPTP Virtual Private Networks is always on by default.)"; remote management, which is OFF; port forwarding, which has nothing set up (although I had set this up and will try again); DMZ hosting, currently OFF; MAC Address cloning, which has 00.20.e0.35.85.4a; NAT, which is ON; and Static Routing, which is set x.x.x.x(our static IP)/255.255.255.0.x.x.x.x (another IP).

 

 

 

I don't use a VPN client, at least not that I know of.

 

 

 

I get the feeling with all these options that you might be able to suggest something. Thanks for your help!

Link to comment
Share on other sites

Quote:

Scott Runkel said:
Good info. It's starting to make sense. The router has address 192.168.0.1. The WinXP machine where Retrospect is running has address 192.168.0.109. The subnet mask is 255.255.255.0. The Mac OS 9 machine with the Client is 192.168.0.200.

 


OK, they are on the same subnet. (If you AND the mask with the addresses, the result is the same in both cases.)

Quote:

The router has various settings that I can fiddle with. I can change its LAN IP address; set it as a DHCP server (currently OFF)

 


Any reason you are not using DHCP? Shouldn't make any difference in this case, but not using DHCP means that you have to keep track of the IP addresses of all the systems on your LAN. And I suppose there's a possibility that the router might block broadcase to fixed IP addresses.

 

The rest of the options you list deal with communicating with the outside world and should not affect the LAN.

 

natew's suggestion was that the router may be blocking broadcast packets. One way to check this would be to connect the two systems directly via a crossover 10BaseT cable, bypassing the router. (But you must get a crossover cable; a regular 10BT cable will not work.) Or get a cheap hub, which is definitely a dumb pass-through device and will not block anuthing. Connect the two systems to the hub and the hub to the router. (The latter may require a crossover cable, or may not. RTFM carefully.)

 

I'll be a little surprised if this is the problem, as the multiple ports on a DSL router usually are just a simple hub built in to the DSL device. What is the make and model of the DSL router?

 

Edward

 

Link to comment
Share on other sites

We're not using DHCP because I kinda like knowing the IP addresses of the machines. Also, because I create software with Director on my PC, and some of the networking Director has requires static IPs. And we only have 2 machines on the network (sometimes another 2 for 4 total).

 

As part of my testing to find out why Retrospect isn't finding the client, I'll try switching to DHCP temporarily and seeing if that helps. If DHCP solves the problem, I can keep the network that way except when testing with Director.

 

I will get a crossover cable and try that test as well. I was considering it, it seemed like a pain, but now it seems pretty necessary in the process of elimination. My suspicion is it will work. I like the cheap dumb hub idea; that had occurred to me as well. We have an older DSL router but I think it will interfere. So may have to buy a cheap hub.

 

The DSL router is an ActionTec R1520SU, Wireless-Ready DSL Gateway. Comes from Qwest, but despite that fact it seems to work well.

 

Thanks again to both you guys for the help so far.

Link to comment
Share on other sites

  • 4 weeks later...

Well, a call to Retrospect tech support solved the problem. It was as simple as -- turning off the Windows XP firewall. Hard to believe I didn't try this before. Impossible to believe, actually. Anyway, I did the crossover cable direct from machine to machine first, and that worked (once the XP firewall was off). Then went back to the router and still working. Tried turning on the firewall, with port 497 open for TCP and UDP etc., but it never worked. No loss; I have other firewall stuff going.

 

Thanks people for your help!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...