|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: huh
----- Original Message ----- From: "Sean Donelan" <[email protected]> To: "Steven M. Bellovin" <[email protected]> Cc: "David G. Andersen" <[email protected]>; "Ian A Finlay" <[email protected]>; <[email protected]> Sent: Tuesday, January 15, 2002 2:27 PM Subject: Re: huh > > > > On Tue, 15 Jan 2002, Steven M. Bellovin wrote: > > > Um, it's firewalled? Most of microsoft isn't traceroutable or > > >pingable. > > > > Yup: > > > > b129$ ipsrvtrace -p 80 windowsupdate.microsoft.com > [...] > > 15 65.195.34.226 65.195.34.226 155.934 156.415 156.973 > > 16 iusbsecurc1202-ge-6-0.msft.net 207.68.128.66 13.109 13.598 14.142 > > 17 - - * * * > > 18 207.68.131.27 207.68.131.27 13.988 14.373 * > > Microsoft has been moving/changing Windowsupdate.microsoft.com for > the last week or so. The problems have been covered extensively > in other forums. > > Although microsoft technicians have messed up access filters on its > routers in the past, I believe this is just them blocking some packets > used by the standard traceroute. If you are having other problems > with windowsupdate, I think they are unrelated to traceroute. Ok, well this is good to know. Although it still doesn't explain why my firewall is reporting DNS UDP/TCP probes from windowupdate.com on a regular basis. -Tim > >
|