Solus 3 - AD browse - Server is not operational

[stevenramsden]

Trying to browse active directory in Solus 3

Solus shows the correct domain and I can re-input domain admin credentials to try and reconnect the AD with Solus but just keeps giving me an error message "Error in computer selection - The server is not operational"

 

Had LA sims support team have a look and also capita support.

But capita won't help and suggest it's an issue with the server and not a solus3 problem (maybe it is?)

 

Had a look in the log file and it shows that Solus finds the domain

browses the domain for OU's

Finds 0 OU's

and then throws the error server not operational

 

This is small single server site, so Solus and all other SIMs components are on this single server which is also the domain controller.

Which hopefully simplifies troubleshooting.

No other AD related issues and I can't see anything obvious in happening in event viewer when it fails to connect up.

 

From what I can tell the AD computer selection has never worked previously, I have successfully deploy SIMS using the network selection section or I can search a computer name or IP and deploy sims via solus successfully.

Solus3 is working fine in the environment and communicating with the clients

 

I Just can't link Solus3 to AD to help with the deployment process

Any seen this and had it fixed.

[chazzy2501]

see if the the user your logged in as doesn't have the correct permissions or maybe is locked or has an out of date password.

[3s-gtech]

The old adage usually applies both for AD and SOLUS is the same - check for DNS issues! Time sync problems can also crop up, but DNS problems tend to make SOLUS bomb out.

[caffrey]

It's never worked here either since installation and never been fixed but it always finds the PC's via the computer selection \ network radio button. It could be to do with our domain name but I've never found it an issue

[stevenramsden]

Yes, Never worked since installed and similar to yourself I've always found PC's via computer/network selection,

Recently the network selection stopped working for a few weeks but seems to be back working.

 

Just would be nice to get the AD side working, thought logging with Capita support would help but they weren't interested in helping

[caffrey]

It's why I left it Do you have a single label domain name by chance ? We do which is what I've always put it down to.

[stevenramsden]

Yes it's a single label domain name, so that does like like the root of the issue.

Will look at new domain name setup when the server is ready for replacement in future.

 

Thanks for the help, saves me spending any more time digging