Jump to content

Retrospect Desktop 5 Configuration with Airport network


Recommended Posts

Does anyone have any experience with using Retrospect Desktop 5 over an Airport network? Retrospect will not "find" client machines over my Airport network, when I try to configure a network backup.

 

All three of my machines are running 10.2.4, Airport software is 3.0.1, have latest versions of Retrospect and client software. The network works pefectly, so Apple says it is not their problem. When using an Ethernet cable to connect the "server" machine directly to a client, Retrospect will see the client machine, no problem.

 

I have the port set properly (497) according to the support personel that I spoke with. (thanks guys & gal)

 

Still it won't see the client machines.

 

Surely someone out there is using Retrospect over an Airport network. How does one make it work?

 

Tim

Link to comment
Share on other sites

OK. Let's get down to business.

 

 

 

What are the correct settings for the Airport base station to make this work?

 

 

 

"Ethernet Bridging" is not specific enough. There are multiple scenarios that include "ethernet bridging" in my configuration panels.

 

 

 

Also, the article in the Knowledge Base you refer to (#27710) suggests a workaround that will only allow me to backup one machine over the wireless network. I have two.

 

 

 

The last paragraph of the article suggests another strategy, but I am not conversant enough in network protocols, to comprehend it.

 

 

 

Please help.

 

 

 

Tim

Link to comment
Share on other sites

Quote:

I am not conversant enough in network protocols, to comprehend it.

 


 

Since you want to configure this software to communicate over your network, you're going to have to get familliar enough with your current setup to describe it here (otherwise no one will be able to help).

 

Retrospect Desktop can only "find" computers on a single subnet. So you need to assure that the client machines are on the same subnet as the machine running Retrospect.

 

Check the Network preference pane (or the TCP/IP Control Panel if it's OS 9) of every machine. If the first three sets of numbers (xxx.xxx.xxx.---) are not the same, then Retrospect Desktop won't be able to see them.

 

As for specific settings and scenarios, you're going to have to provide more information about how your network looks now before anyone here is going to be able to suggest changes that might help. But in general, using your AirPort Base Station as a wireless bridge instead of a wireless router is what you want to do.

 

Dave

Link to comment
Share on other sites

Dave,

 

Thanks for the info.

 

Just got off the phone with an Airport expert at Apple.

 

We confirmed that the Airport Base station is functioning as an Ethernet bridge between the router box plugged into the DSL modem, and the machines on the network. Also, the subnet is the same for all machines.

 

That is, the Base station is passing through the IP numbers assigned by the router box to the individual machines. I have looked at each machine and confirmed that they are unique when the base station is configured this way. However Retrospect cannot find the client macines when I try to configure a backup over the network.

 

We also tried it with the Base station assigning it's own IP addresses. Again, each machine has a unique address. Retrospect was still unable to find the client machines.

 

Given this information, does anyone have any suggestions on how to set up Retrospect backups over an Airport wireless network?

 

thanks in advance,

 

Tim

Link to comment
Share on other sites

Quote:

Given this information, does anyone have any suggestions on how to set up Retrospect backups over an Airport wireless network?

 


 

How is the Network preference pane configured on your machines?

 

I'd suggest that for the wireless machines you have only the AirPort interface enabled, and for the wired machines have only the internal ethernet interface enabled. Use the "Network port configuration" selection under "show" to manage configurations.

 

Dave

Link to comment
Share on other sites

Success at last!

 

Many thanks to Nubz at Apple, and all of the patient folks over at Retrospect, (Eric, Amy, & Koorosh) who helped me figure this out.

 

Here is what made it work on my network:

 

Configure port 497 to be open on both server machine and client machines. Do this in Sharing > Firewall > New. Click on port 497 and apply changes. Check this by starting Network Utility > Port Search. The main machine will see port 497 in the clients, but not vice versa

 

In System Preferences > Network > Show > Network Port Configurations, Airport must be checked and at the top of the list. Built in Ethernet and Internal Modem must be UNCHECKED, or Retrospect won’t find the client machines. Select Airport to exit.

 

Also, in System Preferences > Network > TCP/IP > Configure > Using DHCP

Further, in System Preferences > Network > Apple Talk > uncheck AppleTalk.

 

Finally, using the Airport Administration Utility, Configure Base Station > Show All Settings > Network, make sure that the the Distribute IP Addresses box is unchecked.

 

Once again, kudos to the support community!

 

Tim

Link to comment
Share on other sites

  • 3 months later...
  • 1 month later...

Question:

 

In this setup, is there a separate hardware router in the configuration, or is it all Airport? In other words, is the Airport doing the routing, with all the clients configured with fixed addresses? If so, how is the private side of the Airport configured when Distribute IP addresses is turned off? If Airport is plugged into a hardware router, what are the respective configuration settings on Airport and the router?

 

My understanding of the KB article referenced elsewhere in this thread is you basically need an Airport (for bridging), a router (for the routing) and fixed IP addresses on the clients. Yet I'm having the devil's own time getting all three to work together at all, let alone showing the Retrospect client, which is the point of the entire exercise.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...