Win2k server - "The system cannot log you on now..."

  • Thread starter Thread starter Boss Hog
  • Start date Start date
B

Boss Hog

We have a Win2K server into which one Win2k client machine is unable to
logon.

What actually occurred was that the server software had to be re-built
after it crashed, and subsequently, we had to change all clients from
the domain logon to a workgroup and back to domain (for which we had
been advised to change change names - something to do with GUID? Someone
please explain?) after which the client machine now gets the message :

"The system cannot log you on now because the domain <name> is
unavailable"

Other client machines on the network are fine.

Our support folk mentioned "encryption" but failed to explain further,
and haven't yet resolved the issue.

Any ideas?
 
Try this

Enter the domain suffix on the client PC. eg. youdomain.com..
Also check that the client pc is using the correct DNS server for that domain.
Do a nslookup( in cmd.exe type "nslookup yourdomain.com" ) for your domain
on the client pc, when you get the right response from nslookup( your DNS
server) try and join that client to the domain.

Also try and flush/register the DNS on that client pc.
(in cmd.exe type " ipconfig /flushdns" & ipconfig /registerdns")

Hope this help...

Regards
Ants
 
Try this

Enter the domain suffix on the client PC. eg. youdomain.com..
Click to expand...

The domain name is simply "CENTRE" (no quotes) and is only suffixed by
..local - it is a LAN, not WAN,if that is appropriate?
Also check that the client pc is using the correct DNS server for that domain.
Click to expand...

It is, so far as I can see.
Do a nslookup( in cmd.exe type "nslookup yourdomain.com" ) for your domain
on the client pc, when you get the right response from nslookup( your DNS
server) try and join that client to the domain.
Click to expand...

Yep, think we've been there, but I will try again.
Also try and flush/register the DNS on that client pc.
(in cmd.exe type " ipconfig /flushdns" & ipconfig /registerdns")
Click to expand...

OK, will give it a go.
Hope this help...
Click to expand...

I can but try.
 
Try this

Enter the domain suffix on the client PC. eg. youdomain.com..
Also check that the client pc is using the correct DNS server for that domain.
Do a nslookup( in cmd.exe type "nslookup yourdomain.com" ) for your domain
on the client pc, when you get the right response from nslookup( your DNS
server) try and join that client to the domain.

Also try and flush/register the DNS on that client pc.
(in cmd.exe type " ipconfig /flushdns" & ipconfig /registerdns")

Hope this help...
Click to expand...


Brilliant! I tried the above, and it seems to have worked.
I can't thank you enough, but, thank you!
 
Back
Top