Repeater is leaving ports open.

[cynagen]

Repeater is leaving ports hanging open on CLOSE_WAIT. We're running it on a server (this is for our tech support business), but it's leaving ports hanging open (and we have craploads open already), so I fear it's causing the TCP/IP stack in the repeater to crash thus dropping all active connections and preventing new ones. Is there a fix for this, can anyone possibly tell me how to resolve this by setting some sort of shorter wait time, like say, 5 seconds?

[bevtech]

what version of the repeater are you using???

[cynagen]

1.1.0.7 i believe

[redge]

if you have vncviewer.exe -listen and winvnc.exe running on same computer hosting repeater.exe
you should have port forwarding 5501 and 5901 and not 5500 and 5900

you can use port 5900 and 5500 only if you have no ultravnc server and no ultravnc viewer on the computer running repeater.exe

[cynagen]

That's not the case at all. We have a single Win2k3 server running the repeater as admin, ports are standard 5901 and 5500 (as per default settings in repeater). We have port forwarding to outside, 11000->5500, and 11001->5901, but since we're in the office, we use 5901, (if we were working from home we use 11001.) Now, what appears to be happening, is we're getting ports hanging open from the client port 5500, 11000 to the internet, which are causing the repeater to no longer take incoming from internal or external ports.

[redge]

nat rule bad nework router firmware or is just happen to repeater ?

[cynagen]

nat rule bad nework router firmware or is just happen to repeater ?

NAT is disabled (net admin doesn't want servers and shit running, helps deter this), i doubt a 1 year old cisco router has gone bad, it just seems to be the repeater. we had it on an older machine before it was put on this server class machine, and it was having the same problems, just more often. my boss is yelling at me that we shouldn't have a dedicated server with custom written software to monitor it just to keep it running, but it's looking like we might end up having to either ditch it, or if somebody can fix it so it drops ports after 5 minutes of not receiving anything and cancelling the CLOSE_WAIT then we'll be saved from a repeatedly dying repeater.