Quote:
Originally Posted by fowlplay4
It's possible your ISP/modem/router is interfering and closing the connection as it appears inactive which in turn causes your NC to disconnect
|
This would be my guess. The older (current) Windows RC doesn't send any kind of keep-alive packets on NC afaik. The new one (which Stefan hasn't released on Windows) does, which iirc he said fixes the issue.
Likely your router (which is doing NAT) drops the connection to NC from its translation tables after it doesn't see any activity for a while (since it thinks the connection is dead), effectively killing it. Usually you can raise this timeout ("NAT timeout") to help reduce the frequency the problem, but that depends on your router. You can observe this problem with other protocols that don't send periodic keep-alive packets (e.g. SSH, but usually you configure it with a keep-alive to avoid this very problem).
The real solution is use the new RC, but Stefan hasn't released it yet for Windows, not sure why.