Re: Windows Time Service accessing unknow IP address
- From: David <david.oreilly@xxxxxxxxxxxxxxx>
- Date: Wed, 14 Sep 2005 16:08:23 +0100
Giuseppe Nacci wrote:
David wrote:
Hi,
We have a windows 2000 Advanced Server with (mostly) windows XP workstations. The DC is time synced to an external source, and appears to be the only time source listed in the w32time settings. The workstations are setup to sync to the DC and this also appears to be the only time source listed on the workstations. The actual time synchronisation works but there is an added side affect. All PCs including the server are attempting to access an unknown IP address - 191.168.1.225). I can see this on the firewall logs and also using a port scanner on the client PCs. Our internal subnet is configured for the 192.168.x.x range.
This only happens when the Windows time Service is running, and using the port scanner I have confirmed that it is the svchost process started by W32time which is attempting the access
Anybody got any ideas, where the rogue IP address could be coming from? Thanks, David
Is 191.168.1.225 your client? To which server is syncro the DC? The clients point to DC to syncro or where? Did u set it by GPO? Remember that Time Syncro require port no.123 opened.
191.168.1.225 is unknown on our network. I guess it may be something that was set historically, but I can't find any reference to it in our setup.
The DC is syncing to an external server - ntp.esat.net.
The client points to the DC and is set using "net time /setsntp:timeserver"
Other info - Rogue IP address is being accessed on port 1230
Also, not sure if this will provide any clues....On one of the clients we have VMware installed and curiously it is actually accessing the correct ip address of the DC on port 123.
.
- References:
- Windows Time Service accessing unknow IP address
- From: David
- Re: Windows Time Service accessing unknow IP address
- From: Giuseppe Nacci
- Windows Time Service accessing unknow IP address
- Prev by Date: Re: page file setting foe w2k3 svr with 4GB RAM
- Next by Date: Re: Limit system cache
- Previous by thread: Re: Windows Time Service accessing unknow IP address
- Next by thread: Re: Error 1053 when I try to stop a service
- Index(es):
Relevant Pages
|