tortured Posted July 23, 2003 Report Share Posted July 23, 2003 With AOL USB DSL modem connected to backup host, can't see clients. Disable AOL adapter in device manager, can see clients. With Retrospect still open, can re-enable AOL adapter and will continue to see clients as long as Retrospect stays open. If it's closed and reopened with AOL adapter enabled, can't see clients. Have read in KB about binding Client to specific adapter where client PC has multiple adapters. This is not that issue. Retro Pro 6.0. Windows XP Pro. Link to comment Share on other sites More sharing options...
natew Posted July 23, 2003 Report Share Posted July 23, 2003 Hi There Are there any firewall rules that take effect when you enable the AOL adapter? It could be that port 497 (the port Retrospect uses for contacting clients) is handled differently once you enable the AOL adapter. Clients that were contacted before you conect the adapter would be unaffected as the connection was established before the rules for port 497 changed. For the record - Retrospect uses multicast on port 497 to contact clients. UDP and TCP traffic must be allowed for this to work. Nate Link to comment Share on other sites More sharing options...
tortured Posted July 23, 2003 Author Report Share Posted July 23, 2003 Thanks for speedy reply. Sad to say no firewall yet. Single user ordered and set up AOL DSL himself, adding it to an otherwise functional setup which had previously used dialup. "Modem" goes straight to the wall jack. Link to comment Share on other sites More sharing options...
natew Posted July 24, 2003 Report Share Posted July 24, 2003 Did you have to install anyting on your computer to get the AOL connection to work? I have a feeling that they include a firewall of some type. What is more likely is that the AOL connection is assigning an IP address that is in another subnet than your other computers. Its hard to day without digging through AOLs setup... Nate Link to comment Share on other sites More sharing options...
AmyJ Posted July 24, 2003 Report Share Posted July 24, 2003 Retrospect will look for clients through the "default" network adapter, which is determined by Windows. You may be able to go into the advanced properties for your adapters to change the order, allowing the default adapter to become the NIC. Only the Single Server and Multi Server editions of the Retrospect application allow configuration of multiple adapters. Link to comment Share on other sites More sharing options...
tortured Posted July 27, 2003 Author Report Share Posted July 27, 2003 There is definitely an "adapter" indicated in device manager. And I do know that AOL does assign IP addresses to these, because firewall logs (from other sites I manage) are full of spoof messages when users load the app, consistently on a 172 block. Link to comment Share on other sites More sharing options...
tortured Posted July 27, 2003 Author Report Share Posted July 27, 2003 Should I infer that if there is no advanced setting allowing for designation of a primary NIC that this is not resolvable? There seems no practical way to get rid of the AOL adapter entry in Device Manager. We did try a Linksys router which claimed to be able to treat AOL as a type of PPPoE, but could not get that feature to work despite considerable time spent with tech. That would have let everything go NAT through the built-in NIC -- but no dice. The best plan would be to dump AOL, but the client does not believe that plain, simple old AOL could be at fault here, now that I've talked him into backing up. Link to comment Share on other sites More sharing options...
Mayoff Posted July 27, 2003 Report Share Posted July 27, 2003 In the advanced settings for TCP/IP (not part of the device manager) you will find an option to change the order of the TCP/IP bindings. The AOL adapter needs to be moved to the bottom of the list. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.