|
Question : can not find time server
|
|
Hi,
I can not log onto any of the workstations in a domain from the Server but the workstations can all log onto the Server.
The error log has the following:
The kerberos client received a KRB_AP_ERR_TKT_NYV error from the server LYMPHNODE$. This indicates that the ticket used against that server is not yet valid (in relationship to that server time). Contact your system administrator to make sure the client and server times are in sync, and that the KDC in realm WIMBERLEYEMS.LOCAL is in sync with the KDC in the client realm.
I went to one of the workstations and typed in: Net time /setsntp:/192.168.x.xxx - thats OK Net time /set can not find time server
On the server I did the following: Net time \\192.168.x.xxx /set/yes
For some reason the clients just do not find the DC as the time server. This is for my local EMS so its important.
Thanks Lee
|
Answer : can not find time server
|
|
Mmmmmm... Lots-o-fun :-)
I think you are going to have no choice but to remove and re-join the workstation. Something seems to have become corrupted with the computer account. The fact that it boots up quickly when disconnected from the network, and the possibility that the proper account does not exist in active directory, would mean it is likely logging on using cached credentials when disconnected, and cannot properly authenticate when connected.
as for cleaning up \\ULNA try at a command line ping ULNA nbtstat -a ULNA and in DNS under your domain in forward look up zones as well as, Reverse Lookup zones, look for any ULNA host A records Some of the above may help to give you some clues as to whether it exists and if so where.
When it shows up in my network places is it within your domain, or another domain or workgroup? Could be a rogue machine that is not a member of your domain, and probably should not be connected.
|
|
|
|