MyBrainHurts Posted March 13, 2012 Posted March 13, 2012 Afternoon all! I've been experiencing some issues with rolling out the SOLUS 3 agent to workstations, in that out of 150 computers, the client has only installed itself on 6! The original error message we received was along the lines of 'Unable to get an IPv4 address for this agent', however the latest SOLUS 3 update was supposed to fix this. It has, to a degree, but now we're receiving the error message 'Unable to get an IP address for this agent' Has anyone else seen similar? So far I've tried installing it on computers in groups of 2, 10, and 50 to see if large deployment sizes were an issue. I've tried switching off Windows Firewall, just in case this was interfering with the install process. I've also tried installing to computers with dynamic and static IP addresses, but the same message appears. I have also pinged the name of a computer from the SIMS server and it's returning with the correct IP address of the machine. It's really odd ... I have a few test computers beside me, all running XP SP3 and fully updated, with the latest version of SIMS and Windows Firewall switched off. Yet still the SOLUS 3 deployment environment will not roll the update out to these computers due to the above error message. Just a random thought whilst typing this ... Sophos Anti-Virus wouldn't prevent the install, would it? Might just give that a try Cheers! Chris
matt40k Posted March 13, 2012 Posted March 13, 2012 It's most like the workstation aren't using the domains dns servers, so they aren't registering the fully qualified dns name - ie workstation1.school.local, you may be able to ping \ connect to workstation1, but you can't ping workstation1.school.local In short, it's a DNS problem. 1
MyBrainHurts Posted March 14, 2012 Author Posted March 14, 2012 Sorted it! DNS was the issue ... Cheers!
PrimaryTech Posted September 11, 2013 Posted September 11, 2013 Sorted it! DNS was the issue ... Cheers! Could you tell me what the DNS issue was? I'm having the exact same issue, SOLUS 3 not deploying to some agents with matt40k's diagnosis that I can ping COMPUTERNAME but I can't ping COMPUTERNAME.SCHOOL.LOCAL.
matt40k Posted September 11, 2013 Posted September 11, 2013 Check the workstations IP settings, I'm guess it's got your LA's DNS servers rather then your local DNS servers.
burnsyb0y Posted January 9, 2015 Posted January 9, 2015 How did you fix this issue? I am having the same problem currently.
Boredguy Posted January 9, 2015 Posted January 9, 2015 I normally check the DNS to see if there is more than one entry for the offending workstation, then once that is sorted, on the SIMS server run ipconfig /flushdns 9 times out of 10 Solus then happily talks to the client and carrys on as normal. 2
RArtes Posted December 13, 2018 Posted December 13, 2018 Reverse DNS was the issue for me. As soon as we added the entries to the Reverse Lookup Zone in DNS, then it started working.
mburland Posted February 27 Posted February 27 (edited) This is what I love/hate about SIMS - when I have a problem with it, there's probably a thread about it on EduGeek from the dial-up era. In my particular case, the problem was my computer name was 16 characters, therefore the DNS record didn't match the NETBIOS name, which of course SOLUS3 uses because it is from the 90's at heart. Edited February 27 by mburland 1
Jawloms Posted February 27 Posted February 27 Whenever I had this problem, I added the host name and its IP to the local hosts file of the server, did the install and then removed it again. We moved away from SIMS last week though! Woohoo! \o/
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