hidalgodlhs
asked on
Current time on computer and current time on network are different.
To access our company servers, I would remote-in (RDP) to the box and gain control from my work desktop. Our server is located a couple of hours away from the office and driving there would be my last option.
Anyway, I control three of our server, x.xxx.x.11 (domain-a virtual serverVM), x.xxx.x.12 (exchange-VM), (x.xxx.x.13- host box + backup device). When I try to remote logon to the .13 server I would get this message, "The current time on the computer and the current time on the network are different." The rest of the servers (.11 and .12) i am able to log in no problem. I even tried remoting to the the .13 from the .11 but no success. I checked the time using the command line net time \\x.xx.x.11 and net time \\x.xx.x.13 and found a difference of 5 minutes. Now i don't know how to remotely fix the differences.
I found a command line that would syncronize to gov and millitary standards but they did not change the differences ex. net time /setsnt:time.nist.gov then net time /setsntp:\\x.xxx.x.11 . but to no avail.
when i typed the following command line: net time /querysntp
I get My current SNTP value: NAS (which is the server i cannot connect to).
the functions are fine, i just need access to that particular server for maintenance purpose.
Anyway, I control three of our server, x.xxx.x.11 (domain-a virtual serverVM), x.xxx.x.12 (exchange-VM), (x.xxx.x.13- host box + backup device). When I try to remote logon to the .13 server I would get this message, "The current time on the computer and the current time on the network are different." The rest of the servers (.11 and .12) i am able to log in no problem. I even tried remoting to the the .13 from the .11 but no success. I checked the time using the command line net time \\x.xx.x.11 and net time \\x.xx.x.13 and found a difference of 5 minutes. Now i don't know how to remotely fix the differences.
I found a command line that would syncronize to gov and millitary standards but they did not change the differences ex. net time /setsnt:time.nist.gov then net time /setsntp:\\x.xxx.x.11 . but to no avail.
when i typed the following command line: net time /querysntp
I get My current SNTP value: NAS (which is the server i cannot connect to).
the functions are fine, i just need access to that particular server for maintenance purpose.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Now I have a new problem/ new error:
"Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or because yuo computer account was not found. Please tyr again later....."
Ping this server and it is alive. I know that it is up and running because it is hosting two VM server that are running smoothly. So do you have any idea if this is an account issue? something i could fix in AD? or other command line to remotely communicate with this x.x.13 server?