Matthew Grooms mgrooms at shrew.net
Thu Jan 13 13:58:51 CST 2011

On Jan 13, 2011, at 1:13 PM, rdklotz at optonline.net wrote:

> I actually sent an email that said I have a new computer (4 months old)
> so I don't think I have an old chipset or drivers (but you never know).

Right. A newer Ethernet chipset may have a driver that is not as mature as an older, more proven driver. You can try to open device manager, right click on your Ethernet adapter to display the properties and click the driver tab. At that point, there is a update driver button. This is all from memory so I hope the instructions are accurate. 

> What I told Kevin is that I had tried to install an old cisco client vpn
> which would not install because it was for a 32-bit OS. 
> I don't know is that might have corrupted something.
> I am also using a wireless connection but it cam installed on the
> Dell computer. I have no other vpn clients installed.

Did you restore to a checkpoint after the 32 bit Cisco client didn't work out? It's possible that remnants of the Dne driver or it's bindings are still present on your computer which may cause issues with other intermediate drivers. 

> When I did a google search for the error message and shrew, I found
> some hits, though not on the latest shrew release.

The 2.1.7 version was the first to include the improved driver set. We did an immense amount of work to improve these drivers so that issues like this would be much less likely. I'm not claiming that that our drivers are perfect ( no software is ), but they are very stable.

> If there is something that is configured incorrectly on my computer
> or a driver that needs to be updated, I need a hint on how to find it.
> I don't know where to start.

What Ethernet chipset does your pc use and what driver version do you have installed?


More information about the vpn-help mailing list