Once I uninstalled PGP and reinstalled PGP Freeware without the VPN option,
Ethereal worked fine... I don't have any errors to post since the machine
basically rebooted...
David
----- Original Message -----
From: "Guy Harris" <gharris@xxxxxxxxx>
To: "David Nemeth" <dnemeth77@xxxxxxxxx>
Cc: <ethereal-users@xxxxxxxxxxxx>
Sent: Thursday, March 07, 2002 4:10 AM
Subject: Re: [Ethereal-users] Win98 SE, Ethereal & PGP Freeware v6.5.8 by
Network Associates
> On Wed, Mar 06, 2002 at 10:10:04PM -0600, David Nemeth wrote:
> > It seems that after installed the PGP Freeware software, anything I
click on
> > "Capture" menu my PC does some rather unusual things (video streaks
etc.)
> > then just reboots abrubtly. No GPF, no blue screen nothing...
> >
> > I'm running on an AMD 1600+, 512MB of RAM,
> > have a 3C905B-TX Nic which worked yesterday... until I installed PGP
> > Freeware v6.5.8 and tried to use Ethereal 0.9.1
> > I can open & close Ethereal. I think its due to the new adapter PGP
Freeware
> > installed called:
> > PGPNet Virtual Private Networking driver
>
> It could be. There have been other problems reported with PGPNet:
>
> http://netgroup-serv.polito.it/winpcap/misc/faq.htm
>
> "Q-10: When I capture on Windows in promiscuous mode, I can see packets
> other than those sent to or from my machine; however, those packets show
> up with a "Short Frame" indication, unlike packets to or from my
> machine. What should I do to arrange that I see those packets in their
> entirety?
>
> A: In at least some cases, this appears to be the result of PGPnet
> running on the network interface on which you're capturing; turn it off
> on that interface."
>
> so perhaps the PGPNet driver just doesn't work well with the WinPcap
> driver.
>
> Try downloading and installing WinDump:
>
> http://netgroup-serv.polito.it/windump/
>
> Then run it from an MS-DOS Prompt window (or a Command Prompt window, or
> whatever the heck they call it in Windows 98; I've managed to avoid
> using Windows OT very much - my home machine's Windows partition has NT
> 4.0, and my machine at work has NT 5.0^H^H^H^H^H^HWindows 2000) with the
> "-D" flag, and then try running it with each of the capture devices it
> listed when the "-D" flag was used (they'll be listed with numbers - you
> can just specify the number to the "-i" flag).
>
> If it crashes when capturing on any of them, note which ones it crashed
> on, and then report the problem to the WinPcap developers:
>
> winpcap@xxxxxxxxxxxxxxxxxxxxxxx
>