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

wrv54g and remote desktop

Discussion in 'Networking Issues' started by rog2554, Oct 18, 2006.

  1. rog2554

    rog2554 LI Guru Member

    I have a wrv54r with an static ip address. I use QuickVPN to connect to it and the try to run Remote Desktop but it crashes with the error "The connection to the remote computer was broken. This may have been
    caused by a network error. Please try connecting to the remote computer
    again.†I have enabled port forwarding of port 3389 to the ip address of the pc i am trying to connect to but it still does not work.
  2. ifican

    ifican Network Guru Member

    Windows is very touch about remote desktop, I am assuming here you are running sp2 for xp. You need to go into xp and tell it to allow someone to connect to the machine, when you check this it will automatically allow the 3389 port through windows firewall. You will also have to make sure you check to logon with the credentials you supply as i am assuming again that you are not using the same credentials to log on to your currrent machine.
  3. rog2554

    rog2554 LI Guru Member

    yes, I have enable the exception in Windows firewall and also enabled an account to use Remote Desktop. When I am on the local network I have tested Remote Desktop and it does work.
  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    WRV54G Can't Pass Protocol 47 (GRE)

    RDP requires protocol 47 (GRE) to pass "through" the WRV54G; unfortunately, the WRV54G doesn't support GRE. As a result, RDP is not going to work on its own. The workaround for this is to connect with quickvpn (or a third party vpn client) and then use an application such as "tight vnc" to work on your desktop; alot of users during the early days of the linksysinfo forums (man, I've been around for a while) were using this aproach because the WRV54G didn't pass GRE. Being that it appears quickvpn and your XP client aren't relating so good, you should try another vpn client. Here's a link to download a free copy of SSH Sentinel:


    Get "Tight VNC" ware from here:


    In a worst case scenario, you can "try" to configure the microsoft IPSEC client; I've only seen of "two" people on the entire internet to get this thing to work:


    In the end, the only feasible option you may have (until a better one comes along) is using another vpn client (for the initial connection) followed by some form of remote administration tool to use through the tunnel. If I neglected to mention, the tool I use through my wrv200/wrv54g IPSEC tunnel to control my computers is Radmin (http://www.radmin.com). Incidentally, the performance of Radmin is comparable when I run my MS 2003 vpn server behind my wrv200 (wrv200 passes GRE whereas the wrv54g doesn't) after I forward port 1723 (PPTP) to it (MS 2003 vpn server); hence why I bought the wrv200 :) )

  5. rog2554

    rog2554 LI Guru Member

    do you have any information on configuring the VPN client SSH Sentinal and are there any changes that need to b emade on the router.

Share This Page