Domain Problems Revisited

  recap 10:53 23 May 05
Locked

Please see my previous posting here click here for the full sp.

After setting the system clocks by doing a net time command /setsntp:

All client machines were able to connect to the domain and have all network resources. That was at the time of the above posting.

Now for some reason no client machine can connect to the DC.

nslookup connects to the IP server but not to the DC.

Ping testing from a client is successful for the Internet server but not the DC, for both Admin and under a user account.

Ping testing from the DC is successful for both client and Internet server.

When a user tries to login, the error message tells them that the Domain is not available.

I have ran the fixes that Microsoft suggest click here;en-us;q216734 with the same results.

Has anybody any further suggestions that I can try as I am now stumped as to what is causing this?

  recap 12:02 25 May 05

I have been able to track the problem down to the integration of the Windows 2003 server and out ISP Server.

The ISP is writing a new program to allow a smooth inegration.

This thread is now locked and can not be replied to.

How to get Windows 10 for free | How to install Windows 10: There is still a way to avoid paying…

1995-2015: How technology has changed the world in 20 years

Alex Chinneck’s giant ice cube Christmas tree at Kings Cross

Apple rumours & predictions 2017: The iPhone 8, new iPads, and everything else you should expect fr7…