Question Locked

Incorrect time on networked pc's??

0 helpful
29 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

When users log onto the network there clock is out by 7 minutes

They log onto the "Falcon" domain but where do I change the clock so they are all the same??

(Ive checked the bios clock and windows clock on the pc's and they are correct, its just when they log onto the network)

The computers are running xp and server 2003

29 replies

by Member 25348569

Start with your logon server time and work out.

You will want to set one server to get its time from an external source, the other servers to get their time from that one and the workstations will get their time on logon.

Google will get you loads of information.

http://support.microsoft.com/kb/307897

Use [b]w32tm /monitor /domain:yourdomain[/b] to get a list of what syncs with what and if there are issues.

by mikebyrne000

That command produces somthing like:

falconserve1.falcon.local [192.168.1.8] ICMP 0ms delay.

NPT: +0.0337500s offset from Falcon-DC-01.falcon.local

Is that suggesting that the time issue is coming from Falcon-DC-01.falcon.local?

by Member 25348569

That's your starting point. Get that one right and the workstations should be correct.

The offset of your server falconserve1 is only 30ms so that's OK.

by mikebyrne000

Is there a command I can send to the server if I cant gain access to the machine directly?

I cant find it on the monitors and cant access it remotely

by cg it

then who can? they are the one's who should fix the Windows time server that is if it actually needs fixing.

Windows Servers typically use time.nist.gov as part of their machine data and time clock which Windows Time Service will use.

you can use time.windows.com but time.nist.gov is the authoritative time source.

ooops your in Ireland... well there's the GMT time source in England....

by mikebyrne000

Ive just taken over the IT here and you wouldnt belive the mess.

I know what IP it is but cant access that DC via remote desktop and the monitor in the "comms" room isnt connected to it. The boxs themselves arent even labled!

by mikebyrne000

Ive gone though the ip's of the machines and none are .11 which I'm looking for

When I try to access it remotly with the admin password I get:

"To log onto this computer, you must be granted the Allow log on through terminal server right. By default, members of the remote desktop users group have this right. If you are not a member ......you must be given this right"

However, I can access all the other servers remotely with the admin password

by cg it

if you know the IP address just check the nic card settings.

If you come back and say, well I can't log on locally, I don't have the account info, then either your not supposed to or your royally screwed.

Royally screwed meaning that if you can log on to the servers, you can maintain them so you'll have to reset the passwords which probably will break stuff.

by cg it

if you can't physically find the server, which by process of elimination of logging in locally, and then labeling them, should be the last one, maybe "they" [whomever they is] hid it in some other closet. If your the only IT guy around, well have fun.

by churdoo

From a rig that you CAN log into with an admin account, you can go to Computer Management / Connect to another computer / Specify the server in question / fix the permissions so that you can log on to said server via RDP / voila!

by mikebyrne000

How do I alter the permission to allow remote access to this terminal?

I cant see a security option?

by Member 25348569

There is no local user logon, only domain user access. Do you have any idea what the virtualisation software is?

by mikebyrne000

I'll was going to do something like this on the domain controller which Im trying to find/access

I've since found out its on a virtual machine

by oldbaritone

but the server's real-time clock was whacked and it still had a lot of drift. That raased problems with workstations connected to secure internet sites that had short time-outs - the clock would cause them to be logged out before they could complete the data input.

It was a hardware problem, but it took a while to get a replacement server box because mgmt didn't perceive it as a problem and replacement would cause an outage.

The two work-arounds we did were to decrease the server re-sync time to 30 minutes instead of 24 hours, so the clock couldn't drift too far; and set the workstations to sync to internet time directly, so their RTCs were correct in the "real world."

After two months, we finally got the new box, so it's moot at this point. But we got a real education about how much havoc a defective RTC can wreak.

by cg it

log on to that...then log in to the virtual instance... fix the problem.

don't forget the labeler...

by mikebyrne000

Is there any way to tell what machine the server is sitting on?

All im going on at present is the bog standard 192.168.0.11

by cg it

Sometimes the best education is doing.....

by mikebyrne000

I am doing, but its a bit like finding a needle in a haystack.

Just looking for a bit of advice. Its the only server I cant access

by chris910

The simplest way to find your server.

(with the proviso that it is appropriate for your business. Off hours, weekend etc.)

Set up a computer so that you can view it while accessing the network cables. open a command prompt, Ping -t 192.168.0.11 and then pull the cables and replace them one at a time. when you have pulled the connection for the DC the ping connection time will drop out and then restart when the server is plugged in. Presto, DC found!
[If you do it for just 4 or 5 seconds at a time your users may see a timeout error or have other minor issues but should be ok.]

You may also be able to use the
pathping -n 192.168.0.11 command as a tool to help locate the DC the host server may show up in the routers list depending on configuration.

by mikebyrne000

The pathping just went from my machine to the .11 address

Im leaning towards it being on .10 because I'm having the same error accessing it

by Member 25348569

Can you access Active directory Users and computers on your workstation? If you can, and you have an Admin login, you ought to be able to do anything.

The DC will only accept a domain logon, all of its permissions come from the domain so there ought to be no way to keep you out.

Edited to add, if you can't, then install it! Windows 2003 server admin pack.

by mikebyrne000

Im accessing it as follows (same as the others)

user: Administrator

password: xxxxxxxxxxx

Domain: Falcon

by churdoo

And the permissions for that are dorked. That leaves you 2x choices

1. Find the physical host that the DC is running on and connect to that host with the virtualization tools so you can open the console of the DC

2. Fix the RDP permissions by whatever means appropriate. This will require access to Active Directory Users and Computers, and/or Group Policy, and/or Terminal Services Configuration to give the Administrator or an administrator permission to log onto the DC via RDP.

by mikebyrne000

I have full access to Active Directory.

I can remote desktop to all the servers bar 2

by cg it

anything after that is simply posting to post.

You mention this is a virtual machine. If you don't know anything about virtual machines, the the only other option is "if you can't fix it, you'll have to hire someone who can".

This discussion is closed to new replies.