All replies

• 

  

  0

  Sign in to vote

  Hi,

  Do you mean that you have IPv6 network? As we do not recommend to disable IPv6, please try the following and see how it works:

  1. Open Control Panel and navigate to Control Panel\Network and Internet\Network Connections.

  2. Press ALT and click Advanced.

  3. Click Advanced Settings.

  4. Make sure that IPv4 has the priority order.

  ---

  Niki Han
  TechNet Community Support

  

  Wednesday, June 5, 2013 2:28 AM
• 

  

  0

  Sign in to vote

  Setting IPv4 to be preferred (priority order) over IPv6 will simply mask the problem and affect a lot of other traffic to other IPv6-enabled sites, and as such I don't think that will be a helpful troubleshooting step since the OP has already noted that disabling IPv6 (temporarily or otherwise) resolves the problem.

  Cacklebrain, You might want to start by running a traceroute to the referenced location to ensure that you are actually able to reach it over IPv6. It may be a routing problem between the SP network and the update server. If the traceroute seems to complete successfully, then hopefully someone can give you better guidance as to the reason for the error code.

  
  

  • Edited by WG_IV Wednesday, June 5, 2013 2:10 PM spelling error

  Wednesday, June 5, 2013 2:09 PM
• 

  

  0

  Sign in to vote

  Thanks for the response. I tried a traceroute when I was initially trying to work out what was going on.

  Neither the IPV4 or IPV6 actually get all of the way to the update server (which is not unusual once you get so far into a company's network).

  However what I did find is that fe1.update.microsoft.com (this is the server I see in windowsupdate.log) has 2 IPV6 addresses according to our ISP's DNS servers...

  Non-authoritative answer:
  Name:    fe1.update.microsoft.com.akadns.net
  Addresses:  2a01:111:200f::a1
            157.56.67.221
  Aliases:  fe1.update.microsoft.com

  Non-authoritative answer:
  Name:    fe1.update.microsoft.com.akadns.net
  Addresses:  2a01:111:2006:2::fe1
            157.56.67.221
  Aliases:  fe1.update.microsoft.com

  From the traces you can (probably) tell that I'm in Australia, but I presume that shouldn't make any difference.

  Here's the IPV4 trace...

   

  C:\Users\administrator>tracert fe1.update.microsoft.com
  
  Tracing route to fe1.update.microsoft.com.akadns.net [157.56.67.221]
  over a maximum of 30 hops:
  
    1     1 ms     1 ms    <1 ms  192.168.1.254
    2    21 ms    21 ms    20 ms  lns21.adl2.on.ii.net [203.16.215.199]
    3    20 ms    30 ms    21 ms  gi9-30.cor3.adl2.on.ii.net [150.101.134.190]
    4    21 ms    21 ms    21 ms  xe-0-0-0.cr1.adl6.on.ii.net [150.101.225.77]
    5   221 ms   220 ms   234 ms  ae4.br1.syd7.on.ii.net [150.101.33.34]
    6   198 ms   196 ms   196 ms  te0-2-0-3.br2.sjc2.on.ii.net [203.16.213.158]
    7   220 ms   221 ms   219 ms  be1.br1.sjc2.on.ii.net [150.101.33.56]
    8   220 ms     *      220 ms  8075.microsoft.com [206.223.116.17]
    9   198 ms   198 ms   197 ms  xe-6-0-2-0.bay-16c-1a.ntwk.msn.net [207.46.40.8]
  
   10   250 ms   218 ms   251 ms  ge-6-0-0-0.tuk-64cb-1b.ntwk.msn.net [207.46.43.1
  77]
   11     *        *        *     Request timed out.
  
   30     *        *        *     Request timed out.
  
  Trace complete.
  

  I did the IPV6 traces and one appears to get somewhere into the Microsoft network, but the other one I'm not so sure about.
  

  Tracing route to 2a01:111:200f::a1 over a maximum of 30 hops
  
    1     5 ms     1 ms    <1 ms  2001:44b8:196:ae00::1
    2    20 ms    20 ms    20 ms  loop0.lns21.adl2.on.ii.net [2001:44b8:8020::b]
    3    20 ms    22 ms    22 ms  gi9-30.cor3.adl2.on.ii.net [2001:44b8:8020:1a::1]
    4    20 ms    20 ms    20 ms  g8-1.bdr1.adl6.on.ii.net [2001:44b8:8060:25::1]
  
    5    40 ms    39 ms    40 ms  2001:4478:1:1::22
    6    40 ms    40 ms    40 ms  2001:4478:1:1::f
    7    40 ms     *       40 ms  6453.syd.equinix.com [2001:de8:6::6453:1]
    8   192 ms   193 ms   192 ms  pos3-1.mcore4.pdi-paloalto.ipv6.as6453.net [2001:5a0:1200::2d]
    9   192 ms   193 ms   192 ms  if-xe-1-1-0.4.tcore2.pdi-paloalto.ipv6.as6453.net [2001:5a0:1200::36]
   10   194 ms   195 ms   194 ms  2001:5a0:1200::2a
   11   195 ms   195 ms   195 ms  2a01:111:2000:2::e85
   12   270 ms   250 ms   250 ms  2a01:111:2000:2::58d
   13   249 ms   250 ms   250 ms  2a01:111:2000:2::50d
   14   252 ms   269 ms   283 ms  2a01:111:2000:2::50a
   15   257 ms   252 ms   251 ms  ten6-4.blu-76c-1a.ntwk.msn.net [::ffff:207.46.46.121]
   16   251 ms   252 ms   252 ms  2a01:111:200f::1
   17     *        *        *     Request timed out.
  

   30     *        *        *     Request timed out.
  
  Trace complete.

  Tracing route to 2a01:111:2006:2::fe1 over a maximum of 30 hops
  
    1     1 ms     1 ms    <1 ms  2001:44b8:196:ae00::1
    2    20 ms    20 ms    20 ms  loop0.lns21.adl2.on.ii.net [2001:44b8:8020::b]
    3    20 ms    20 ms    21 ms  gi9-30.cor3.adl2.on.ii.net [2001:44b8:8020:1a::1
  ]
    4    20 ms    20 ms    21 ms  g8-1.bdr1.adl6.on.ii.net [2001:44b8:8060:25::1]
  
    5    40 ms    39 ms    39 ms  2001:4478:1:1::22
    6    40 ms    40 ms    41 ms  2001:4478:1:1::f
    7    40 ms     *       41 ms  6453.syd.equinix.com [2001:de8:6::6453:1]
    8   191 ms   192 ms   193 ms  pos3-1.mcore4.pdi-paloalto.ipv6.as6453.net [2001:5a0:1200::2d]
    9   192 ms   193 ms   192 ms  if-xe-1-1-0.4.tcore2.pdi-paloalto.ipv6.as6453.net [2001:5a0:1200::36]
   10   194 ms   195 ms   193 ms  2001:5a0:1200::2a
   11   246 ms   245 ms   247 ms  2a01:111:2000:2::781
   12     *        *        *     Request timed out.
   
   30     *        *        *     Request timed out.
  
  Trace complete.

  Friday, June 7, 2013 12:54 AM