Unable to connect to machine behind MS MN-700 router using..

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I have two machines running behind a Microsoft MN-700 router. I'd like to be able to connect to one of these computers (XP Pro) when I'm away from home (my home computers are connected to the Internet via a fast Comcast cable connection), but I'm having absolutely no success in doing this. Here's what I've tried:

Ping:
When I ping the local computer address (192.168.0.x), it finds it immediately. When I ping the internal router address, again, no problem. However, if I ping the routers WAN IP address, the request times out.

Remote Desktop:
I configured this as follows:
1. Made sure Remote Desktop was enabled on the machine I was trying to connect to.
2. Went into Add/Remove Programs and turned on the Remote Desktop Web Connection and UPnP.
3. In my Microsoft MN-700 router, I turned on "persistent" Port Forwarding as follows:
a. Inbound Port: 3389 - 3389
b. Type: TCP
c. Private IP Address: 192.168.0.x
d. Private Port: 3389 - 3389
4. For the web connection, I also forwarded the following port:
a. Inbound Port: 80 - 80
b. Type: TCP
c. Private IP Address: 192.168.0.x
d. Private Port: 80 - 80
5. Under Security->Firewall, I turned off ICMP command blocking.

If I try to connect to the computer using the local computer address, no problem (standard or web client). If I try to connect using the WAN IP address, I get a timeout, whether I try to connect via the standard Remote Desktop client or the web client.

IIS:
I'm able to access a web page on the computer if I do it internally using the local IP address. Using the WAN IP address, however, I get a "Page not found".

Any ideas? What else can I try? Thanks...

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Perhaps Comcast is blocking your connection...

What type of IP Address are you getting from Comcast... In the past,
I have heard of some cable providers assigning private addresses to
cable subscribers instead of a publicly accessible address... This
could be a cause of your problems...

