mavraam Posted January 28, 2005 Report Share Posted January 28, 2005 OK, here's the scenario. 1) Installed Retrospect on my main computer. Win XP Pro SP-2. 2) Installed RClient on old computer. Win XP Pro - pre SP-2. 3) I have a router / wireless hub in the room with the main computer. It is connected by cable. 4) Old computer is also connected to the hub by cable, for the moment. 5) Retrospect finds client without a problem and I do a backup without a hitch. 6) Disconnect cable from network to old computer and install wireless NIC on old computer. 7) Old computer connects fine, I can see old computer from main computer via explorer, access shared directories, etc. 8) Try backup of old computer, it fails, Retrospect can no longer see old computer. 9) Assuming old computer may have been assigned different IP when I switched to wireless, I tell Retrospect to 'forget' Client and then search for clients again hoping it will 'rediscover' my old computer with new network settings. 10) Retrospect does not find Client. 11) Tried turning off firewall, still no client. 12) Checked that client is running on old computer, it is running and says it is ready. Any ideas why I can suddenly not find client? The main computer's connection to the router has not changed, the only change is going from cable to wireless on the old (client) computer. I know about the SP-2 issues and firewalls but I have turned the firewall off and it still can not find the client. Also, could this be related to the issue I'm having with Retrospect hanging for 15-20 minutes whenever I shut it down? It had jobs scheduled with the client computer and I was thinking that since it tries to validate upcoming jobs before shutdown it might be trying to find the old computer and that's why I just get an hourglass form 15-20 minutes before it finally exits. Any help would be greatly appreciated! Link to comment Share on other sites More sharing options...
natew Posted February 10, 2005 Report Share Posted February 10, 2005 Hi If you are using Retrospect professional the client and the Retrospect application must be in the same IP subnet. Is your wireless connection using a different IP address range? You can bind Retrospect client to the IP address of your wireless adapter with the retroclient -ip command line option. Thanks Nate Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.