Windows 7 - no network connection with wrong time
Network connections (peer to peer) from Windows 7 (RC) to Windows XP and Windows 2000 fail, if date and/or time on both computers are differing too much. In the moment I could not find out, how much deviation is allowed. Sometimes it works with even 1 hour difference, but sometimes network access fails even with 10 minutes difference. Took me some time to find out, why I was asked for the input of my credentials, even if I already saved them. And access was always denied, even with the right credentials. After correcting the computer time manually, I could access Win2k and Win XP again.Usually I run a small batch-file with the NET TIME command in it, to synchronize time with one of my computers (Win2k). This works fine with Win2k and Win XP. In Windows 7 I got this script running by disabling User Account Control. But if the machine's time is too much deviating from the "master's" time, then network access is denied and I cannot get the right time from the master - and the I cannot access the network.Note: The master synchronizes time with a Time-Server in the internet.Has somebody an idea, how to solve this problem? Thanks a lot!
September 11th, 2009 11:58am

Usually that means the clock on the mother board is probably bad if your time is drifting that much. Have you checked that? You could also increase the frequency Windows 7 syncs with the time server by way of a simply registry hack.The user can increase or decrease the frequency of updates by making a simple registry change. Add or change the SpecialPollInterval DWORD setting. Note the value is in seconds...HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\For example the value is set to 3600 on my Windows 7 and XP machines (that's in seconds), so the machines poll the time server once each hour.MS-MVP Windows Desktop Experience, "When all else fails, read the instructions"
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2009 9:01pm

Hi, If Al Jarvi is right about the motherboard, it most likely to be the computer running Win2k . The motherboard might need a new cmos battery. Before you change it, take a note of the bios settings. Slan go foill, Paul
September 12th, 2009 1:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics