cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1787
Views
0
Helpful
1
Replies

RV325 will not allow remote desktop through

rhodco9ceo
Level 1
Level 1

I recently upgraded from a LinksysWRT54GL using DD-WRT firmware (working fine - no problems) to the Cisco RV325. The problem now is that the firewall will not allow my remote desktop through encrypted tunnel to pass through to the fixed IP of my desktop PC (running CopSSH server). I have proven that the port forwards are setup correctly because I can disable the firewall completely and it works fine.

Since the problem is narrowed down to the firewall, I have tried every possible combination of options provided in the GUI for the RV325 but nothing works while the firewall is enabled. I have created access rules to allow the two ports I'm forwarding to the PC to have anytime access from any source, but it still does not work until I disable the entire firewall. Can anyone explain this? My previous router had no problems with this. I am using the exact same ports, same Putty client, same ISP, the problem seems confined to the firewall.

The specific symptoms are as follows: I can launch the PuTTy client and the remote desktop responds in a command prompt window asking for username. I give username and it responds with a prompt for the password. It accepts password and replies with last login date/time/ect. This is normally the point where I launch the Windows Remote Desktop client using "localhost:3399" as the destination address. It usually prompts me for my Windows username and password, then I'm in. But now with the RV325, it times out with error "cannot connect to the remote computer". I can disable the firewall at this point, try again, and it connects.

The mystery is why I can connect to the CopSSH server and authenticate, but I cannot establish the subsequent Remote Desktop Session within this tunnel like I could before. How can the firewall be blocking this?

 

1 Reply 1

rhodco9ceo
Level 1
Level 1

I finally figured out the solution. I had to create a firewall rule that would allow any WAN traffic to PING my internal fixed IP address using port 0. That did it.

 

Review Cisco Networking for a $25 gift card