socket prgm-Error

[Guest]

I tried a socket application in C#(windows XP 2002). I used 1900 port with
UDP protocal to receive msg from my client application(multi casting). The
receiving application is giving some problem.. like "Only one usage of each
socket address (protocol/network address/port) is normally permitted" . I
didn't write sending in my application ..the application only receive the
message. When I am binding the port that time i am getting this error..

I feel some service(s) may using this same port ... so that this is
happening..give me your idea to reuse the port.. to receive message.

regards,
RajaManickam

 

[Chad Z. Hower aka Kudzu]

I tried a socket application in C#(windows XP 2002). I used 1900 port
with UDP protocal to receive msg from my client application(multi
casting). The receiving application is giving some problem.. like "Only
one usage of each socket address (protocol/network address/port) is
normally permitted" . I didn't write sending in my application ..the
application only receive the message. When I am binding the port that
time i am getting this error..

I feel some service(s) may using this same port ... so that this is
happening..give me your idea to reuse the port.. to receive message.

Yes, you are using some port that another app is already using. Try running
netstat to see.


--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"

Make your ASP.NET applications run faster
http://www.atozed.com/IntraWeb/

 

[Guest]

Thanks Chad Z. Hower aka Kudzu,
I got it... we have a Socket Option ReuseAddress property to use the port
which is already accessing by other application.

By setting this property we can use the port before the OS releasing port.
It is not required to wait to release the port.

rajaManickam

 

[Chad Z. Hower aka Kudzu]

I got it... we have a Socket Option ReuseAddress property to use the
port which is already accessing by other application.

By setting this property we can use the port before the OS releasing
port. It is not required to wait to release the port.

Yes - but if another application is STILL using that port, now you have
trouble. The OS will randomly distribute connections between the two
different processes.


--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"

Develop ASP.NET applications easier and in less time:
http://www.atozed.com/IntraWeb/