Thread: RC Help
View Single Post
  #15  
Old 03-13-2013, 09:34 PM
fowlplay4 fowlplay4 is offline
team canada
fowlplay4's Avatar
Join Date: Jul 2004
Location: Canada
Posts: 5,200
fowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond reputefowlplay4 has a reputation beyond repute
Quote:
Originally Posted by DazJenova View Post
I don't have one set up, does anyone know the ports for RC possibly could port forward it to see if there's any connection issue?
Port forwarding won't do anything because it's an outbound connection. The ports RC and NC uses are also different per server. I'm pretty sure this is related to NC disconnecting/reconnecting because the RC doesn't 'ping' or receive data to keep the NC connection alive.

With your RC connected, open a command prompt and do: netstat -a -b

You'll eventually see RemoteControl2.exe listed and it will show the port it's using. The bigger port number is typically the NC.

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, a VPN could alleviate this issue.
__________________
Quote:
Reply With Quote