enormous amounts of bandwidth available), and I have had ensuing
problems with clients getting time-outs when connecting.
A few facts:
Computer 1 (1.Vege): Dell Dimension Precision 220 PIII 700Mhz
Computer 2 (2.Vege): Dell Optiplex GX1 PII 350 Mhz
How a client and server communicate:
1) The client sends UDP: "I am a Papyrus client" to port 32766 on server
2) The server answers, UDP "I am a Papyrus server" to port 32767 on
client with the assigned port number for the client to use
3) The client sends UDP: "I am a Papy client" to the newly assigned port
on the server, in this case 32778
4) The server responds, UDP "I am a Papy server" to port 32767, coming
from server port 32778
5) Then info on passwords, tracks and things like that is passed back
and forth between the client port (32766) and the designated client's
port on the server (32778 in this case) and connection is established
When I get time-outs, the server fails to send a new handshaking packet
from the newly assigned port, it just continues to send from the old
port (32766). After 10 tries, the client gets a "destination
unreachable". After 5 seconds of this, the client says: Time-out and
blah-blah...
It seems like the server doesn't open the port that it designated for
the client in question, and I would desperately like to know why. Is
there any setting in Windows that stops too many UDP ports to be opened
at one time? Is there any reason for the server NOT to accept the UDP
packets coming in on the designated port? I mean, the server sends out
the new port on which the client is supposed to send packets too, but
this port is closed. I would guess that the UDP port in question simply
is closed both ways.
Anyone got any idea? Randy Cassidy, for instance? Is there any way I can
make the connecting process to work smoothly? Time-out values?What
reasons can there be for the server not being able to receive
UDP-packets on the port it recently designated? How much time does a
window app need to readying reading on a new UDP port?
I'd love to find out why, because this problem has ***ed me for so
long now, and I'd love to exploit my huge connection to the benefit of
the GPL society... Now, if mr. Cassidy was here.... :-)
---Asgeir---
Observations:
The ping rates are very low, and no errors (but this is ICMP based, so
it is a different story, I know), irrespective of any server load
Once the clients get in (after sometimes inumberable failed attempts),
the connection is *very* good, and totally glitch free
Sometimes, I get in without a hitch, other times, I need to try 30
times, and I am on dial-up inside the university network...
Computer speed makes NO difference in the amounts of timeouts
Different OS's make no difference (95, 98)
Different netcards make no difference
There is no limiting or admission checking of UDP packets on the
university network