PHWinfo banniere

Titres
PORTAIL ANNUAIRE ARTICLES COMPARATEUR HÉBERGEURS DEVIS FORUMS RÉDUCTEUR D'URL
Précédent   PHWinfo > Forums Hébergement > Forum Noms de domaine > ms.public.winnt.domain > Windows Time Service going to non-local IP?
S'inscrire FAQ Membres Recherche Messages du jour Marquer les forums comme lus
ms.public.winnt.domain Usnet Forum about Windows NT.

Windows Time Service going to non-local IP?

Réponse
 
LinkBack Outils de la discussion
Vieux 19/03/2007, 23h25   #1
Phil McNeill
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Windows Time Service going to non-local IP?

Hi,

Since Friday roughly 30 PCs on my network of 600 have been sending traffic
to 157.184.0.2 via TCP port 123 (NTP). I am seeing this traffic being
dropped outbound at my firewall and each PC is generating it every 15
seconds. I don't understand why they would all of a sudden start doing
this. I don't see any rogue processes or services running, and if I turn
off the Windows Time Service on the PC, it stops sending the traffic.

Any ideas on what would cause this to pop up all of a sudden on a small
percentage of PCs? Possible that a common print driver could cause this? I
see references to that IP range being the default for some Lexmark printers.

Thanks for any thoughts!

Phil


  Réponse avec citation
Vieux 19/03/2007, 23h49   #2
Robert Jacobs
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Windows Time Service going to non-local IP?

On Mar 19, 4:25 pm, "Phil McNeill"
<philmcne...@REMOVETEXTINCAPShydroottawa.com> wrote:
> Hi,
>
> Since Friday roughly 30 PCs on my network of 600 have been sending traffic
> to 157.184.0.2 via TCP port 123 (NTP). I am seeing this traffic being
> dropped outbound at my firewall and each PC is generating it every 15
> seconds. I don't understand why they would all of a sudden start doing
> this. I don't see any rogue processes or services running, and if I turn
> off the Windows Time Service on the PC, it stops sending the traffic.
>
> Any ideas on what would cause this to pop up all of a sudden on a small
> percentage of PCs? Possible that a common print driver could cause this? I
> see references to that IP range being the default for some Lexmark printers.
>
> Thanks for any thoughts!
>
> Phil


Wierd. Do you have a group policy setup to use a specific server for
ntp? Our company has a GP for the domain controllers to be ntp
servers, and the machines at each location are setup as ntp client
pointing to the local DC. What does your setup look like? Do you
need setting up ntp servers and clients via ntp?

Look here for some info:
http://www.microsoft.com/technet/pro.../26_s3wts.mspx

Good luck!

  Réponse avec citation
Vieux 20/03/2007, 00h03   #3
Robert Jacobs
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Windows Time Service going to non-local IP?

On Mar 19, 4:49 pm, "Robert Jacobs" <robertjacob...@gmail.com> wrote:
> On Mar 19, 4:25 pm, "Phil McNeill"
>
>
>
>
>
> <philmcne...@REMOVETEXTINCAPShydroottawa.com> wrote:
> > Hi,

>
> > Since Friday roughly 30 PCs on my network of 600 have been sending traffic
> > to 157.184.0.2 via TCP port 123 (NTP). I am seeing this traffic being
> > dropped outbound at my firewall and each PC is generating it every 15
> > seconds. I don't understand why they would all of a sudden start doing
> > this. I don't see any rogue processes or services running, and if I turn
> > off the Windows Time Service on the PC, it stops sending the traffic.

>
> > Any ideas on what would cause this to pop up all of a sudden on a small
> > percentage of PCs? Possible that a common print driver could cause this? I
> > see references to that IP range being the default for some Lexmark printers.

>
> > Thanks for any thoughts!

>
> > Phil

