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

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

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.
 
Remote Access fails when they enable Natting at the ISP side...
If Natting is enable, Remote Access will disconnect every 5 minutes....
and check how much latency you are getting......
 
First, if outside the Bellsouth system, Remote Desktop NEVER connects so
there is no "disconnect" problem. Secondly, I have talked to the techs at
Adelphia and they have told me there is nothing they are doing which would
block remote desktop.

So, I'm still searching for an answer.

Thanks.

John
 
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...
 
You also might post this to the Bellsouth forum on the BBR site since this
seems related to a configuration issue with the Bellsouth DSL modem/router,
at least in my mind...

http://www.dslreports.com/forum/ilec,bels

You also might be interested in this guide to setting up a Westell modem in
bridge mode...

http://www.dslreports.com/faq/6405

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