Re: Remote Desktop problems outside my network
- From: "Sooner Al [MVP]" <SoonerAl@xxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 19 Jul 2007 14:28:03 -0500
"Gary R." <GaryR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:068A71A6-5F90-481A-A364-D0A8B6B7C658@xxxxxxxxxxxxxxxx
With the link you sent My son found the following:Interesting...
"One of the settings on the router side that the previous guide had showed
was incorrect, as it was using screenshots from an earlier firmware. Due to
that, it was forwarding TCP but not UDP, causing the connection not to
complete."
"The forwarding on the old firmware had individual settings for TCP and UDP.
The new one just toggles whether you want one, the other, or both"
I successfully connected after he Switched the pulldown from TCP to Both.
Just shows how a simple mistake can create problems. Much Thanks.
"
Normally UDP Port 3389 is not needed. Early on, ie. XP SP1 days and earlier, some folks with audio redirection issues needed UDP Port 3389. Normally Remote Desktop (RDP) only needs TCP Port 3389 forwarded.
Glad to hear its working for you...
--
Al Jarvi (MS-MVP Windows Networking)
Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375
.
- References:
- Re: Remote Desktop problems outside my network
- From: Sooner Al [MVP]
- Re: Remote Desktop problems outside my network
- From: Sooner Al [MVP]
- Re: Remote Desktop problems outside my network
- Prev by Date: Transitioning from pcAnywhere to Remote Desktop
- Next by Date: Re: Missing Remote Tab in Divice manager
- Previous by thread: Re: Remote Desktop problems outside my network
- Next by thread: rdp through internet connections
- Index(es):
Relevant Pages
|