VB Controls, Winsock error "Address in Use"

Winsock error "Address in Use"

Author	Message
s_mohanku.. #1 / 3	Winsock error "Address in Use" I've written asimple program using TCP in VB6 to transmit whatever I type on one machine, to another. I had assigned the port no 1005. It works fine for some time. after a few executions it starts saying "Address in use". I then have to change my port address to make it run. the same thing happens again until I change the port no. again. Sent via Deja.com http://www.--*.com/ Share what you know. Learn what you don't.
Sun, 13 Jan 2002 03:00:00 GMT

MSnew #2 / 3	Winsock error "Address in Use" I remember having the same trouble. tcp instantiates as client / server communication. Gennerally, the calling app becomes the server and maintains the connection. For reasons I didn't care to study further, problems arise when the client / server connection is not closed properly or an attempt to reverse the client / server roles of the two machine occures. The reason I did not study it further is because the TCP control that comes with VB also supports UDP. This is a connection-less communication protocol and does not have the same problems you are encountering. Useing it is similar to useing TCP so you will not have much trouble adapting your application to use it. (I used it to do exactly what you are doing by the way). Quote: > I've written asimple program using TCP in VB6 to transmit whatever I > type on one > machine, to another. I had assigned the port no 1005. It works fine for > some time. after a few executions it starts saying "Address in use". > I then have to change my port address to make it run. the same thing > happens again until I > change the port no. again. > Sent via Deja.com http://www.deja.com/ > Share what you know. Learn what you don't.
Mon, 21 Jan 2002 03:00:00 GMT

John Vaccar #3 / 3	Winsock error "Address in Use" I'm not sure I understand the question correctly, but if you are getting that error after you stop execution of your app and restart it again, then set the Winsock control's LocalPort property to '0' before you exit the app so it resets the port. This same problem was an expensive tech support answer from Microsoft. Later....john Quote: > I remember having the same trouble. tcp instantiates as client / server > communication. Gennerally, the calling app becomes the server and maintains > the connection. For reasons I didn't care to study further, problems arise > when the client / server connection is not closed properly or an attempt to > reverse the client / server roles of the two machine occures. > The reason I did not study it further is because the TCP control that comes > with VB also supports UDP. This is a connection-less communication protocol > and does not have the same problems you are encountering. Useing it is > similar to useing TCP so you will not have much trouble adapting your > application to use it. (I used it to do exactly what you are doing by the > way). > > I've written asimple program using TCP in VB6 to transmit whatever I > > type on one > > machine, to another. I had assigned the port no 1005. It works fine for > > some time. after a few executions it starts saying "Address in use". > > I then have to change my port address to make it run. the same thing > > happens again until I > > change the port no. again. > > Sent via Deja.com http://www.deja.com/ > > Share what you know. Learn what you don't.
Mon, 21 Jan 2002 03:00:00 GMT

Page 1 of 1

[ 3 post ]