Jump to content

Recommended Posts

Posted

A little bit late to the party as always!

 

Anyway, I've been forced into doing the Autumn SIMS update last night and came in this morning to mostly positive results so far...

 

A few workstations haven't done the update yet - from what I can see they were some of the first ones on the list that SOLUS 3 tried last night, so may have gone to the back of the queue (if that is indeed the way SOLUS works). So, just 1 issue so far...

 

- My work laptop is refusing to update and when I use the agent to check it says 'no DNS entries exist for host'...

 

There could be a reason for how this has happened...

 

Last night I was trying to get my work laptop to update SIMS over our VPN (and failing miserably) so I made some changes to various things, but I'm pretty sure I backed them all out when it didn't happen (I'm not entirely sure what I need to make this work). But this is when it started happening and it doesn't seem to have cleared now I'm back in school.

 

So where is SOLUS looking for when it says DNS entries (does it keep its own records or does it do a look up every time), how often does it look and how can I force it.

 

I have done ipconfig /flushdns. release, renew on the laptop and rebooted, checked the DNS entry for it exists on the server, everything else seems fine.

 

The SOLUS agent sees it as online and responds to 'status check' and 'get target version'...

Posted

The order matters. THe order your describe might result in the SOLUS picking up the old name/IP before the client has registered its new dns entry.

 

Delete any dns entry (forward and reverse) for your computer.

 

Replicated AD

 

On the client run ipconfig /registerdns

 

Check records have appeared on DNS Server and replicated.

 

*now* ipconfig /flushdns on the solus server.

 

Should work fine - though by this point sometimes you need to completely remove records from SOLUS and remove the client from the laptop and start again.

  • Thanks 1
Posted (edited)

In the end I just uninstalled the AGENT from the SOLUS GUI and then reinstalled it, re-adding it as a TARGET.

 

I guess that made SOLUS look at DNS again, with the AGENT now sending the correct details.

 

As soon as the AGENT was installed it started updating SIMS.

 

EDIT: I guess as I was mucking about trying to diagnose the issue with updating SIMS over the VPN it had been confused with the VPN IP address.

Edited by Koldov

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...