About

I'm Mike Pope. I live in the Seattle area. I've been a technical writer and editor for over 35 years. I'm interested in software, language, music, movies, books, motorcycles, travel, and ... well, lots of stuff.

Read more ...

Blog Search


(Supports AND)

Feed

Subscribe to the RSS feed for this blog.

See this post for info on full versus truncated feeds.

Quote

Where is human nature so weak as in the bookstore?

Henry Ward Beecher



Navigation





<April 2025>
SMTWTFS
303112345
6789101112
13141516171819
20212223242526
27282930123
45678910

Categories

  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  
  RSS  

Contact Me

Email me

Blog Statistics

Dates
First entry - 6/27/2003
Most recent entry - 4/4/2025

Totals
Posts - 2656
Comments - 2678
Hits - 2,737,207

Averages
Entries/day - 0.33
Comments/entry - 1.01
Hits/day - 344

Updated every 30 minutes. Last: 10:50 PM Pacific


  08:12 PM

I've been getting reports from some people that when they try to see anything on my site, they're getting an error in IE "The page cannot be displayed" with the fine print "Cannot find server or DNS error."

I am somewhat at a loss as to how to debug this, because I have never experienced the problem myself. Here are some notes about what I've seen and tried.
  • Some people can see the site (like, me and people who I know who visit the site often). Other people cannot see it ever.
  • Last week sometime I installed SP1 on Windows Server 2003, which is hosting the blog you're reading. Hmmm.
  • Seeing as how this might have been a DNS thing, I had people try accessing the site using the raw IP address. That worked for one person but not for another person. How weird is that?
  • I disabled the Windows Server 2003 firewall. No change.
  • One thought I've had is that people can get to the site if they visited it before the SP1 upgrade. Could that be? Is there something persisted somewhere (like, in their browser) that's allowing them access?
  • One site suggested using the Windows "repair" command on the server's network connection. Tried that, no change.
  • GRC.com's ShieldsUp probe can apparently see the server ok.
Some things I guess I could try:
  • Have non-successful people try just pinging the server to see if it's connectivity or the Web server.
  • Uninstall SP1. I'd rather not do that, of course.
What else? Any ideas?

[categories]  

[2] |