Regional Update server? DarkStarZA 7/11/2007 7:54:01 AM Are there any other update servers available I can point my new installation of WSUS 3 to? Specifically in South Africa. Due to slow international speeds in SA it would make life alot easier for me if there were closer update servers available. Thanx,

Re: Regional Update server? "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 7/12/2007 2:43:47 AM "DarkStarZA" <DarkStarZA[ at ]discussions.microsoft.com> wrote in message news:6165599F-A524-4441-B96D-235BCD526711[ at ]microsoft.com... [Quoted Text] > Are there any other update servers available I can point my new > installation > of WSUS 3 to? > > Specifically in South Africa. Due to slow international speeds in SA it > would make life alot easier for me if there were closer update servers > available. The domain names should be automagically resolved to regionalized data centers. The *.microsoft.com domain name are merely aliases that point to the various hosting services that host Microsoft content around the world. Have you run a traceroute and domain lookup to identify exactly where your WSUS Server is being routed to? -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://www.microsoft.com/wsus And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Regional Update server? DarkStarZA 7/12/2007 7:32:04 AM When I ping update.microsoft.com it resolves to update.microsoft.com.nsatc.net [207.46.253.125]. Doing a Whois on this ip gives me: OrgName: Microsoft Corp OrgID: MSFT Address: One Microsoft Way City: Redmond StateProv: WA PostalCode: 98052 Country: US So I guess that Redmond is my "closest" update server. "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "DarkStarZA" <DarkStarZA[ at ]discussions.microsoft.com> wrote in message > news:6165599F-A524-4441-B96D-235BCD526711[ at ]microsoft.com... > > Are there any other update servers available I can point my new > > installation > > of WSUS 3 to? > > > > Specifically in South Africa. Due to slow international speeds in SA it > > would make life alot easier for me if there were closer update servers > > available. > > The domain names should be automagically resolved to regionalized data > centers. The *.microsoft.com domain name are merely aliases that point to > the various hosting services that host Microsoft content around the world. > > Have you run a traceroute and domain lookup to identify exactly where your > WSUS Server is being routed to? > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://www.microsoft.com/wsus > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > > >

Re: Regional Update server? "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 7/13/2007 3:05:52 AM "DarkStarZA" <DarkStarZA[ at ]discussions.microsoft.com> wrote in message news:D0FDE60C-C836-4FAA-B5ED-3FC5E85F1EEA[ at ]microsoft.com... [Quoted Text] > When I ping update.microsoft.com it resolves to > update.microsoft.com.nsatc.net [207.46.253.125]. > > Doing a Whois on this ip gives me: > OrgName: Microsoft Corp > OrgID: MSFT > Address: One Microsoft Way > City: Redmond > StateProv: WA > PostalCode: 98052 > Country: US > > So I guess that Redmond is my "closest" update server. The *whois* is not really authoritative. It only tells you who the *registered* owner of the address is. Your best luck is in using traceroute and following the path back to the source. Note also that from Texas, update.microsoft.com resolves to an entirely different network. >nslookup update.microsoft.com <***> Name: update.microsoft.com.nsatc.net Address: 64.4.21.189 Aliases: update.microsoft.com What we know for sure is that both networks are operated by nsatc.net, which is Savvis Communications in California. Running traceroutes to both IP Addresses gives us this: Tracing route to update.microsoft.com.nsatc.net [64.4.21.189] over a maximum of 30 hops: <***> 3 12 ms 10 ms 11 ms dist2-vlan60.hstntx.sbcglobal.net [151.164.11.189] 4 11 ms 9 ms 10 ms bb2-g2-0.hstntx.sbcglobal.net [151.164.43.42] 5 36 ms 41 ms 35 ms ex1-p5-0.eqabva.sbcglobal.net [151.164.191.134] 6 * * asn8075-microsoft.eqsjca.sbcglobal.net [151.164.248.6] reports: Destination net unreachable. Doesn't give us a definitive answer, but it does tell us that the path appears to be going from Houston to San Jose, CA. It would appear that there might be some congestion in that San Jose link, because a subsequent test couldn't even get a response from the San Jose router. -- but maybe the 64.* network is blocking ICMP at the perimeter and the SBC San Jose router isn't consistent about how it handles the response. Checking the address from South Africa: <***> 3 14 ms 10 ms 11 ms dist2-vlan60.hstntx.sbcglobal.net [151.164.11.189] 4 12 ms * 11 ms bb2-g2-0.hstntx.sbcglobal.net [151.164.43.42] 5 35 ms 35 ms 35 ms ex1-p1-1.eqabva.sbcglobal.net [151.164.95.101] 6 35 ms 34 ms 36 ms asn8075-microsoft.eqsjca.sbcglobal.net [151.164.248.6] 7 36 ms 35 ms 36 ms ge-7-3-0-55.ash-64cb-1b.ntwk.msn.net [207.46.41.61] 8 39 ms 36 ms 36 ms ge-0-0-0-0.ash-64cb-1a.ntwk.msn.net [207.46.41.33] 9 101 ms 105 ms 98 ms so-7-2-3-0.wst-64cb-1b.ntwk.msn.net [207.46.35.97] 10 97 ms 95 ms 96 ms ge-0-1-0-0.tuk-64cb-1b.ntwk.msn.net [207.46.35.165] 11 96 ms 96 ms 98 ms ten2-4.tuk-76c-1b.ntwk.msn.net [207.46.44.54] 12 99 ms 98 ms 99 ms po17.tuk-65ns-mcs-1b.ntwk.msn.net [207.46.35.146] 13 * * * Request timed out. That one gets us a bit farther... inside msn.net. I'll leave it to a real cryptanalyst to figure out what "po17.tuk-65ns-mcs-1b" means. Only thing we know for certain is that the path to 207.46.253.125 flew right through SBCGlobal's San Jose router into an msn.net link, but tracing to 64.4.21.189 didn't meet with such good luck. That, at least, suggests to me that the paths went in different directions from San Jose. Another clue is that the South Africa resolution goes to a Class C network (207.46.253.0), and the Houston, Texas, resolution goes to a Class A network (64.0.0.0) The real test, though, is to run the traceroute to 207.46.253.125 from South Africa, and see where it goes, and ends up. It could well be that all of the servers are on the West Coast of the U.S. -- but I *highly* doubt that. Microsoft isn't particularly glib about the locations of their data centers outside of the Redmond campus. :-) -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://www.microsoft.com/wsus And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....