Re: Remote works at one local...not the other
- From: "Sooner Al [MVP]" <SoonerAl@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 8 Mar 2006 05:49:06 -0600
What cable modem/router? See if this site can help you opening TCP Port
3389...
http://www.portforward.com/english/applications/port_forwarding/RemoteDesktop/RemoteDesktopindex.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...
"Snake49444" <Snake49444@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BF2A4155-D45C-4F74-B3A4-98102BD812F3@xxxxxxxxxxxxxxxx
So this would be the same case in a cable modem/router? I have the
wireless
connection working great. I have a static IP address programed into the
wireless TCP/IP settings but I cannot remote connect to the laptop. If
this
is the case, from what i've read, I need to call my cable ISP and ask them
to
turn on port 3389 for the router?
"Brian Tate" wrote:
This seems to be the case Al. After fighting this all day with another
DSL provider, I came to same conclusion. I'm going back into the battle
tomorrow and will go have the 3389 port to see if this works.
Thanks
"Sooner Al" wrote:
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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:484B1E26-828E-46E8-B2D3-42A681D34FEB@xxxxxxxxxxxxxxxx
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.
.
- Prev by Date: Re: Remote Desktop directly to another computer on the network
- Next by Date: Re: Cant connect to one computer
- Previous by thread: Re: Remote Desktop directly to another computer on the network
- Next by thread: Re: Remote works at one local...not the other
- Index(es):
Relevant Pages
|
