TERRYRICKETTS Posted June 12, 2013 Report Share Posted June 12, 2013 We are running version 8.1 multiserver. Some users have recently upgraded to Windows 8. After installing the Windows client version 8.1 the server cannot see the client on the machine. I have had them turn off their firewall temporarily to see if that is what is blocking access, but their client still cannot be seen. The error message says 'Can't access a client at "xxxx", error -530 (backup client not found)'. Any ideas on how to solve this? Quote Link to comment Share on other sites More sharing options...
rsleegers Posted June 13, 2013 Report Share Posted June 13, 2013 I find if substantial information has changed (hard drive, computer) but the name is the same, you have to update the client name, as it's still pointing to a unique internal id. Configure, Clients, (select client), Properties, Access tab, Change, choose the same name, and accept/save all your changes. Quote Link to comment Share on other sites More sharing options...
TERRYRICKETTS Posted June 13, 2013 Author Report Share Posted June 13, 2013 We tried some experiments to try to locate the problem. 1. Put both client and server on same subnet Result: could not see client 2. Turned off firewall in client Result: could not see client 3. Ran port scan on client from server Result: port 497 not open (even with firewall off) 4. Reverted to version 7.7 client Result: client can now be seen 5. Ran port scan on client with old version Result: port 497 is open 6. Turned firewall back on Result: client can still be seen, and port 497 is open 7. Allowed client to use DHCP Result: Client can still be seen There is something happening in the Retrospect Client version 8.0 and 8.1 that on some machines will not respond to the server, and will show port 497 closed to port scanners. On other machines it will work just fine. This has been happening with Win 7 and Win 8 PCs (all of our PCs are from Dell). I have no idea why switching to Version 7.7 made it work. Note that we were adding a new machine to the network, not changing a client on an existing machine. In testing I always used the 'advanced' button and selected 'Direct'. Then I enter the ip address and click on 'Test' to see if a client can be seen on the machine. Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted June 14, 2013 Report Share Posted June 14, 2013 You're not running Symantec or another AV tool which has an inbuilt network protection feature are you? Richard Quote Link to comment Share on other sites More sharing options...
TERRYRICKETTS Posted June 14, 2013 Author Report Share Posted June 14, 2013 We are running Symantec Endpoint Protection. There are over 600 workstations at our location. About 98% of them connect without any difficulty. Some of them simply refuse, and the ports in the firewall appear to be closed even though the firewall says they are open. Quote Link to comment Share on other sites More sharing options...
dan.jordan Posted June 18, 2013 Report Share Posted June 18, 2013 Here are my conclusions when I faced similar trouble: - 8.1 agent won't co-exist with 8.0 agent- You may need to reboot after uninstalling client 8.0 and before installing 8.1- Don't be too quick after adding 8.1 to add the client in Retrospect or you may be fooled into thinking it can't communicate. Try a few times.- when you try to add the client in Retrospect you may need to first exist the Clients dialogue completely and then go back into it. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.