Re: Remote works at one local...not the other
From: Sooner Al (SoonerAl_at_somewhere.net.invalid)
Date: 07/28/04
- Next message: Sooner Al: "Re: Not all PCs in network can connect with Remote Desktop"
- Previous message: Sooner Al: "Re: From college to home"
- In reply to: Brian Tate: "Remote works at one local...not the other"
- Next in thread: Brian Tate: "Re: Remote works at one local...not the other"
- Reply: Brian Tate: "Re: Remote works at one local...not the other"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 27 Jul 2004 19:08:34 -0500
Some DSL modems are also routers. If that is the case its possible TCP Port 3389 in closed. Contact
tech support to see if that is the case. Bottom line is you need TCP Port 3389 open to the private
IP, ie. the 192.X.X.X address, in order for Remote Desktop to work...
--
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...
"Brian Tate" <BrianTate@discussions.microsoft.com> wrote in message
news:484B1E26-828E-46E8-B2D3-42A681D34FEB@microsoft.com...
> I'm working with a client that is trying to connect to several different locations. We have
> connected with no problem to one which uses Sprint/Earthlink DSL, but for some reason, we can't
> connect to some of the other locations using the same DSL service and Bellsouth fast DSL.
>
> On the Bellsouth one, we have a static IP setup, but it seems the westell modem acts like a
> firewall giving it an IP of 192.168.1.154 instead of our assinged static IP. If you go to the
> network connections and try to set the IP, subnet, default gateway and DNS servers manually, it
> causes the internet connection to not work. When it is set back to auto, it grabs the info and
> works find. It is like there is a router/firewall attached, but there is not.
>
> What is worse, every tech support call landed me with somebody who spoke broken English so that
> was a total waste of time because I could never really understand the tech person nor do I think
> he was totally understanding what I was trying to do.
>
> The only person I got between all the calls was Steve with Microsoft tech. He was great with
> English, but he could not figure out why this stuff would not work.
>
> The error I am getting in these connections is "Could not establish connection with the remote.
> The remote desktop may not be enabled, there may be too many connections, or there may be network
> problems."....or something like that.
>
> Found the error on help.Microsoft.com, but it only said to install upgrades which I have done.
>
> Thanks in advance for any leads. Been fighting this for 9 hours today with 200 used minutes and a
> dead cell phone. Could use a little guidance.
- Next message: Sooner Al: "Re: Not all PCs in network can connect with Remote Desktop"
- Previous message: Sooner Al: "Re: From college to home"
- In reply to: Brian Tate: "Remote works at one local...not the other"
- Next in thread: Brian Tate: "Re: Remote works at one local...not the other"
- Reply: Brian Tate: "Re: Remote works at one local...not the other"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|