sockets and Windows behavior

[John Rule]

Maybe someone can explain this...

 I noticed that when a socket (regular or datagram) is opened to Windows
(via my app that is listening on port 1901), an 'alias' port is given
instead of the 'real' one. For example, if my external device (computer,
PDA, etc.) connects to socket 192.168.77.10:1901 for communications, the
actual socket reported is a random number (like 1407), and it changes each
time the device connects (incrementally..1408, 1409, 1410).

Is this Windows or RunRev?

Thanks,
JR