<div>
Check out this link...<br />
<br />
<a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q258059" rel="ugc">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q258059</a>
</div>


Check out this link...

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q258059 [http://support.microsoft.com/default.aspx?scid=kb;en-us;Q258059]

<div>
Thank Eric, You are Excellent! &nbsp;<br />
<br />
Thanks also Jassav.<br />
<br />
:D
</div>


Thank Eric, You are Excellent!  

Thanks also Jassav.

:D

<div>
Thanks Eric, You are Excellent.<br />
Thanks Also Jassav
</div>


Thanks Eric, You are Excellent.
Thanks Also Jassav

<div>
<div class="content wysiwyg-content">
Hi friends,<br />
<br />
I find our development IIS5 keep returning old web page, even the file is updated. and I find the following warning in Event Viewer (of the IIS5 machine):<br />
------------------<br />
Because of repeated network problems, the time service has not been able to find a domain controller to synchronize with for a long time. To reduce network traffic, the time service will wait 960 minutes before trying again. No synchronization will take place during this interval, even if network connectivity is restored. Accumulated time errors may cause certain network operations to fail. To tell the time service that network connectivity has been restored and that it should resynchronize, execute &quot;w32tm /s&quot; from the command line. <br />
-----------------<br />
<br />
This problem get fixed after rebooting PDC (NT Domain), but will come back within 24 hours.<br />
<br />
We are using NT4 Domain, with w2k member servers.<br />
<br />
Any suggestion?
</div>
</div>


Hi friends,

I find our development IIS5 keep returning old web page, even the file is updated. and I find the following warning in Event Viewer (of the IIS5 machine):
------------------
Because of repeated network problems, the time service has not been able to find a domain controller to synchronize with for a long time. To reduce network traffic, the time service will wait 960 minutes before trying again. No synchronization will take place during this interval, even if network connectivity is restored. Accumulated time errors may cause certain network operations to fail. To tell the time service that network connectivity has been restored and that it should resynchronize, execute "w32tm /s" from the command line. 
-----------------

This problem get fixed after rebooting PDC (NT Domain), but will come back within 24 hours.

We are using NT4 Domain, with w2k member servers.

Any suggestion?

Network Problem: w32time cannot sync.

Windows 2000 is an operating system for use on both client and server computers. It is the successor to Windows NT 4.0, and is the last version of Microsoft Windows to display the "Windows NT" designation. Four editions of Windows 2000 were released (Professional, Server, Advanced Server, and Datacenter Server) that shared a core set of features, including many system utilities such as the Microsoft Management Console. All versions of the operating system support NTFS 3.0, Encrypting File System, as well as basic and dynamic disk storage. The Windows 2000 Server family includes support for Active Directory services, Distributed File System and fault-redundant storage volumes.