Cisco RV130W and RDP

Toggle sidebar Toggle sidebar
Q

quxote

Distinguished
Jan 14, 2010
34
0
18,530
I just got a new Cisco RV190W and I am trying to set it up so one of the computers can be connected via Remote Desktop.

I set the computer as a static IP address in the Static DHCP section.

I tried forwarding 3389 TCP and UDP in both the single port and port range port forwarding settings (i tried each one separately and both at the same time).

To test I even put the IP address as the DMZ host and I still can not connect.

I can connect if I am on the same network but not over the internet.
 
Solution
B


Good idea, if you have a consumer/residential grade connection, they often block common ports for http, https, pop3, rdp, etc. Thus by using a different port and having that different port be the external port in the port forwarding and the 3389 be the internal port.
Sort by date Sort by votes
B

boosted1g

Titan
Jun 12, 2013
14,846
8
74,965
Are you typing in the computer's IP address or your public internet address? You need to use your public internet address.

In reality though this is a HUGE security concern. Windows RDP is not secure at all and opening up the default port is just asking for problems.

If this is not for commerical use then just use teamviewer.
 
Upvote 0 Downvote
Q

quxote

Distinguished
Jan 14, 2010
34
0
18,530
I am typing in the Public IP address in the RDP client.
I use very strong passwords and intend to change the default port once I can confirm the connection is working
 
Upvote 0 Downvote
Q

quxote

Distinguished
Jan 14, 2010
34
0
18,530
Also, teamview is very slow. WIth our old router RDP was woring great...I just cant get the port open on the new router. I set the Service Up, created an access rule. Can not figure out what is wrong.
 
Upvote 0 Downvote
B

boosted1g

Titan
Jun 12, 2013
14,846
8
74,965
Its not just about passwords, it is about vulnerabilities in the entire RDP of windows. It is just not secure.

Are you typing in the public IP on a local computer or a remote computer (local computer meaning it is on the same network as the computer you wish to remote to)? Most routers wont allow you to router out to its public address from the LAN.

When you go to a port checker website does it show the port as open?
 
Upvote 0 Downvote
Q

quxote

Distinguished
Jan 14, 2010
34
0
18,530
I understand the risks..thanks

I am typing the public address on a remote computer. In a local computer I can remote to it by typing the computer name.

Like i said ...RDP works fine when using the old router...so I know the computer is setup correctly. The problem is with opening/forwarding the ports on the new router.
WHen I scan the the public Ip address with the new router the port is closed. When I can the IP address with the old router the port is open

 
Upvote 0 Downvote
Q

quxote

Distinguished
Jan 14, 2010
34
0
18,530
Upvote 0 Downvote
J

Jaxon Hennings

Commendable
Nov 3, 2016
3
0
1,510
Have you tried moving the RDP port and seeing if it is the protocol or the port that is having an issue? You could also do a packet capture on the remote WAN side of the remote site to see if the traffic is tunneling or on the hub lan to see if the traffic is reaching the server but just not returning.
 
Upvote 0 Downvote
B

boosted1g

Titan
Jun 12, 2013
14,846
8
74,965


Good idea, if you have a consumer/residential grade connection, they often block common ports for http, https, pop3, rdp, etc. Thus by using a different port and having that different port be the external port in the port forwarding and the 3389 be the internal port.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom