Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 271
  • Last Modified:

Set the time on a network

I need to set the time on a network. It can not be from an external source, I would like to use the net time command. It is currently in a login script but not working. Its net time \\servername /set /yes but it doesnt do anything. Even when I type this in a command prompt it doesnt work, it just shows command completed successfully, but nothing changes:

It states
Current time at \\server is 4/13/2006 11:02 AM
Local time at \\server is 4/13/2006 6:32 AM
The command completed successfully.


But my pc still says 11:02.... I need it to change to local time when I run this, any ideas?
0
jbell72
Asked:
jbell72
1 Solution
 
Irwin SantosComputer Integration SpecialistCommented:
are you doing this on the server or the workstation?  Confirm that the server has indeed the correct time.
0
 
jbell72Author Commented:
I need to set the entire network to the time via batch script. I set the server to Greenwich mean time and am testing the command on a pc but the pc doesnt change.
0
 
NeoEGMCommented:
Hi,

Do you have Administrative access?

What OS is the command running on?
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
ian_chardCommented:
I don't think you need to use the \\servername command. I'm assuming that you are in a Windows environment, by default the time is picked up from the DC(s). You may want to check your DC(s) out to make sure that they are set to the correct time, then you can simply use net time /set /y on the workstations.

One thing you may not have realised is that if the time is way out then this won't work from a logon script. This is purely because the machines won't be able to authenticate, hence why you have to run this manually. We have a fair few Dell's that like to set themselves back to July 2003, the only solution I've found is to use DameWare Command Line Tools and the local admin account to reset this.

Another reason why it's probably not working in a login script is because the machines will fail to find the net exe. Take a copy of the net.exe file from one of your servers and place it in the same folder as the logon batch file. Check your event logs too on the clients as if the net time batch file has failed an event will be written to the system event logs. You may also need to change how you are applying the logon script. If you are applying it as a user configuration it may fail if the user doesn't have the rights to change system clocks, to overcome this look at setting a startup script in computer configuration instead.
0
 
CGretskiCommented:
what timezone is the PC in - the PC's work in seconds since a certain date, then modify how the time is displayed based on timezone settings -- so the two times may indeed be the same as far as the PC cares, and it just be changing the displayed output.

Easy way the check if it is synching, move the clock a couple of minutes out, then run the command again, see if it resets it.

If so just put the client PC in the correct timezone and it should display correctly.
0
 
jbell72Author Commented:
yes I am a domain admin
0
 
rsivanandanCommented:
First decide the server to which you want to synchronize the time with, mostly a domain controller?

Then on all the client machines;

net time /setsntp:<DomainController IP>

after this try to see the time.

Cheers,
Rajesh
0
 
OAC TechnologyProfessional NerdsCommented:
have you checked the time zones?
0
 
jbell72Author Commented:
Have I checked the time zones yes. What am I checking for?
0
 
rsivanandanCommented:
Did you try the solution in my comment?

Cheers,
Rajesh
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now