>
> Wierd. Do you have a group policy setup to use a specific server for
> ntp? Our company has a GP for the domain controllers to be ntp
> servers, and the machines at each location are setup as ntp client
> pointing to the local DC. What does your setup look like? Do you
> need setting up ntp servers and clients via ntp?
>
> Look here for some info:http://www.microsoft.com/technet/pro...ver2003/techno...
>
> Good luck!- Hide quoted text -
>
> - Show quoted text -


I meant to say "Weird" not "Wierd"

  Réponse avec citation
Vieux 20/03/2007, 15h35   #4
Ray
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Windows Time Service going to non-local IP?

Lexmark is probably phoning home to report on how often you're printing.
Lexmark is assigned that IP block.

Ray

"Phil McNeill" <philmcneill@REMOVETEXTINCAPShydroottawa.com> wrote in
message news:%23NkWf0maHHA.4788@TK2MSFTNGP04.phx.gbl...
> Hi,
>
> Since Friday roughly 30 PCs on my network of 600 have been sending traffic
> to 157.184.0.2 via TCP port 123 (NTP). I am seeing this traffic being
> dropped outbound at my firewall and each PC is generating it every 15
> seconds. I don't understand why they would all of a sudden start doing
> this. I don't see any rogue processes or services running, and if I turn
> off the Windows Time Service on the PC, it stops sending the traffic.
>
> Any ideas on what would cause this to pop up all of a sudden on a small
> percentage of PCs? Possible that a common print driver could cause this?
> I see references to that IP range being the default for some Lexmark
> printers.
>
> Thanks for any thoughts!
>
> Phil
>



  Réponse avec citation
Vieux 28/03/2007, 22h29   #5
Phil McNeill
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Windows Time Service going to non-local IP?


"Ray" <n/a> wrote in message news:uYWjcTvaHHA.5108@TK2MSFTNGP03.phx.gbl...
> Lexmark is probably phoning home to report on how often you're printing.
> Lexmark is assigned that IP block.
>
> Ray


The "why" is not cofirmed, but it did come down to a blabbermouth Lexmark
printer. Killed it, problem solved.



  Réponse avec citation
Vieux 29/03/2007, 14h49   #6
Ray
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Windows Time Service going to non-local IP?

You really have to wonder what these vendors are doing. We installed several
Zebra label printers and they're all trying to go to dozens of URLs on the
Internet with the time-tcp protocol.

There is nothing on the printer that does a timestamp. There's nothing
exposed in the interface for time servers and the vendor swears they're not
doing it.

I really wonder where they're getting their firmware and how closely they
are (not) auditing what it does.

Ray

"Phil McNeill" <philmcneill@REMOVETEXTINCAPShydroottawa.com> wrote in
message news:erVmFfXcHHA.4864@TK2MSFTNGP05.phx.gbl...
>
> "Ray" <n/a> wrote in message news:uYWjcTvaHHA.5108@TK2MSFTNGP03.phx.gbl...
>> Lexmark is probably phoning home to report on how often you're printing.
>> Lexmark is assigned that IP block.
>>
>> Ray

>
> The "why" is not cofirmed, but it did come down to a blabbermouth Lexmark
> printer. Killed it, problem solved.
>
>
>



  Réponse avec citation
Réponse


Outils de la discussion

Règles de messages
Vous ne pouvez pas créer de nouvelles discussions
Vous ne pouvez pas envoyer des réponses
Vous ne pouvez pas envoyer des pièces jointes
Vous ne pouvez pas modifier vos messages

Les balises BB sont activées : oui
Les smileys sont activés : oui
La balise [IMG] est activée : oui
Le code HTML peut être employé : non
Trackbacks are oui
Pingbacks are oui
Refbacks are oui


Fuseau horaire GMT +1. Il est actuellement 00h11.


Édité par : vBulletin® version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0 RC5 Tous droits réservés.
Version française #16 par l'association vBulletin francophone
PHWinfo est un site Éducation Sans Frontières ©2000-2008
Ad Management by RedTyger
©Tous droits réservés par les parties respectives
Page generated in 0,17495 seconds with 14 queries