Jeffrey Randow (Windows Net. & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

On Wed, 14 Apr 2004 01:11:05 -0700, Tad Price
<anonymous@discussions.microsoft.com> wrote:

>I have two machines running behind a Microsoft MN-700 router. I'd like to be able to connect to one of these computers (XP Pro) when I'm away from home (my home computers are connected to the Internet via a fast Comcast cable connection), but I'm having absolutely no success in doing this. Here's what I've tried:
>
>Ping:
>When I ping the local computer address (192.168.0.x), it finds it immediately. When I ping the internal router address, again, no problem. However, if I ping the routers WAN IP address, the request times out.
>
>Remote Desktop:
>I configured this as follows:
>1. Made sure Remote Desktop was enabled on the machine I was trying to connect to.
>2. Went into Add/Remove Programs and turned on the Remote Desktop Web Connection and UPnP.
>3. In my Microsoft MN-700 router, I turned on "persistent" Port Forwarding as follows:
> a. Inbound Port: 3389 - 3389
> b. Type: TCP
> c. Private IP Address: 192.168.0.x
> d. Private Port: 3389 - 3389
>4. For the web connection, I also forwarded the following port:
> a. Inbound Port: 80 - 80
> b. Type: TCP
> c. Private IP Address: 192.168.0.x
> d. Private Port: 80 - 80
>5. Under Security->Firewall, I turned off ICMP command blocking.
>
>If I try to connect to the computer using the local computer address, no problem (standard or web client). If I try to connect using the WAN IP address, I get a timeout, whether I try to connect via the standard Remote Desktop client or the web client.
>
>IIS:
>I'm able to access a web page on the computer if I do it internally using the local IP address. Using the WAN IP address, however, I get a "Page not found".
>
>Any ideas? What else can I try? Thanks...

 

[rod]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

----- Jeffrey Randow (MVP) wrote: -----

Perhaps Comcast is blocking your connection...

What type of IP Address are you getting from Comcast... In the past,
I have heard of some cable providers assigning private addresses to
cable subscribers instead of a publicly accessible address... This
could be a cause of your problems...

I am wondering if this might be my problem -can't connect to my XP Pro laptap when it is online with my home ISP - wireless high speed. Can connect fine when it is online at work or dial-up. My home ISP says they are not blocking 3389 and 1723, router not the issue because I have tried with the laptap connected directly as well.
How can I tell if they are not providing a "publicly accesseible address"? My dns update returns an address of 207.xxx.xxx.xxx, the wan ip shown by the router is 172.xxx.xxx.xxx. Can't connect using either address.

Thanks,

Rod

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Which one do you get if you go to http://myipaddress.com ?

The 172.x.x.x address space may be part of the private network space
(it depends on the value in the first x.)

From the Spec:
The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:


10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

If you are getting this type of WAN (make sure it is not LAN address),
then you are NAT'ed behind the ISP Firewall.

Jeffrey Randow (Windows Net. & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone


On Sun, 18 Apr 2004 10:51:03 -0700, Rod
<anonymous@discussions.microsoft.com> wrote:

> ----- Jeffrey Randow (MVP) wrote: -----
>
> Perhaps Comcast is blocking your connection...
>
> What type of IP Address are you getting from Comcast... In the past,
> I have heard of some cable providers assigning private addresses to
> cable subscribers instead of a publicly accessible address... This
> could be a cause of your problems...
>
>I am wondering if this might be my problem -can't connect to my XP Pro laptap when it is online with my home ISP - wireless high speed. Can connect fine when it is online at work or dial-up. My home ISP says they are not blocking 3389 and 1723, router not the issue because I have tried with the laptap connected directly as well.
>How can I tell if they are not providing a "publicly accesseible address"? My dns update returns an address of 207.xxx.xxx.xxx, the wan ip shown by the router is 172.xxx.xxx.xxx. Can't connect using either address.
>
>Thanks,
>
>Rod

 

[rod]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

----- Jeffrey Randow (MVP) wrote: -----

Which one do you get if you go to http://myipaddress.com ?

The 172.x.x.x address space may be part of the private network space
(it depends on the value in the first x.)

From the Spec:
The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets...

When I go to http://myipaddress.com is get: 207.107.xxx.xxx.

My router shows the WAN IP as being 172.16.xxx.xxx.

What does it mean to be "NAT'ed behind the ISP Firewall"? If that is my situation, what can be done about it?

THANK YOU VERY MUCH!

Rod

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

172.16.x.x is a private address. There is not much you can do other
than complain to your ISP since you are not in control of the NAT
gateway...

In other words, you are actually double NAT'ed as your ISP has you
behind a NAT (Network Address Translation) gateway and then you go and
re-NAT your connection with your router...

You should check with your ISP to see if or what it takes to get a
publicly addressible LAN IP address. Without this, all of the nice
services (Remote Assistance, Remote Desktop, etc) will never work.

Jeffrey Randow (Windows Net. & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

On Sun, 18 Apr 2004 20:51:09 -0700, Rod
<anonymous@discussions.microsoft.com> wrote:

>
> ----- Jeffrey Randow (MVP) wrote: -----
>
> Which one do you get if you go to http://myipaddress.com ?
>
> The 172.x.x.x address space may be part of the private network space
> (it depends on the value in the first x.)
>
> From the Spec:
> The Internet Assigned Numbers Authority (IANA) has reserved the
> following three blocks of the IP address space for private internets...
>
>When I go to http://myipaddress.com is get: 207.107.xxx.xxx.
>
>My router shows the WAN IP as being 172.16.xxx.xxx.
>
>What does it mean to be "NAT'ed behind the ISP Firewall"? If that is my situation, what can be done about it?
>
>THANK YOU VERY MUCH!
>
>Rod

 

[rod]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

----- Jeffrey Randow (MVP) wrote: -----

172.16.x.x is a private address. There is not much you can do other
than complain to your ISP since you are not in control of the NAT
gateway...

In other words, you are actually double NAT'ed as your ISP has you
behind a NAT (Network Address Translation) gateway and then you go and
re-NAT your connection with your router...

You should check with your ISP to see if or what it takes to get a
publicly addressible LAN IP address. Without this, all of the nice
services (Remote Assistance, Remote Desktop, etc) will never work.. . .

Thanks again, now I can talk to my ISP having a more information under my belt. One other question - what about the 207.107.xxx.xxx address that http://myipaddress.com and my dns updater return: is this a publicly addressable IP, and if so, how is it that it can't be accessed?

Thanks!

Rod

 

[Bob]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

On Tue, 20 Apr 2004 05:06:02 -0700, =?Utf-8?B?Um9k?=
<RwBadgley@DELETEmsn.com> wrote:

>
> ----- Jeffrey Randow (MVP) wrote: -----
>
> 172.16.x.x is a private address. There is not much you can do other
> than complain to your ISP since you are not in control of the NAT
> gateway...
>
> In other words, you are actually double NAT'ed as your ISP has you
> behind a NAT (Network Address Translation) gateway and then you go and
> re-NAT your connection with your router...
>
> You should check with your ISP to see if or what it takes to get a
> publicly addressible LAN IP address. Without this, all of the nice
> services (Remote Assistance, Remote Desktop, etc) will never work.. . .
>
>Thanks again, now I can talk to my ISP having a more information under my belt. One other question - what about the 207.107.xxx.xxx address that http://myipaddress.com and my dns updater return: is this a publicly addressable IP, and if so, how is it that it can't be accessed?
>
>Thanks!
>
>Rod

My IP address is wrong! How can that be?
If your computer is located behind a firewall, the firewall may be
hiding your computer's actual IP address from myIPaddress.com. In
which case the IP address displayed is actually the IP address of the
firewall, not your computer.

Similarly, if your computer is behind a "proxy server" or "web cache"
(i.e., a computer that intercepts requests for web pages in order to
speed up frequently-requested pages), the IP address displayed is
probably the IP address of the proxy server or web cache -- not your
computer.

Note that your computer may be behind a proxy server or web cache
without your knowledge! A number of companies and Internet Service
Providers use "transparent web caches", which intercept requests for
web pages without any special configuration of your computer.

---

Non-Routable (Private) IP Addresses

We recommend non-routable IP for home networks. These IP addresses
have been set aside for use in home and office networks, when it isn't
necessary (or even desirable) to use a public IP address. They are
especially useful to the DSL user who has multiple computers connected
to a single proxy server, firewall or router (see our Network Overview
for details).

Reserved IP addresses for private networks

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

For more information, see RFC 1918 Address Allocation for Private
Internets: http://www.faqs.org/rfcs/rfc1918.html

HTH

--

Map Of The Vast Right Wing Conspiracy:
http://www.freewebs.com/vrwc/

"You can all go to hell, and I will go to Texas."
--David Crockett

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

That's the address of the gateway at your ISP...

Jeffrey Randow (Windows Net. & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

On Tue, 20 Apr 2004 05:06:02 -0700, Rod <RwBadgley@DELETEmsn.com>
wrote:

>
> ----- Jeffrey Randow (MVP) wrote: -----
>
> 172.16.x.x is a private address. There is not much you can do other
> than complain to your ISP since you are not in control of the NAT
> gateway...
>
> In other words, you are actually double NAT'ed as your ISP has you
> behind a NAT (Network Address Translation) gateway and then you go and
> re-NAT your connection with your router...
>
> You should check with your ISP to see if or what it takes to get a
> publicly addressible LAN IP address. Without this, all of the nice
> services (Remote Assistance, Remote Desktop, etc) will never work.. . .
>
>Thanks again, now I can talk to my ISP having a more information under my belt. One other question - what about the 207.107.xxx.xxx address that http://myipaddress.com and my dns updater return: is this a publicly addressable IP, and if so, how is it that it can't be accessed?
>
>Thanks!
>
>Rod