none
getting errors in last couple of days posting to msdn RRS feed

  • Question

  • Hi.  More often than not, I'm getting errors posting to msdn in the last couple of days.   A big yellow block appears in both IE and Chrome saying "This Page Cannot be Displayed".  My last one in the ssis forum.  Is this a problem on our side or MS's side?

    db042188

    Thursday, May 9, 2013 3:23 PM

Answers

  • It seems like an error caused by your ISP.
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
     
    Hi. More often than not, I'm getting errors posting to msdn in the last couple of days. A big yellow block appears in both IE and
    Chrome saying "This Page Cannot be Displayed".
     
     
    Friday, May 10, 2013 2:09 AM
  • its only on msdn forums.

    I agree with Alexis.   An example would be a deficient DNS.   Where do you get your DNS?   I'm surprised that you have a problem with Chrome too though.   Usually that is the workaround.   I never know whether that is because Chrome uses its own DNS or somehow is more tolerant of too long lookups.

    BTW the Find a forum tool does not recognize SSIS.   I was only able to find it by searching Forum threads

    http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/threads

    Anyway if you do an  ipconfig  /displaydns  after trying to open that you will probably see nothing but CNAME records, e.g. in particular no A(record) for an IP address to be used.

    If instead I do only an  nslookup  and then try to open the IP address that shows I get redirected here:

    http://www.microsoft.com/en-us/default.aspx

    So with problem symptoms such as yours what I usually suggest is using ping -n 1 -w 1  to ensure that a complete lookup is loaded in the dnscache for your browser to try to use.   And in this case you will have to work quickly because the Time to Live values are quite small.   E.g. the biggest I saw was 15 seconds.

    In this case, just pinging the host we want found its canonical host and then I was able to ping that to get one with the IP address.   So you could probably get away with just typing the two ping commands and reusing them with CursorUp, then quickly switching to an IE window.  Otherwise you may have to construct a cmd file script to do all the steps, including launching the browser with the correct URL specified.

    Note that the IE Network troubleshooter will not help with this scenario, since all it does is ensure that there is a lookup.  In particular it does not do anything about loading the dnscache with an A record.   The troubleshooter normally does help when CNAME records are not involved.

     
    FYI

     
    Robert Aldwinckle
    ---

    Friday, May 10, 2013 2:12 PM
  • In case it matters, I am always already in the forum replying when the error occurs.

    In that case supposedly IE caches the lookup and does not even do another one, so if a real lookup should have been done instead, that would be a different issue.   E.g. IE might be using an IP address which it would not otherwise.   Your network guys could use a protocol analyzer such as NetMon or Wireshark to find out if that is what is happening.  Or there may be sufficient clues at just the HTTP level in which case you could use IE Developer Tools' Network Capture to look at those yourself.
    Friday, May 10, 2013 9:59 PM

All replies

  • Which browser you're using? I'm using Google Chrome and don't see this problem. Also, have you re-started your PC and scan for viruses?

    For every expert, there is an equal and opposite expert. - Becker's Law


    My blog

    Thursday, May 9, 2013 5:04 PM
    Moderator
  • problem in both chrome and ie.  We have automatic virus scans here so doubtful there is a virus.

    db042188

    Thursday, May 9, 2013 6:05 PM
  • It seems like an error caused by your ISP.
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
     
    Hi. More often than not, I'm getting errors posting to msdn in the last couple of days. A big yellow block appears in both IE and
    Chrome saying "This Page Cannot be Displayed".
     
     
    Friday, May 10, 2013 2:09 AM
  • its only on msdn forums.

    db042188

    Friday, May 10, 2013 12:35 PM
  • its only on msdn forums.

    I agree with Alexis.   An example would be a deficient DNS.   Where do you get your DNS?   I'm surprised that you have a problem with Chrome too though.   Usually that is the workaround.   I never know whether that is because Chrome uses its own DNS or somehow is more tolerant of too long lookups.

    BTW the Find a forum tool does not recognize SSIS.   I was only able to find it by searching Forum threads

    http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/threads

    Anyway if you do an  ipconfig  /displaydns  after trying to open that you will probably see nothing but CNAME records, e.g. in particular no A(record) for an IP address to be used.

    If instead I do only an  nslookup  and then try to open the IP address that shows I get redirected here:

    http://www.microsoft.com/en-us/default.aspx

    So with problem symptoms such as yours what I usually suggest is using ping -n 1 -w 1  to ensure that a complete lookup is loaded in the dnscache for your browser to try to use.   And in this case you will have to work quickly because the Time to Live values are quite small.   E.g. the biggest I saw was 15 seconds.

    In this case, just pinging the host we want found its canonical host and then I was able to ping that to get one with the IP address.   So you could probably get away with just typing the two ping commands and reusing them with CursorUp, then quickly switching to an IE window.  Otherwise you may have to construct a cmd file script to do all the steps, including launching the browser with the correct URL specified.

    Note that the IE Network troubleshooter will not help with this scenario, since all it does is ensure that there is a lookup.  In particular it does not do anything about loading the dnscache with an A record.   The troubleshooter normally does help when CNAME records are not involved.

     
    FYI

     
    Robert Aldwinckle
    ---

    Friday, May 10, 2013 2:12 PM
  • I'll ask my network guys to interpret but this sounds like a big hassle taht I've never had to deal with in yrs of using the forum.  Will post back here.  In case it matters, I am always already in the forum replying when the error occurs.  No proof but it might be just in the ssis forum.   Also got the sense that smaller replies had a better chance of working.

    db042188

    Friday, May 10, 2013 2:29 PM
  • In case it matters, I am always already in the forum replying when the error occurs.

    In that case supposedly IE caches the lookup and does not even do another one, so if a real lookup should have been done instead, that would be a different issue.   E.g. IE might be using an IP address which it would not otherwise.   Your network guys could use a protocol analyzer such as NetMon or Wireshark to find out if that is what is happening.  Or there may be sufficient clues at just the HTTP level in which case you could use IE Developer Tools' Network Capture to look at those yourself.
    Friday, May 10, 2013 9:59 PM