Error 10022

Posted by CM on Thu 20 Jan 2005 02:29 AM — 11 posts, 43,010 views.

CM Thu 20 Jan 2005 02:29 AM #0

Unable to connect to "place", code = 10022 (Invalid argument)

I've recently upgraded to 3.65 in hoping it would rectify the same problem I had in 3.42. Doesn't seem to be working. Neither did turning off firewalls.

Flannel USA Thu 20 Jan 2005 03:45 AM #1

What IP/Port are you trying to connect to?

Post that bit of the world file (make sure to edit out password, and actuall, you only need the few options that have to do with the connection), if you don't mind.

Faux United Kingdom Thu 20 Jan 2005 12:18 PM #2

Posting the contents of File\Windows Socket Information.. and details about what Operating System you are using might be helpful, too. :)

Faux United Kingdom Fri 21 Jan 2005 03:36 PM #3

Okay, I know everyone with programming knowledge is going to have a go at me now, but I've (recently) heard this being caused by the target machine having ISP problems.

Any progress, CM?

David Haley USA Fri 21 Jan 2005 03:42 PM #4

I don't think so. According to pages such as http://support.ipswitch.com/kb/WSK-19980714-EM09.htm, the problem is a local one, before even trying to establish a connection. It means that you gave invalid arguments to a Winsock function. Perhaps the address wasn't typed in correctly, e.g. had invalid characters.

Faux United Kingdom Fri 21 Jan 2005 04:50 PM #5

*sobs quietly*

It happened, okay? For about 100 peopleish, and again (on another mud) for about.. well. all 4 of us :)

David Haley USA Fri 21 Jan 2005 05:09 PM #6

Oh, definitely, sometimes connection problems can be due to that. :P I was just saying that in this particular case, unless Winsock is on crack (hmm...) it seems to be a local issue, not remote.

Faux United Kingdom Fri 21 Jan 2005 07:34 PM #7

Heheh, also as a point, I have a cracked version of winsock on my pc because winsock xpsp2 is stupid.

Also because VB6 on winxpsp2 doens't register license info probalerly, even though I own the full verison, so I had to crax0r it. Stupid m$oft.

And I'll disagree with you.. just because winsock replies quickly dones't mean the ips isn't telling you that it's not a valid class a block. Which is what was happening with the isp.
I have no idea how, but it was becuase they were doing "maintinaince".. this would result in a non-valid ip address. I think :p

-- Faux the serverely drunk :P

David Haley USA Fri 21 Jan 2005 10:45 PM #8

Quote:
just because winsock replies quickly dones't mean...

It's not an issue of Winsock replying quickly... it's an issue of the error number Winsock gives you. 'Invalid arguments' means it couldn't figure out what to do with what you gave it, not that it failed to perform a valid operation.

I wasn't aware that Winsock needed to be 'registered', by the way. :-) Are you saying that you cracked it to not have to pay for it?

Poromenos Greece Sat 22 Jan 2005 01:07 AM #9

She probably means the 60 connection fix patch. In SP2, each program can't have more than 60 (?) connections, and there's a patch to "fix" that.

Faux United Kingdom Sat 22 Jan 2005 05:56 AM #10

Quote:
She probably means the 60 connection fix patch. In SP2, each program can't have more than 60 (?) connections, and there's a patch to "fix" that.

Quote:
It's not an issue of Winsock replying quickly... it's an issue of the error number Winsock gives you. 'Invalid arguments' means it couldn't figure out what to do with what you gave it, not that it failed to perform a valid operation.

No, no, no, no, no. NO. *sobs again*

Quote:
I wasn't aware that Winsock needed to be 'registered', by the way. :-) Are you saying that you cracked it to not have to pay for it?

You have to have purchased visual studio (which I did) to use the winsock ActiveX control in VB. Apparently.
After I upgraded to XP, it stopped letting me use it (the winsock activex control, among others), so yes, I cracked the ... thing. :p