The NET TIME Command May Report the GMT Bias Incorrectly

This article was previously published under Q319913
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
If you run the net time command against a server that is located in a time zone that is not an exact multiple of 60 minutes from Greenwich Mean Time (GMT), and that is located in a time zone other than yours, the bias is reported incorrectly.

For example, the local time (GMT+04:45) at \\Server is 02/19/2002 14:50, and the time for the Kathmandu (Nepal Standard Time) is +05:45.

This problem affects the following time zones:

(GMT-03:30) Newfoundland
Newfoundland Daylight Time

(GMT+03:30) Tehran
Iran Daylight Time
Iran Standard Time

(GMT+04:30) Kabul
Afghanistan Daylight Time
Afghanistan Standard Time

(GMT+05:30) Calcutta, Chennai, Mumbai, New DelhiIndia Daylight Time
India Standard Time
(GMT+05:45) Kathmandu
Nepal Daylight Time
Nepal Standard Time

(GMT+06:30) Rangoon
Myanmar Daylight Time
Myanmar Standard Time

(GMT+09:30) Darwin
AUS Central Daylight Time
AUS Central Standard Time

(GMT+09:30) Adelaide
Cen. Australia Daylight Time
Cen. Australia Standard Time
RESOLUTION

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.The English version of this fix should have the following file attributes or later:
   Date        Time   Version        Size     File name   ----------------------------------------------------   4-Apr-2002  15:30  5.0.2195.5533  124,176  Net1.exe				

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
MORE INFORMATION
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:
296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot
Właściwości

Identyfikator artykułu: 319913 — ostatni przegląd: 02/27/2014 21:12:21 — zmiana: 3.6

Microsoft Windows 2000 Server SP1, Microsoft Windows 2000 Server SP2, Microsoft Windows 2000 Advanced Server SP1, Microsoft Windows 2000 Advanced Server SP2, Microsoft Windows 2000 Professional SP1, Microsoft Windows 2000 Professional SP2

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbwin2ksp4fix kbbug kbfix kbwin2000presp3fix KB319913
Opinia
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)