Remote Desktop connection

  • Thread starter Thread starter Jason
  • Start date Start date
J

Jason

Guest
I see RDC uses UDP and port 3389. Initially I thought I just needed to
forward TCP port 3389 from the router to the computer. So do I need to
forward UDP port 3389 as well? Is there other ports that need to be
forwarded as well? I've used RDC over a LAN ok but haven't been able to over
the internet where the host computer is conencted via an ethernet router.

Thanks,
J.
 
Re: Remote Desktop connection


"Jason" <JAllen@Hotmail.com> wrote in message
news:OIn6sXRIJHA.2772@TK2MSFTNGP03.phx.gbl...
>I see RDC uses UDP and port 3389. Initially I thought I just needed to
>forward TCP port 3389 from the router to the computer. So do I need to
>forward UDP port 3389 as well? Is there other ports that need to be
>forwarded as well? I've used RDC over a LAN ok but haven't been able to
>over the internet where the host computer is conencted via an ethernet
>router.
>
> Thanks,
> J.

TCP Port 3389 is sufficient and no other ports are required. Start by
running some tests with this command:
telnet IPAddress 3389
first on your LAN, then via the Internet. Note that you must use your
router's external IP address for these tests, not the PC's internal address.
 
Re: Remote Desktop connection

I was using the routers internet IP address/internet domain name address but
still couldn't connect. Over the LAN worked fine.
"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
news:O$fUJ2SIJHA.740@TK2MSFTNGP03.phx.gbl...
>
> "Jason" <JAllen@Hotmail.com> wrote in message
> news:OIn6sXRIJHA.2772@TK2MSFTNGP03.phx.gbl...
>>I see RDC uses UDP and port 3389. Initially I thought I just needed to
>>forward TCP port 3389 from the router to the computer. So do I need to
>>forward UDP port 3389 as well? Is there other ports that need to be
>>forwarded as well? I've used RDC over a LAN ok but haven't been able to
>>over the internet where the host computer is conencted via an ethernet
>>router.
>>
>> Thanks,
>> J.
>
> TCP Port 3389 is sufficient and no other ports are required. Start by
> running some tests with this command:
> telnet IPAddress 3389
> first on your LAN, then via the Internet. Note that you must use your
> router's external IP address for these tests, not the PC's internal
> address.
>
 
Re: Remote Desktop connection


"Jason" <JAllen@Hotmail.com> wrote in message
news:OCvN$DTIJHA.728@TK2MSFTNGP03.phx.gbl...
>I was using the routers internet IP address/internet domain name address
>but still couldn't connect. Over the LAN worked fine.

Your router is not forwarding the packets it receives, perhaps because the
forwarding rule is incorrect or because of some firewall restriction. Use
the telnet command I quoted before to test the connection.
 
Re: Remote Desktop connection

"Jason" <JAllen@Hotmail.com> wrote in message
news:OIn6sXRIJHA.2772@TK2MSFTNGP03.phx.gbl...
>I see RDC uses UDP and port 3389. Initially I thought I just needed to
>forward TCP port 3389 from the router to the computer. So do I need to
>forward UDP port 3389 as well? Is there other ports that need to be
>forwarded as well? I've used RDC over a LAN ok but haven't been able to
>over the internet where the host computer is conencted via an ethernet
>router.
>
> Thanks,
> J.
>


FWIW, I ran into a similar problem recently while setting up some new
computers and thought I'd pass along what I had to do to get RDC working.
Remote Desktop worked fine over the LAN but I had no luck connecting from a
remote location. When I hit the Connect button the RDC program just closed.
No error message. This was in an office where RDC worked on older computers
fine. That meant the router settings were OK. The new computers also had the
same firewall settings.

I did a little research and ran into a bunch of references to Nvidia and ATI
video drivers being the source of the problem. I installed the latest
drivers from Dell's web site but that didn't help. It wasn't until I
installed the latest drivers from ATI's web site that I was able to get RDC
working.

Nepatsfan
 
Back
Top