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

To be unacquainted with what has passed in the world, before we came into it ourselves, is to be always children.

— Cicero



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,735,457

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

Updated every 30 minutes. Last: 8:38 AM Pacific


  08:19 PM

In response to my whinging about the problems some people were having seeing my Windows 2003 server (which I ascribed to the SP1 update), Todd noted[1] that the Windows 2003 page suggests a couple of KnowledgeBase articles that describe similar-sounding problems:I had a look, and the overall problems sure sounded familiar, but the details were perhaps not quite there. For example, 899148 deals specifically with RPC calls involving VPN and/or ISA. This text gave me pause: "Only apply it[2] to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 that contains this hotfix." Hmm. Can't say I'm severely affected, I don't think.

Anyway, I did apply the hotfix suggested in the second KB article.

Did it work? Who knows. Two people who previously were unable to see the website now can. At least one person still cannot. As I said before, it's damn hard to debug a problem you can't reproduce yourself. So I might try the instructions in the first KB, but ... maybe I'll wait.

The good news, though, is that the spam filter I installed recently (Outlook Spam Filter 3.0) is still batting 1000. Die, spam, die!


[1] Resisting nobly, I thought, the opportunity to say "RTFReadme!"

[2] By which they mean "Apply it only," as explained here. :-)

[categories]  

[1] |