Backing up over Airport

[GJJ]

I am using Retrospect for Workgroups under MacOS X 10.2. It works fine with backing up the same computer or a Windows (2000) client. However, when trying to backup a PowerBook MacOS X 10.2 client I can't connect to this computer. I can see the client but cannot Login (Configure:Clients).

 

 

 

Is there a special technique, because I tried updating everything.

 

 

 

Thanx,

 

 

 

Gert-Jan Jonker

[AmyJ]

What happens when you try to log the client in? What errors?

 

 

 

If you're getting an error 541, make sure you either disable the firewall in 10.2 or enable Retrospect access within the firewall.

 

 

 

System Preferences > Sharing > Firewall

[GJJ]

Sorry for not mentioning the error message. I'm getting 'Can't log in, erro -1028 (client is not visible on network).

 

 

 

However, I can select it in the panel Backup Clients on Network. There it just says 'Not Logged in'

 

 

 

Best wishes,

 

 

 

Gert-Jan Jonker

[AmyJ]

What happens if you try to Ping the client computer through Applications:Utilities:Network Utility? Do you get a response?

 

 

 

The following article may also help:

 

 

 

People often want to use Retrospect with wireless networking. Fortunately, in many configurations this is fully supported. In some configurations, however, Retrospect cannot access client computers that are connected to the network via a wireless interface.

 

 

 

The quick answer is that if your wireless users either have fixed non-shared IP address or get their IP addresses from a DHCP server on your non-wireless LAN, then Retrospect will work seamlessly with your wireless clients. In other words, wireless networking is just like other hard-wired networking, if you have a non-shared IP address and can access all normal network functions.

 

 

 

If you are using network address translation (usually called NAT) on your wireless client computers, Retrospect will not be able to back them up using Retrospect client software by default. There is a way to get Retrospect to access a single client per IP address if wireless clients are sharing an IP address by configuration only one of the clients using port mapping. For Macintosh users this workaround is described below for Macintosh Airport networking. The process will be quite similar with any other wireless networking software, Macintosh or Windows.

 

 

 

Instructions for enabling a single Macintosh client's use of Retrospect Client software in a NAT (shared IP address) environment:

 

 

 

1. Pick the client for which you want to enable wireless networking access using the Retrospect Client software.

 

2. On the client machine (that is, the computer with the wireless networking connection) look at the TCP/IP address assigned to the system.

 

3. Start the Airport Admin Utility, select the Airport module and click Configure.

 

4. Select the Network tab and then click the Port Mapping button. Some Airport base station models have a separate Port Mapping tab for this function.

 

5. Click Add, and fill in the following information:

 

Public Port: 497

 

Private IP Address: Enter the address from step 1 above

 

Private Port: 497

 

6. Click OK and then Done to get back to the Update tab. Click Update to force the Airport module to reconfigure itself. Quit the Admin program.

 

7. In Retrospect on the backup computer, add this computer using Add by Address, using the address noted in step 1. Retrospect will now be able to access the one client you configured, even though that IP address is shared among multiple wireless computers.

 

 

 

Remember: this workaround can only be done for one computer on the NAT.

 

 

 

Another simple workaround is to have a backup machine for all of the computers on the NAT that also gets its IP address from the NAT. This backup computer can get an IP address wirelessly, or the Wireless Access Point can distribute IP addresses on the LAN as well. If the backup computer is also using NAT addressing within the same wireless group, it can back up more than one client on that NAT.