Homeland Posted July 16, 2015 Posted July 16, 2015 Hey Guys, Has anyone seen this issue before and how did you get round it if you don't mine me asking, I have deployed the solus 3 agent to all the admin team and staff laptops this morning, 75% have worked fine with no issues the rest just seem to fail and say 'the remote machine cannot be contacted'. the firewall is switched off and anti-virus has been disabled I can ping the client and the client can ping the server the IP address is correct I can route to the workstation without needing additional credentials I have checked the log on the server and this is what it records. 2015-07-16 13:19:31.7709|Info|Executing command InstallAgent for computer name jpeck-lt.********.sch.uk net.tcp://IP address:52966/. 2015-07-16 13:19:31.8079|Info|jpeck-lt.********.sch.uk Looking for target OS 2015-07-16 13:19:31.8079|Info|Attempting to create ConnectionOptions with username='administrator' 2015-07-16 13:19:52.8700|Info|jpeck-lt.********.sch.uk Installation worker completed. I have even tried deploying the agent to a laptop that already has SIMS installed but still receive the same error, even a manual install of the agent doesn't resolve the issue. Really stumped but trying to sort it before I contact Capita.
Meldrew Posted July 16, 2015 Posted July 16, 2015 You could use a small command line utility called PCATTCP.exe to test the connection on the ports that SOLUS uses. Run the exe both ends with appropriate parameters and see if it can communicate. Also check DNS is resolving the PC name correctly, ie no stale DNS records for the PC name. Meldrew
glen_j Posted July 16, 2015 Posted July 16, 2015 Are you putting a username of domain\administrator or just administrator in the user box? If the latter it probably cant authenticate.
Homeland Posted July 17, 2015 Author Posted July 17, 2015 No using domain\administrator account, I have found if I manually install SIMS on the laptop then do the manual agent it will then work but surley that defeats the object of solus 3
neilenormal Posted July 17, 2015 Posted July 17, 2015 Check permissions on this folder \ProgramData\Microsoft\Crypto\RSA\MachineKeys It needs to create a file beginning "1d..." here and if it can't then it fails.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now