Not listening for incoming connections?

[CapnBry]

I left uTorrent running last night getting the Ubuntu 5.10 preview ISO and when I checked on it this morning, I had "NAT error" listed on the status bar. I checked my firewall and it was forwarding properly, but I couldn't establish a connection from outside. Netstat on that machine reports:

c:>netstat -ano | grep 3744
File STDIN:
  TCP    192.168.100.164:37671  195.122.26.66:24484    ESTABLISHED     3744
  TCP    192.168.100.164:37700  81.175.214.196:59999   ESTABLISHED     3744
  TCP    192.168.100.164:37862  86.126.62.208:6881     ESTABLISHED     3744
  TCP    192.168.100.164:37975  84.160.124.128:65011   ESTABLISHED     3744
  TCP    192.168.100.164:38063  81.203.232.12:6881     ESTABLISHED     3744

Note the lack of any socket in a LISTENING state. I have my settings set to:

Listen on port 63001

Use a random port unchecked

Use UPnP unchecked

I don't know if there was a problem binding the port when uTorrent was started or if it stopped listening for some reason (although I seriously doubt the latter). For giggles, I closed uTorrent and opened my own listening socket on 63001 and restarted it. It did not complain at all about the ADDRINUSE error it should have gotten when binding the listening port. I stopped my listener and after an hour, I have yet to see uTorrent re-attempt binding to the local socket.

Is there a message I should be getting in the network area of the status bar that would indicate I have no listener? Should uTorrent try to listen again later if the local port is in use when it first starts?

[ludde]

Currently uTorrent doesn't give any indication except NAT error if the port couldn't be opened. I'll add a message in the status bar.