Net_SendPacket Error: WSAEINTR
Wiggles
Join Date: 2003-05-13 Member: 16253Members, Constellation
Join Date: 2003-05-13 Member: 16253Members, Constellation
in Tech Support
<div class="IPBDescription">fappage</div>NS will run for about 30 - 40 seconds with the expected ping for whatever server I attempt to play on. After this time my ping starts spiking to the 1000's followed by large amounts of CL_flushentitypackets and finally HL.exe shutsdown and comes up with an delightful little box saying Net_SendPacket Error: WSAEINTR. Normally followed by me throwing my mouse at the screen.
I've googled the error, and tried all the usual fixes that seem to have worked (e.g ending QoS, checking vchace etc) but none of them works. I have also tried numerous different rates to no avail.
Any help is appreciated.
I've googled the error, and tried all the usual fixes that seem to have worked (e.g ending QoS, checking vchace etc) but none of them works. I have also tried numerous different rates to no avail.
Any help is appreciated.
Comments
Try disabling QoS packet scheduler.
Try going to 'control panel-->administrative tools-->local security policy' double click 'secure server', and untic all boxes, repeat for 'server'.
I hope it helps.
Well there was no local security policy under administrative tools (maybe because I'm using XP home?) and none came up in a search <img src="style_emoticons/<#EMO_DIR#>/sad-fix.gif" style="vertical-align:middle" emoid=":(" border="0" alt="sad-fix.gif" />
Is the shortcut line for the screen, maybe that will work.
I missed that it was under the IP section at the bottom of the left part.
What IP section where?
The IP security section in security policy is what I meant.
Try disabling the firewall just for a short time to play and see if it works. If it does try to find out what specific setting you need to disable to run the game smoothly while still getting some forewall protection (if at all possible).
Oh, and come back here with the info. I never fully figured out what I needed to change in the firewall settings to get around this.
This error has been rampant among 56k users. Valve has known about the problem and has promised the community a fix but, obviously, have not delivered.
Unfortunatly, there is no one fix to this problem (as so many people say) but I've heard <a href="http://support.microsoft.com/kb/q311077/" target="_blank">this</a> sometimes fixes it.
Make a restore point before altering settings -- never know if you may misclick.
Hope I could help.
My old computer, (now dead for unrelated reasons) had this error a <i>lot.</i> My connection speed was never up to the "full" 56k either. Usually, on a good day it would be 48.8 or something like that. (As displayed when hovering my mouse over the connection icon in the system tray.) On bad days, it'd be 36pointsomething or less. I suspect my modem was the problem because for the first time since I bought it, it was having issues connecting to the internet at all this summer. (I literally found that a ritual of unplugging the jack from the modem, trying to connect, obviously failing, replugging it in, and trying again worked every time.)
Ever since that machine died though, I've been playing on another machine in the house that is about 4 years newer. It also, being in a room near where the phoneline comes into the house, has less wire between it and the wall. The combination of a newer 56k modem and less wire seems to have all but eliminated this problem for me and a slow connection now is "52.0". It is rare for me to have this frustrating crash now. (Mostly when someone picks up the phone to try to make a call while I'm playing or something.)
The phoneline going into this house has also been suspect to me, as it is quite old and ragged in appearance. Ideally, I'd like to see it replaced, but as I say, this machine is working much better.
So, from what I've found, check the quality of the wire, make sure your modem is up to date with drivers and stuff, and maybe, try a friends machine if possible. Or swap modems and maybe a new modem may be worth looking into as well.