1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Remote Desktop through an RVS4000

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by apples, Dec 19, 2006.

  1. apples

    apples Guest

    I have an RVS4000 at my office and I'm using Quick VPN to establish a connection successfully. I am however not able to "remote desktop" into my work PC. I am able to get into the RVS4000 to remotely manage it. I cannot see any of the PC's on my network. How do I "get past" the router and manage files on my work PC?

    Also is it possible to make the connection to the RVS4000 using VPN connections in Win XP Pro. I'm using a dyndns utility?
     
  2. shamelin

    shamelin LI Guru Member

    same issue please help

    I am having the same issue. please help
     
  3. heidnerd

    heidnerd LI Guru Member

    Is Windows XP firewalling the remote desktop access? Check the Windows Security center.
     
  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    What version of quickvpn are you using if I may ask? Also, are you able to ping any of the nodes on the inside of the remote network?

    Jay
     
  5. shamelin

    shamelin LI Guru Member

    the quick vpn file name I dounloaded was QVPN_Client_1039. Router has all updates and I can ping all the nodes and even log in to router via IE using the GW address but I cant see any of my shares
     
  6. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    Have you tested the RD host by logging on from another PC on the LAN? You need to make an exception for it in the XP firewall, on the host.

    Don't worry about seeing shares in network places..totally irrelevant for RDC, and often difficult to get setup on a VPN.
     
  7. Toxic

    Toxic Administrator Staff Member

    have you port forward the RDC port from the RVS4000 to the PC you need to connect to? Port 3389 UDP. make sure the firewallon the PC has this set to allow RDC. also make sure your RDC Options are correct. (set "experience" to correct upload speed, Modem 56k is best tbh)
     
  8. SoonerAl

    SoonerAl LI Guru Member

    Remote Desktop uses TCP Port 3389 not UDP Port 3389...

    General troubleshooting help, etc for Remote Desktop...

    http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html
    http://theillustratednetwork.mvps.org/RemoteDesktop/RDP6ConfigRecommendations.html
     
  9. Toxic

    Toxic Administrator Staff Member

  10. SoonerAl

    SoonerAl LI Guru Member

    That is concerning sound redirection only. Early on some folks needed to also open UDP Port 3389 in order to get sound passed from the remote PC. That has never been an issue for me, but others had it. I believe it does not apply with later versions of the RDP client. As always though...YMMV...
     
  11. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    TCP port for plain RDC...however, if he's VPN'ing in...port forwarding on the router is not needed. HOwever, you'd port forward if you didn't use any VPN to the network...just connecting to the WAN IP from across the internet.
     
  12. DDogg

    DDogg LI Guru Member

    Nothing unique, but I set up multiple RDc's behind the router routinely for my clients by changing the port on each machine I want accessible.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\

    Change "port number" to whatever, in this example 5006 (reboot!) - then once VPN is established use rdc with:

    local IP:port number like 192.168.10.106:5006

    You can have as many as you want.

    Of course, if you want to use Wan access to do the same thing the address would be the IP or FQDN plus the colon and port number - mytest.com:5006 but this requires the risk of forwarding the custom ports to their respective machines.
     
  13. SoonerAl

    SoonerAl LI Guru Member

    Except accessing the PCs through a VPN (or Secure Shell (SSH)) tunnel means you don't need to do that, ie. change the listening port on each PC to something else than the default. Your making an easy task more complicated for no gain...:cool:
     
  14. DDogg

    DDogg LI Guru Member

    Of course, but it does give a small bit of extra security as the rdc needs the special port number as well as the IP - not much additional security I'll admit. Primarily I do it this way in case I need to fix something externally if they are having problems and I can't establish the vpn. I have a helper activate my preset port forwarding which allows me external access to all machines behind the router. It come in handy as these situations would be a real mess if I did not have the custom ports and forwarding already setup (normally under the time gun when this happens).

    It works well for me, but as you say, not necessary at all for simple setups.
     
  15. SoonerAl

    SoonerAl LI Guru Member

    Personally I would look for the reason you can't reliably establish a VPN connection instead of opening more ports on your router...:cool:

    Good luck...
     
  16. swiego

    swiego LI Guru Member

    I am VPNing into my router (the wireless version of the RVS4000) and am having a similar problem.

    I have this working but only by going into my router setup and forwarding port 3389 (TCP) to a particular IP for a particular PC within my network... only then can I RDC to that PC. And therefore I can't RDC to any other PCs in the network (want to be able to RDC into at least one other). I'm a bit lost. If I'm VPNing into my network, why would I need to do port forwarding in my router firewall anyway? I'm already "inside" my network now, right?
     

Share This Page