This error is killing some great matches
Jittles!
Join Date: 2009-07-09 Member: 68090Members
Join Date: 2009-07-09 Member: 68090Members
in Tech Support
I'll be in the middle of a frantic game, killing heaps of stuff and what not, then I get quit out of HL and this error comes up:
NET_SendPacket ERROR: WSAEINTR
Before yesterday this had only happened about twice over 4 or so months I've been playing recently, but in the last 2 days it's happened at least 3 times. I've had a quick look around to see if anything helps, but it all refers to XP and updating it (I'm running Vista32). Anyone have any idea how I can resolve this? Many thanks for any help.
NET_SendPacket ERROR: WSAEINTR
Before yesterday this had only happened about twice over 4 or so months I've been playing recently, but in the last 2 days it's happened at least 3 times. I've had a quick look around to see if anything helps, but it all refers to XP and updating it (I'm running Vista32). Anyone have any idea how I can resolve this? Many thanks for any help.
Comments
<!--quoteo--><div class='quotetop'>QUOTE </div><div class='quotemain'><!--quotec-->This error is:
WSAEINTR (10004) Interrupted function call.
A blocking operation was interrupted by a call to WSACancelBlockingCall.
If you receive the following error: NET_SendPacket ERROR:WSAEINTR this is typically caused when your computer is already using the default client port 27005.
This solution might help for other types of WINSOCK errors as well.
Possible Causes:
1. Bad Winsock dll
2. Bad TCP/IP stack
3. Conflicting Ports
Try adding this to the end of your launch properties:
+clientport 27025
4. Firewall
5. ICS
6. VIA KT133A motherboard chipset w/o proper 4-in-1 patch<!--QuoteEnd--></div><!--QuoteEEnd-->
btw: ...some time ago i got this:
NET_SendPacket ERROR: NO ERROR
:D