MIS Systems Thread, Solus 3 will no longer install agent in Technical; Yesterday our Solus3 would install the agent on selected PC's without a problem. Today I have tried to deploy to ...
-
10th June 2011, 03:00 PM #1
- Rep Power
- 0
Solus 3 will no longer install agent
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?
-
-
IDG Tech News
-
10th June 2011, 03:03 PM #2 its the firewall our solus will not install if the firewall is on.
-
-
10th June 2011, 03:29 PM #3
- Rep Power
- 0
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.
-
-
10th June 2011, 08:23 PM #4 Stupid question, can you get an IP for the client if you ping it? Does it give you back two IP's perhaps?
-
-
31st January 2013, 09:32 AM #5
- Rep Power
- 2
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.
Last edited by JPShields; 31st January 2013 at 09:40 AM.
-
Thanks to JPShields from:
Rawns (31st January 2013)
-
31st January 2013, 09:47 AM #6 
Originally Posted by
JPShields
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.
-
SHARE: 
Similar Threads
-
By stevenewman in forum General Chat
Replies: 8
Last Post: 24th February 2010, 08:44 AM
-
By dgrams in forum Windows Server 2008
Replies: 4
Last Post: 3rd February 2010, 08:33 AM
-
By cookie_monster in forum Thin Client and Virtual Machines
Replies: 0
Last Post: 11th January 2010, 07:00 PM
-
By maniac in forum Hardware
Replies: 1
Last Post: 21st September 2009, 09:18 PM
-
By LCPSWolf in forum Coding
Replies: 11
Last Post: 7th August 2009, 02:37 PM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules