I tested this on Windows 98 SE, which in my case was running on a small
lan, with all packets going through a NetBSD gateway. After typing
shell://, I get the "Page Cannot be Displayed" (obviously), and as Alex
Schuetz said, about 30 minutes later, a reboot was needed because I could
not access the outside. It still does this about every half hour, even
after reboot. Just a confirmation.
Erik Tayler
14x Network Security
http://www.14x.net
On Sat, 3 Jun 2000, Alex Schuetz wrote:
> Dear people,
>
> I just dipped deeper into the "shell://" problem using _Windows98_
> instead of WinNt/2k. For me, it causes endless problems. After exactly
> 30 minutes of operation, Win98 started to block every TCPIP packet,
> every ping from my host resulted in an immediate "Error 10050" (whatever
> that is). No packet goes in or out alive.
>
> Trying to reproduce the error sooner by pushing forward the local time
> (DOS command.com box, "time" command) after rebooting didn't help to
> make the error occur "sooner". Since I tried out the "shell://" pattern
> the first time, now I'll have to pray every 30 minutes that the @#!
> computer will please,please keep sending/receiving my internet packets.
> Oh, shit....
>
> I also found out there were some remains in the (run/runonce/runonceEX)
> registry from a firewall called ZoneAlarm. Maybe the bug somehow
> triggered these remains to block everything every 30 minutes. It's just
> a theory. But I'll keep you up to date as soon as I find out more.
> Comments welcome.
>
> Dazed and confused,
>
> Alex
>
Received on Jun 03 2000
Intro
