I cannot view or open any pages with microsoft.com in the domain name

已答覆 I cannot view or open any pages with microsoft.com in the domain name

  • jeudi 10 mai 2012 03:10
     
     

    I am running a windows server 2008 with exchange 2010 in a hyper v environment. I tried running updates on the server and got the error code 8024402f.

    In my efforts to begin troubleshooting i found that i could not open or view any web page or pages that had anything to do with micorosft.com

    i can sucecssfully perform an nslookup on microsoft.com and update.microsoft.com.I can also ping both of these domain names with no replies but it does resolve the name during the ping process.

    i can successfully surf the web it is only MS webpages that i cannot view. in my readings i found conversations about transparent proxies but i have no idea what that is.

    I also have other virtual servers running 2008 srv and can view MS webpages without any problems

    Any ideas and or suggestions would be a great help

    thanks

    Carlos

Toutes les réponses

  • jeudi 10 mai 2012 03:58
     
     

    Hi Carlos,

    Please try to follow "Temporary connection-related errors may occur when you use Windows Update or Microsoft Update" to fix the problem.

    Regards, Terry | My Blog: http://terrytlslau.tls1.cc

  • vendredi 11 mai 2012 02:56
    Modérateur
     
     

    Hi Carlos,

    Thank you for the post.

    Error code 8024402f is caused by you couldn't connect to microsoft.com page. It's a DNS or network connectivity issue.
    Please ping and tracert update.microsoft.com on this server and another server. Contrast the resolved ip address and tracert hops status.

    If there are more inquiries on this issue, please feel free to let us know.

    Regards


    Rick Tan

    TechNet Community Support

  • vendredi 11 mai 2012 02:58
     
     

    A transparent proxy is your firewall that redirect all port 80 traffic to a proxy before allowing you on the internet.

    Check your firewall's rule to be sure to exclude your server from that rules if it's the case.


    MCP | MCTS 70-236: Exchange Server 2007, Configuring

  • lundi 14 mai 2012 14:45
     
     

    Rick Tan I ran the Traceroute and am including the results along with this post. I cant say I understand why it is timing out after a couple of hops. Any insught on this from anyone willbe a great help to me.

    Here are the results

    C:\>tracert update.microsoft.com

    Tracing route to www.update.microsoft.com.nsatc.net [65.54.51.251]
    over a maximum of 30 hops:

      1    <1 ms    <1 ms    <1 ms  10.1.10.1
      2     2 ms     1 ms     2 ms  206.253.170.209
      3     1 ms     1 ms     1 ms  po1-ibr4.vaultnetworks.com [206.253.168.157]
      4     1 ms     1 ms     1 ms  po3-ibr3.vaultnetworks.com [206.253.168.149]
      5     1 ms     1 ms     1 ms  border2.ge1-8.vaultnet-4.mia007.pnap.net [69.25.
    48.141]
      6     1 ms     1 ms     1 ms  core2.t6-2.bbnet2.mia003.pnap.net [69.25.0.66]
      7     1 ms     1 ms     1 ms  tengigabitethernet2-2.ar1.mia2.gblx.net [64.212.
    16.165]
      8     1 ms     1 ms     1 ms  ip-208.49.147.86.gblx.net [208.49.147.86]
      9    45 ms    35 ms    35 ms  xe-2-0-0-0.sn1-96cb-1a.ntwk.msn.net [207.46.43.6
    0]
     10    36 ms    31 ms    31 ms  ge-3-0-0-0.dal-64cb-1a.ntwk.msn.net [207.46.43.2
    34]
     11    37 ms    37 ms    38 ms  xe-4-0-2-0.sn1-96cb-1a.ntwk.msn.net [207.46.43.2
    37]
     12     *        *        *     Request timed out.
     13     *        *        *     Request timed out.
     14     *        *        *     Request timed out.
     15     *        *        *     Request timed out.
     16     *        *        *     Request timed out.
     17     *        *        *     Request timed out.
     18     *        *        *     Request timed out.
     19     *        *        *     Request timed out.
     20     *        *        *     Request timed out.
     21     *        *        *     Request timed out.
     22     *        *        *     Request timed out.
     23     *        *        *     Request timed out.
     24     *        *        *     Request timed out.
     25     *        *        *     Request timed out.
     26     *        *        *     Request timed out.

  • lundi 14 mai 2012 16:15
     
     

    A tracert will not tell us if you got a transparent proxy or not. As the proxy just come in play for the port 80, not the tracert.

    I the other site the tracert seem good, you seem to go on the internet on the second hop.

    Try with firefox portable to visit MS's site, just to isolate if it's a IE's site configuration error. (like not in "thrusted"'s site, but in the "not thrusted")

    else you can reset your firewall rule or put your firewall at off (http://technet.microsoft.com/en-us/library/ff428142(v=ws.10).aspx)


    MCP | MCTS 70-236: Exchange Server 2007, Configuring

  • mardi 15 mai 2012 02:52
    Modérateur
     
     Traitée

    Hi Carlos,

    The tracert result show DNS and connection work normal. The issue looks so weird.
    In addition to Yagmoth's suggestion, please try solution listed below. Hope it helps you.
    1. Clean windows/IE temp file and clean boot your system
    http://en.kioskea.net/faq/4835-cannot-open-the-microsoft-website

    2. Install Microsoft Safety Scanner or other Antivirus software (download via other computer) and run full scan
    http://www.microsoft.com/security/scanner/en-gb/default.aspx
    http://www.techsupportforum.com/forums/f10/cannot-open-microsoft-web-pages-355021.html

    3. Change the router/switch port or change the router/switch MTU settings
    http://www.indiabroadband.net/mtnl-broadband/6001-cant-open-microsoft-download-com.html

    Regards


    Rick Tan

    TechNet Community Support

  • jeudi 17 mai 2012 14:44
     
     
    Thank you Rick - I will do so and post results as soon as I can.