Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Is it possible that DSL Modem won't allow remote desktop connectio

0 views
Skip to first unread message

fzfrank

unread,
Mar 20, 2007, 3:59:38 PM3/20/07
to
I apologize if this has been covered. I searched and couldn't find anything.

I think I understand how to configure my computer and routers for a remote
desktop connection but I can't connect from a computer outside my network. I
can get a remote connection (both web-based and standard) from a computer on
the local network.

My modem/router configuration is:
DSL Modem --> VOIP Router --> Wireless Router --> Desktop/Laptop

I set the VOIP router to DMZ to the Wireless Router and I set the Wireless
Router to forward ports xx (that's the port I chose) and 3389 to the host
computer. There are no options to change settings on the DSL modem.

I have a static IP address. When try the site http://xx.xx.xxx.xx:xx/tsweb I
get a "can't establish connection."

Is it possible that my DSL modem won't allow incoming connections. FYI, the
DSL modem is Microsoft DSL1000. I've spent a couple of days on this and it's
starting to drive me nuts.

Any help would be appreciated. Thanks.

Sooner Al [MVP]

unread,
Mar 20, 2007, 4:43:00 PM3/20/07
to
"fzfrank" <fzf...@discussions.microsoft.com> wrote in message
news:733B5A1C-3228-4032...@microsoft.com...

You need both TCP Port 80 (IIS) and TCP Port 3389 (Remote Desktop aka RDP)
open/forwarded through any firewall or router the PC you want to connect to
is behind. So, if you go to the http://www.canyouseeme.org site while on
that PC does the test pass? Meaning can you pass both the IIS and RDP port
tests? If not, can you at least pass the RDP port test? Be aware some DSL
modems are also routers and either you need to open/forward the appropriate
ports or configure the modem into a bridge mode, ie. disabling its NAT
function. Check the users manual for help with that.

Also make sure your calling the correct public IP. Note that with most
current consumer grade routers it is *NOT* a valid test to call the PC from
another PC on your local network using the public IP of the modem and/or
router.

http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDiagrams/Basic.html

Also note that some ISPs block TCP Port 80 incoming because running a web
server (ie. IIS) that is publicly available is a violation of a residential
account terms of service. Check with your ISP about that...

--

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

fzfrank

unread,
Mar 20, 2007, 7:27:02 PM3/20/07
to
> You need both TCP Port 80 (IIS) and TCP Port 3389 (Remote Desktop aka RDP)
> open/forwarded through any firewall or router the PC you want to connect to
> is behind.

I opened both ports (actually used an alternative to port 80).

> So, if you go to the http://www.canyouseeme.org site while on
> that PC does the test pass? Meaning can you pass both the IIS and RDP port
> tests?

It did not pass. Then I tried removing the routers between the DSL modem and
host computer and canyousee.org still didn't pass.

> If not, can you at least pass the RDP port test?

I could not get it to pass 3389 or 80 (or my substitute).

> Be aware some DSL
> modems are also routers and either you need to open/forward the appropriate
> ports or configure the modem into a bridge mode, ie. disabling its NAT
> function. Check the users manual for help with that.

I don't think this is a router because there is only one LAN port in the
back. I also checked the advanced settings and there doesn't appear to be
anything I can change.

> Also make sure your calling the correct public IP. Note that with most
> current consumer grade routers it is *NOT* a valid test to call the PC from
> another PC on your local network using the public IP of the modem and/or
> router.

I had someone try connecting to my IP address from another location and they
got a "server error".


>
> Also note that some ISPs block TCP Port 80 incoming because running a web
> server (ie. IIS) that is publicly available is a violation of a residential
> account terms of service. Check with your ISP about that...

I substituted a port for 80. I configured my routers/firewall for that port
and I am able to connect using my internal network 192.168.0.3:xx/tsweb.

Sooner Al [MVP]

unread,
Mar 21, 2007, 5:55:09 AM3/21/07
to
"fzfrank" <fzf...@discussions.microsoft.com> wrote in message
news:73E5ADE6-8F14-4D7C...@microsoft.com...

It sounds to me like that DSL modem is also a router. With the computer
connected directly to the router what IP is reported if you go to "Start ->
Run" and type cmd at the command window, then type ipconfig at the command
prompt? Is is a 10.X.X.X or 172.16.X.X or a 192.168.X.X address? If its one
of those IP ranges then you need to find a way to put the DSL modem, which
is also a NAT router, into a bridge or pass through mode of operation, ie.
the built-in NAT is disabled. Check the users manual for help with that or
check with your ISP.

Neil K

unread,
Mar 22, 2007, 1:20:30 AM3/22/07
to
That DSL Modem is also a router. The westell dsl modems are just like this.
They look like a modem with 1 lan port, but they are a modem/router.
There's a config page you'll have to get to in order to switch it to a
bridged ethernet as Al mentioned below. On my westell, it was
192.168.0.2/config. Just using the modem IP doesn't reveal this page; maybe
the company didn't want people changing settings.

I did see one posting on the web about using this address:
192.168.1.1/mmadv/advindex.htm.
Good Luck
Neil K
"Sooner Al [MVP]" <Soon...@somewhere.net.invalid> wrote in message
news:A80F6265-5F63-4CF9...@microsoft.com...

0 new messages