Sign in with
Sign up | Sign in
Your question

Help! "Operation on a socket" error: WinXP Home SP3

Tags:
  • Socket
  • Networking
Last response: in Networking
Share
January 15, 2010 12:26:58 AM

I've been trying to understand an error for weeks now and I am at a loss to know what is wrong.

Here's what happens: After I download ~1GB of data, using ReGet Deluxe ver 4.1a with six connections (on XP home SP3), I loose all TCPIP connectivity until I reboot.

The failure begins when ReGet reports the following error:
Error #80072747(An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.) in CRgHttpSession::ConnectHttp()

If I try > IPCONFIG /all
everything looks fine.

But if I ping my machine (192,168.0.100) I get:
Ping request could not find host 192,168.0.100.

And if I > ping 172.0.0.1
I get a timeout!
Pinging 172.0.0.1 with 32 bytes of data:
Request timed out.... (x4)
Ping statistics for 172.0.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Now the REALLY wierd thing is that ping successfully resolves and connects to "localhost"
>ping localhost
Pinging 503GR [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 (x4)
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

And it also works when I use my machine's network name (503GR):
>ping 503GR
Pinging 503GR [192.168.0.100] with 32 bytes of data:
Reply from 192.168.0.100: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

But remember, Ping could not find host 192,168.0.100 by it's IP address!
One new clue...

With the most recent error, I also got an event log entry that I hadn't seen before:
Event Type: Error
Event Source: Srv
Event ID: 2019
Description:
The server was unable to allocate from the system nonpaged pool because the pool was empty.

Does anyone have an idea what is going on? I've been tracking memory, port allocations... nothing looks odd before OR after the failure. (other than Firefox consistently leaves an orphaned instance running that I discover when I reboot).

I don't know what to do, other than reinstall the OS.

Thanks in advance.
--damien

More about : operation socket error winxp home sp3

January 15, 2010 1:37:43 PM

http://support.microsoft.com/kb/822219
Quote:
This issue may occur if a non-Microsoft program that is installed on your computer uses an outdated kernel-mode filter driver.

It looks like the cause may be the software you are using. I'd suggest contacting their support to see if they have a fix.

Does this occur when downloading any other way?

Pinging 172.0.0.1 should fail. Unless I am not understanding correctly it appears you are trying to ping your loopback to check your NIC. If you look at the IP listed when you pinged localhost you will notice that it shows 127.0.0.1 which is the correct IP to test your NICs functionality. If this is a typo then this is probably due to the error caused by the software you are using.

Edit: Typo'd my typo :( 
m
0
l
January 15, 2010 2:20:02 PM

Yep. "172" was my typo. But "localhost" did ping as did the net name ("504GR"), while typing the IP for the machine (192.168.0.100) did not

I'll check out the MS knowledge base article and also try to recreate the problem without ReGet. Then I'll let you know.
Thanks for the pointers!

--Damien
m
0
l
!