|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
September 27th 04, 12:20 PM
|
|||
|
|||
XP and Time Sync Problem in AD
Have some clients at a remote site that are reporting
random drops of network share access to mapped drives. When it occurs the following message is displayed on the XP workstation: DRIVE is not accessible. There is a time and/or date difference between the client and server. How is the XP boxes getting out of sync in the domain? We are synced throughout the entire forest, and it seems only this site is having an issue. Any ways to work around this? 
|
| Ads |
|
#2
September 27th 04, 05:58 PM
|
|||
|
|||
|
XP and Time Sync Problem in AD
"Dave Clark" wrote in message
... Have some clients at a remote site that are reporting random drops of network share access to mapped drives. When it occurs the following message is displayed on the XP workstation: DRIVE is not accessible. There is a time and/or date difference between the client and server. How is the XP boxes getting out of sync in the domain? We are synced throughout the entire forest, and it seems only this site is having an issue. Any ways to work around this? Look in the syslog of a failing machine and see what gets logged during bootup. If it's only one site, then perhaps there's something getting blocked at one of the routers serving that site? Perhaps the next thing would be to use something like ethereal to do a network trace of a machine booting, and observe the time sync occouring. -- Best Regards, Ron Lowe MS-MVP Windows Networking
|
|
#3
September 27th 04, 05:58 PM
|
|||
|
|||
|
XP and Time Sync Problem in AD
"Dave Clark" wrote in message
... Have some clients at a remote site that are reporting random drops of network share access to mapped drives. When it occurs the following message is displayed on the XP workstation: DRIVE is not accessible. There is a time and/or date difference between the client and server. How is the XP boxes getting out of sync in the domain? We are synced throughout the entire forest, and it seems only this site is having an issue. Any ways to work around this? Look in the syslog of a failing machine and see what gets logged during bootup. If it's only one site, then perhaps there's something getting blocked at one of the routers serving that site? Perhaps the next thing would be to use something like ethereal to do a network trace of a machine booting, and observe the time sync occouring. -- Best Regards, Ron Lowe MS-MVP Windows Networking
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Time and date changing problem | John O'Husky | General XP issues or comments | 1 | September 24th 04 01:24 AM |
| Clock ALWAYS an hour behind on startup | Bruce | General XP issues or comments | 10 | September 15th 04 03:02 PM |
| WinXP SP2 Internet Time Server Problem | Tolga Balci | Windows Service Pack 2 | 1 | September 13th 04 12:54 PM |
| Found problem with sp2 causing windows installer to start all the time | noitisnotme | Windows Service Pack 2 | 1 | September 11th 04 06:09 AM |
| Firewire 1394 speed/connection problem | Kevin Brault | Networking and the Internet with Windows XP | 4 | August 22nd 04 10:31 PM |
Linear Mode
