ITBOB Posted June 10, 2011 Posted June 10, 2011 Yesterday our Solus3 would install the agent on selected PC's without a problem. Today I have tried to deploy to another couple of PC's and the install just fails. The error I get is "access denied to the remote machine." The firewall settings are on the remote machine and I'm using an admin account to install. Nothing has changed since yesterday. Can anyone help?
round2it Posted June 10, 2011 Posted June 10, 2011 its the firewall our solus will not install if the firewall is on.
ITBOB Posted June 10, 2011 Author Posted June 10, 2011 Thanks. I have now managed to get it to install on a few machines (firewall enabled) however the rest just give an "Unable to get an ipv4 address for this agent" error.
matt40k Posted June 10, 2011 Posted June 10, 2011 Stupid question, can you get an IP for the client if you ping it? Does it give you back two IP's perhaps?
EmperorPeng Posted January 31, 2013 Posted January 31, 2013 (edited) Came across this thread and had a thought about it - apologies for bumping such an old post. The ip4 issue seems to be when DNS contains multiple entries for a host; probably due to having LAN and WLAN configured and active at the same time. Log on to your DNS servers and scavenge stale records, do a ipconfig /flushdns on your Solus3 server and also an ipconfig /registerdns on the machine with the ipv4 issue. You could also reboot here but I'm not sure it makes a difference. Finally delete the machine from Solus3 and then re-add it. It should now be able to reach the machine. Edited January 31, 2013 by JPShields 1
Rawns Posted January 31, 2013 Posted January 31, 2013 Came across this thread and had a thought about it - apologies for bumping such an old post. The ip4 issue seems to be when DNS contains multiple entries for a host; probably due to having LAN and WLAN configured and active at the same time. Log on to your DNS servers and scavenge stale records, do a ipconfig /flushdns on your Solus3 server and also an ipconfig /registerdns on the machine with the ipv4 issue. You could also reboot here but I'm not sure it makes a difference. Finally delete the machine from Solus3 and then re-add it. It should now be able to reach the machine. We've come across this a fair old bit too, and can confirm this is good information.
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