Re: If not on native ISP, remote desktop does not work.

More possible help...

http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=50&EvtSrc=TermDD&LCID=1033

http://www.jsifaq.com/subm/tip6000/rh6031.htm

--
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...


"Sooner Al [MVP]" <SoonerAl@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:u$NaW9PpGHA.1140@xxxxxxxxxxxxxxxxxxxxxxx
A quick Google search brought up these threads...

http://tinyurl.com/ehkcq

One person seems to have fixed this issue with a new router so its
possible a firmware upgrade or reflash may fix the issue...

Has RDP from a remote location off of the Bellsouth network ever worked?

--
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...


"johnnybluenote" <johnnybluenote@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:F179AC6F-86F7-40B3-A06F-271CB66054A3@xxxxxxxxxxxxxxxx
First, the IP address is a static number provided by Bellsouth.
Next, I've gone to canyouseeme.org before and I double-checked it after
your
post - it sees the IP address and it can see port 3389, no problem.
In the event log, the following message appears everytime I tried to get
in
remotely from an ISP other than Bellsouth: "The RDP protocol component
X.224
detected an error in the protocol stream and has disconnected the
client."
Finally, the Westell modem is configured to pass port 3389 onto the
Netgear
router, which in turn, forwards port 3389 to the computer I want to
control
remotely.
Again, everything works well inside the Bellsouth system.

Thanks for all your ideas.

John


"Sooner Al [MVP]" wrote:

What happens if you go to the http://www.canyouseeme.org site while
logged
on the PC you want to remotely connect to?

Is there anything in the event log on that PC when you try to connect
from a
remote site that is off the Bellsouth network?

When you say you have a static IP do you mean you get a static IP from
Bellsouth or do you mean the PC you want to remotely control is
configured
for a static IP on your home LAN?

Is the Westell modem configured as a bridge?

--
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...


"johnnybluenote" <johnnybluenote@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:AC1CFC5F-40AB-4EA1-998B-3D8D37ECBAB6@xxxxxxxxxxxxxxxx
I have: Windows XP Pro SP2, all current updates. It's connected to a
Netgear router and the router is connected to a Westell modem. The
ISP is
Bellsouth (DSL). The modem and the router are both configred so that
port
3389 is passed through to the XP Pro computer I want to control
remotely.
Our IP# is static.
Remote access works perfectly from any computer which is also on the
Bellsouth network. However, from any other ISP - Adelphia, Comcast,
etc.,
Remote Desktop starts to go to the remote screen - the tool bar
appears at
the top, the screen turns blue - but it never connects. Instead, an
error
message appears stating that the connection was lost, perhaps because
of a
network problem. Again, remote access works flawlessly if I connect
from
any
Bellsouth DSL connection outside the office.

Any suggestions?

Thanks, in advance.







.

Relevant Pages

  • Re: PLEASE HELP!! Can connect within network, but not anywhere els
    ... Al Jarvi (MS-MVP Windows Networking) ... which is the assigned IP from my router. ... I really didn't know what i was doing when I switched my TCP port from ... I used the IP my remote computer uses ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: PLEASE HELP!! Can connect within network, but not anywhere els
    ... I really didn't know what i was doing when I switched my TCP port from ... needs TCP Port 3389 forwarded/opened to the IP of your router. ... Al Jarvi (MS-MVP Windows Networking) ... I used the IP my remote computer uses (192.168.100.xxx ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Desktop Web connection setup question
    ... expand Internet Information Service ... One popular brand of routers uses this address for remote html admin, ... The most severe problems arise from router preventing ... >> Al Jarvi (MS-MVP Windows Networking) ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Desktop
    ... Wireless router that I have set up to forward port 3389 to the IP address I ... If so its possible the firewall is configured to only allow Remote ... Al Jarvi (MS-MVP Windows Networking) ...
    (microsoft.public.windowsxp.network_web)
  • Re: Remote Desktop
    ... Wireless router that I have set up to forward port 3389 to the IP address I ... If so its possible the firewall is configured to only allow Remote ... Al Jarvi (MS-MVP Windows Networking) ...
    (microsoft.public.windowsxp.network_web)