The problem is quite strange since the winpcap driver has nothing to do with sockets. Another strange fact is that the behavior occurs after 20 minutes: driver problems (like the ones with dial-up connections, that are similar to your one) usually show up as soon as you start the capture. Do you experience the same problem with windump? If yes, do you receive any error?
Loris > Hi there, > > We have been using winpcap 2.3 for a longtime now; both on NT, 2000,98 and > XP without any major problems. > Recently however running on my: > > Microsoft Windows XP Professional, Version 5.1.2600 Service Pack 1 > Build 2600 > > The npf.sys driver, (I think it must be that one) seems to eat up all my > socket connections, after a 20 minuttes stress test on my network card. > After that I cannot connect to either the internet or my database. As soon > as the application using the driver is shutdown, everything works okay > again. > > I suspect that it might have to do with one of the recent updates to XP > since the application is running smoothly on an unpatched XP. I've also > tried with the 3.0 alpha winpcap same bad results, and I've even tried with > Ethereal an anylyzer program using winpcap, which also shuts down my > internet connection. Ethereal says something like not enough kernelbuffer. > > Any help gladly appreciated. > > > Regards > Henrik > > ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ==================================================================
