I'm doing wireless TCP connections in an app. The user must have the ability to choose their network adapter so they can ensure their wireless adapter is selected. I can then specify the adapter for winsock to use by doing:
Winsock.Bind 0, IPofAdapter
This seems like it works ok (at least there are no errors), however, if I then switch to a different adapter and call again:
Winsock.Bind 0, IPofAdapter2
I get an "Invalid Argument" error code 10022. What am I doing wrong?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Two things (dont have VB here with me at the moment so can't doublecheck), but:
1. Have you 'unbound' the existing connection? (if thats possible). Try also closing the winsock connection, i.e., winsock1.close, etc.
2. If it assigns it to a random port, its possible when you try to rebind it it is using the same 'random' port number (you know how great ms's random number generators are sometimes). Perhaps pick your own random port and bind it there, or pick something that is highly unlikely to be in use.
I was just posting this and about to request a refund when I got an email notif saying someone posted a new comment. Since you reference the issue, I'll give you the points. Here is what I was about to post:
Found out that you must close the socket even though the state of the socket indicates there is no connection after doing a Bind. In my socket disconnection routine, which I was calling before calling Bind again, I would check the state of the socket and if it was open, or connected, to perform a disconnect. I had been assuming all along that this was just fine. However, I did some debugging and noticed that if I only performed the Bind method, and did not explicitly connect to the remote port, that the state property still indicated 0 (default/closed), and thus the CloseSocket method was never invoked. As a test, I ignored the checking of the state, and just called CloseSocket regardless of the state of the socket, and sure enough, the Bind method then worked on subsequent calls.
I don't think that was the case, because on subsequent calls, if I changed 0 to some random port chosen by me, I still received the error. I don't think it was a port conflict, but rather just an issue with winsock itself. One might think that calling Bind would, by default, inform winsock to release the previous port it was bound to. That was my train of thought. Apparently, though, MS developers believed that one should have to explicitly release that bound port by performing a disconnect before attempting to bind to a different port. At least, I would have hoped, they would indicate a changed state in the control, because otherwise, as I found out, there was nothing telling me otherwise.
Business Accounts
Answer for Membership
by: BarthaxPosted on 2005-10-03 at 09:19:12ID: 15007588
10022 is an "Invalid arguement" error - suggesting that one or more of the parameter(s) given is incorrect.
As port 0 doesn't actually exist, I'd expect that to be the error - try a different (much higher) port number, say around the 10000 region as a test.
Additionally, are you confirming that the IPofAdapter2 exists prior to attempting the bind?