VB and WinSock

VB and WinSock

Winsock with VB works fine if I specify a port (e.g., 1001). However when I set the Winsock’s port (local and remote) properties to 0 so that they would be dynamically chosen, it doesn’t work (The protocol used is TCP). Why?

I will assume that you are using the Winsock Control that ships with VB and not writing to the API. The ports are dynamically assigned when you issue the Listen command. I cannot remember any bugs in the past that would effect you in performing this. If you can post some of your code that would also be helpful.


Share the Post: