Category Archive 'Volokh Conspiracy'

10 Apr 2007

Volokh Address Working Again

, , ,

Yesterday, I followed up a link from Glenn Reynolds and discovered that the conventional Volokh Conspiracy url: was working just fine again.

Last month, it was impossible to access that eminent legal blog using that address from several East Coast computers. My theory was that someone with a grudge against that blog had distributed a Trojan which overwrote that address in the Hosts File. I was planning to edit my Registry one of these days to fix the problem, but then Glenn Reynolds mentioned hearing about the problem, and identified an alternative working URL:, eliminating the need to go to all that trouble.

I’m glad the issue is gone, but I wish I knew what really happened.

19 Mar 2007

Volokh Conspiracy Access Problem

, , , , , ,

On March 14 I reported finding it impossible for several days, since around March 10 or 11, to access the Volokh Conspiracy Blog at its conventional address:

Clearly, my experience with this problem is not unique, since Glenn Reynolds blogged about this yesterday (March 18).

Professor Reynolds kindly supplies a solution which saves all of us affected the necessity of logging into our computers in Safe Mode and searching the Registry for a corrupted Host file.

All one needs to do is use Volokh.Powerblogs.Com instead.

Hat tip to Walter Olson.

14 Mar 2007

Volokh Conspiracy Hijacked by Trojan

, , , , , , ,

Last Saturday, I clicked on an Instapundit link to a Volokh posting, and got the traditional MS Explorer negative page-not-found response.

The page cannot be displayed

The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.

Even important blogs have technical difficulties, so I simply shrugged and made a mental note to try again later.

But when the problem was still there on Monday, I concluded there was more to this than meets the eye.

About a year ago, my personal computer was infected by a Trojan, which exploited one of those only-too-numerous Microsoft vulnerabilities. It was the sort of thing which hijacks your computer to send out thousands of replications of itself covertly, degrading system performance significantly in the process.

I would never have known it was there, but for the fact that I could no longer log into Norton to update my antivirus software. The Trojan wrote to my Host file instructions directing all prominent antivirus website addresses to a dead address.

Wikipedia discusses this kind of hijacking technique in its Host file entry.

Further investigation established that my wife’s notebook was blocked from Volokh Conspiracy by the same malware. But a friend in California last night was not impacted by this problem.

I don’t recall exactly which file needs to be edited, but I can tell you that correcting this kind of problem is a lot of work. One has to turn off System Restore, reboot the computer in Safe mode, then edit the Registry to get rid of the illicit Host file entry. Entering Safe Mode is a bummer for me, because it will mess up all the icons on desk top, producing even more work sorting them all out again.

Would readers please check to see if they can link to Volokh Conspiracy, and tell me via email, or in Comments here, if they are also experiencing the same problem?

27 Apr 2006

Juan Non-Volokh Identity to be Revealed


Readers are being invited to post their guesses.


Hat Tip to Brian Hughes.

Your are browsing
the Archives of Never Yet Melted in the 'Volokh Conspiracy' Category.

Entries (RSS)
Comments (RSS)
Feed Shark