Sign in
 
HomeInternet Explorer 10Internet Explorer 9Internet Explorer 8Previous VersionsLibraryForums
Internet Explorer TechCenter >
> 
> 
Non www sites no longer working with IE8 or IE9 i.e. cisco.webex.com,

Answered Non www sites no longer working with IE8 or IE9 i.e. cisco.webex.com,

  • Tuesday, July 10, 2012 4:04 PM
     
     
    Sign In to Vote
    0

    I can get to sites that start with www such as www.microsoft.com. I cannot get to sites that do not start with www such as cisco.impac.com

    I cleared all history, ect. Reset IE to default settings. Still dosen't work. I upgraded to IE 9 still same issue.

    I loaded firefox and it works perfectly. I can get to www.cisco.com and cisco.webex.com.   Any ideas how to fix this issue in IE 9?

    Is this a redirector issue? No virsus present or Malware. Any ideas?

    Dave Santel

     

All Replies

  • Tuesday, July 10, 2012 7:02 PM
    Answerer
     
     
    Sign In to Vote
    0

    I cannot get to sites that do not start with www such as cisco.impac.com

    Do you have a lookup for that host name?   FWIW my DNS does not, e.g. as seen via nslookup.   So that would explain your symptom.


    ---

     
  • Tuesday, July 10, 2012 7:06 PM
     
     
    Sign In to Vote
    0

    I do have lookups. So I don't have a DNS issue. Its browser based I think.

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\dsantel45>cd\

    C:\>nslookup cisco.webex.com
    Server: file.ccc.local
    Address:  10.1.4.

    Non-authoritative answer:
    Name:    global-nebulaac.webex.com
    Address:  66.114.168.212
    Aliases:  cisco.webex.com
              nebulaac.webex.com


    C:\>nslookup impac.webex.com
    Server:  file.ccc.local
    Address:  10.1.4.

    Non-authoritative answer:
    Name:    global-galaxyb9.webex.com
    Address:  209.197.193.204
    Aliases:  impac.webex.com
              galaxyb9.webex.com


    C:\>

    Dave Santel

     
  • Wednesday, July 11, 2012 3:57 AM
    Answerer
     
     
    Sign In to Vote
    0

    C:\>nslookup cisco.webex.com

    Non-authoritative answer:
    Name:    global-nebulaac.webex.com
    Address:  66.114.168.212
    Aliases:  cisco.webex.com
              nebulaac.webex.com


    C:\>nslookup impac.webex.com

    Non-authoritative answer:
    Name:    global-galaxyb9.webex.com
    Address:  209.197.193.204
    Aliases:  impac.webex.com
              galaxyb9.webex.com

    So the first one you gave us and which I tested was a typo for one of those?

    BTW notice that the ones you are displaying are aliases so they don't immediately show an IP address to IE, e.g. in particular they would not be fully cached in the dnscache.   Use  ipconfig  /displaydns   to see this  and  ipconfig  /flushdns  before your test so its clear what changes occurred due to IE's lookup.   

    If necessary you could use  ping -n 1  -w 1   to preload complete lookups in the dnscache for IE, to prove that DNS is not the issue.  Doing that could also give you a workaround if it avoids your problem symptom.   You could also try the reverse, using IE to start with the canonical host name.   However, the response of the server when you try that can be unpredictable.

    For example, the last one redirects to a 404 page:

    http://global-galaxyb9.webex.com/dispatcher/dispatcher.do?

    Hmm...   the Time To Live  of those entries is very small so to get any advantage of this technique you might have to automate it, e.g. using a cmd file.


    FYI


    Robert
    ---


     
  • Thursday, July 12, 2012 6:57 AM
    Moderator
     
     
    Sign In to Vote
    1

    Hi,


    Firstly, please let us know the following:


    1. Did the issue occur previously?

    2. What is your network environment, home or domain?

    3. Had you changed some settings before the issue occurred?

    4. Is there any error message?


    Meanwhile, based on my research, please try the following:


    1. Run Internet Explorer (No Add-ons) Mode and see how it works.

    2. Boot into Clean Boot Mode and test the issue again.


    If issue persists, please use Fiddler to troubleshoot the issue.


    Note: The third-party product discussed here is manufactured by a company that is independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's performance or reliability.

     

    Hope this helps.

    Jeremy Wu

    TechNet Community Support

     
  • Friday, July 13, 2012 2:38 PM
     
     Answered
    Sign In to Vote
    0

    After 2 hours of troubelshooting  I realized I was wasting my time. So I spent 1 hour reinstalling Windows which fixed issue. ;-)

    Dave Santel

    • Marked As Answer by dsantel Friday, July 13, 2012 2:38 PM
    •