ServerSockets, their Ports, and No-Route exception
I have a deep, burning question on ServerSockets...
I have a situation where sometimes there is "No Route To Host" from a client, and sometimes there is not..
Currently, the ServerSocket is listening @ around Port 18xx or 2yyy, and I am wondering if one of the following two options exist...
1-Can you force a ServerSocket at port 80? ((Currently this is being tested with Windows 95 and a dialup))
2- What do you do when a client fails to reach a Server Socket that _is_ open?
(It currently tries _10_ times, that should be more than enough if a route to host opens up..no?)
(For example, would explicitly binding to a local address with the client-socket work/help?)
Does anybody have any ideas,
Thanks,
xiarcel@users.sourceforge.net
cxtable.sourceforge.net
[840 byte] By [
xiarcel] at [2007-9-26 1:32:04]
> 1-Can you force a ServerSocket at port 80?
> ((Currently this is being tested with Windows 95 and
> a dialup))
Remember, that only users with root/administrator priviledges can run programs which bind to ports <1024. At least on Unices and "better" Windows (NT/2000) - maybe on 95 there is similar problem? But I'm not really sure about it.
> 2- What do you do when a client fails to reach a
> Server Socket that _is_ open?
> (It currently tries _10_ times, that should be more
> than enough if a route to host opens up..no?)
Fail? Don't know what you mean... If it fails 10 times, then there probalbly IS a route problem.
Robert
Ok.... well.. bound to a port like 1700 it works one direction, and not the other... so I am basically wondering if there is some other way to do it..
((Ie, I can be the ServerSocket and my friend can connect, but ran in reverse it presents a problem...))
When you create a socket (ip,port) there is also a (ip,port,localip,localport) {the last two for bind}
Could that help?
~Dave
