My desktop support team noticed the issue about a month ago, but only recently notified me of the issue.
We cannot access http://updates.microsoft.com. The page is blank and IE reports the web page is done loading. I have done some troubleshooting and found the following. Pay special attention to line 9 and 10:
C:\Documents and Settings\Administrator>tracert update.microsoft.com
Tracing route to update.microsoft.com.nsatc.net [65.55.184.156]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 10.3.5.1
2 4 ms 3 ms 3 ms 192.168.1.254
3 13 ms 13 ms 14 ms adsl-99-145-231-254.dsl.emhril.sbcglobal.net [9.145.231.254]
4 14 ms 13 ms 12 ms 68.250.251.65
5 13 ms 13 ms 12 ms bb1-g9-0.emhril.sbcglobal.net [151.164.94.162]
6 36 ms 34 ms 35 ms ex3-p1-0.eqabva.sbcglobal.net [151.164.171.102]
7 35 ms 34 ms 35 ms asn8075-microsoft.eqabva.sbcglobal.net [151.164248.6]
8 35 ms 35 ms 36 ms ge-1-3-0-0.bl2-64c-1a.ntwk.msn.net [207.46.47.9]
9 36 ms 35 ms 96 ms 10.22.112.117
10 35 ms 36 ms 35 ms 10.22.112.70
11 * * * Request timed out.
12 * * * Request timed out.
incase you are wondering why this is an issue see the following information from Wikipedia:
IPv4 private addresses
Early network design, when global end-to-end connectivity was envisioned for communications with all Internet hosts, intended that IP addresses be uniquely assigned to a particular computer or device. However, it was found that this was not always necessary as private networks developed and public address space needed to be conserved (IPv4 address exhaustion ).
Computers not connected to the Internet, such as factory machines that communicate only with each other via TCP/IP, need not have globally-unique IP addresses. Three ranges of IPv4 addresses for private networks , one range for each class (A , B , C ), were reserved in RFC 1918 . These addresses are not routed on the Internet and thus their use need not be coordinated with an IP address registry.
Today, when needed, such private networks typically connect to the Internet through network address translation (NAT).
| IANA-reserved private IPv4 network ranges |
| Start | End | No. of addresses |
| 24-bit Block (/8 prefix, 1 x A) |
10.0.0.0 |
10.255.255.255 |
16,777,216 |
| 20-bit Block (/12 prefix, 16 x B) |
172.16.0.0 |
172.31.255.255 |
1,048,576 |
| 16-bit Block (/16 prefix, 256 x C) |
192.168.0.0 |
192.168.255.255 |
65,536 |
Any user may use any of the reserved blocks. Typically, a network administrator will divide a block into subnets ; for example, many home routers automatically use a default address range of 192.168.0.0 - 192.168.0.255 (192.168.0.0/24).
Since there is NO VALID reason that RCF 1918 IP address should be routing on the internet, I block these addresses on the edge routers. Microsoft should really address this issue and start following IP protocol standards.
The workaround at this time is to use https://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us. This is very slow, but atleast we can install security updates.
