Can't ping from internet

I've got a Windows 2003 Server SP1 that I can't ping from the Internet side.
My interface is thru a Cisco 675 DSL modem which will allow pass addresses
xxx.xxx.xxx.73 thru xxx.xxx.xxx.78 thru. I've configured the W2k3 server at
76 and can ping it from other devices on the same internal net, however,
when I ping from the internet side it fails. The Cisco modem is at
xxx.xxx.xxx.78 which I can ping from the internet. I have another router
between another network and the internet at xxx.xxx.xxx.74. I can ping it.
I've even swapped the 2003 server to xxx.xxx.xxx.74 and the router to
xxx.xxx.xxx.76 and can ping the router but not the W2k3 server. I have an
NT Server at xxx.xxx.xxx.77 which I can ping from both sides. As I mentioned
earlier, the confusing part is that I can ping all 4 hosts from the inside,
but only 3 from the internet side (the W2k3 server doesn't respond). I've
looked for a firewall block and an registry entry that might be blocking it
and come up empty handed. Any and all suggestions would be greatly
appreciated.

Give the Windows 2003 Server an IP from one of the other workstations (and
turn that other workstation off) temporarily and see what happens. This is
probably a TCP/IP routing problem from the Internet to the server. Won't
know until you test and get back to us.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

"Bud Belles" <(E-Mail Removed)> wrote in message
news:e60y%(E-Mail Removed)...
I've got a Windows 2003 Server SP1 that I can't ping from the Internet side.
My interface is thru a Cisco 675 DSL modem which will allow pass addresses
xxx.xxx.xxx.73 thru xxx.xxx.xxx.78 thru. I've configured the W2k3 server at
76 and can ping it from other devices on the same internal net, however,
when I ping from the internet side it fails. The Cisco modem is at
xxx.xxx.xxx.78 which I can ping from the internet. I have another router
between another network and the internet at xxx.xxx.xxx.74. I can ping it.
I've even swapped the 2003 server to xxx.xxx.xxx.74 and the router to
xxx.xxx.xxx.76 and can ping the router but not the W2k3 server. I have an
NT Server at xxx.xxx.xxx.77 which I can ping from both sides. As I mentioned
earlier, the confusing part is that I can ping all 4 hosts from the inside,
but only 3 from the internet side (the W2k3 server doesn't respond). I've
looked for a firewall block and an registry entry that might be blocking it
and come up empty handed. Any and all suggestions would be greatly
appreciated.

If I understand your suggestion, I should give someother workstation on the
network an address that should be reachable from the internet then try
pinging it from outside. Is that right?

Bud
"Todd J Heron" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Give the Windows 2003 Server an IP from one of the other workstations (and
> turn that other workstation off) temporarily and see what happens. This
> is
> probably a TCP/IP routing problem from the Internet to the server. Won't
> know until you test and get back to us.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
> "Bud Belles" <(E-Mail Removed)> wrote in message
> news:e60y%(E-Mail Removed)...
> I've got a Windows 2003 Server SP1 that I can't ping from the Internet
> side.
> My interface is thru a Cisco 675 DSL modem which will allow pass addresses
> xxx.xxx.xxx.73 thru xxx.xxx.xxx.78 thru. I've configured the W2k3 server
> at
> 76 and can ping it from other devices on the same internal net, however,
> when I ping from the internet side it fails. The Cisco modem is at
> xxx.xxx.xxx.78 which I can ping from the internet. I have another router
> between another network and the internet at xxx.xxx.xxx.74. I can ping
> it.
> I've even swapped the 2003 server to xxx.xxx.xxx.74 and the router to
> xxx.xxx.xxx.76 and can ping the router but not the W2k3 server. I have an
> NT Server at xxx.xxx.xxx.77 which I can ping from both sides. As I
> mentioned
> earlier, the confusing part is that I can ping all 4 hosts from the
> inside,
> but only 3 from the internet side (the W2k3 server doesn't respond). I've
> looked for a firewall block and an registry entry that might be blocking
> it
> and come up empty handed. Any and all suggestions would be greatly
> appreciated.
>
>

Yes. Use a known-working IP.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

"Bud" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
If I understand your suggestion, I should give someother workstation on the
network an address that should be reachable from the internet then try
pinging it from outside. Is that right?

Ok. It will be Wednesday before I can give it a try. Thanks, Todd

"Todd J Heron" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Yes. Use a known-working IP.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> --------------------------------------------------------------------------
--
> This posting is provided "as is" with no warranties and confers no rights
>
> "Bud" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> If I understand your suggestion, I should give someother workstation on
the
> network an address that should be reachable from the internet then try
> pinging it from outside. Is that right?
>

I changed the IP address of another PC in our network to xxx.xxx.xxx.74. I
was able to ping it with no problem from outside our network. My server has
two ports on it. One is for intranet services, the other for the internet
(xxx.xxx.xxx.73 thru 78). Based upon the previous success, I disabled my
intranet adapter then pinged my internet adapter from outside. It workedd.
I was able to make it work by turning of the registry value IPEnableRouting
off. Now I can ping from outside our network my server. However, there was
a price. My IIS is on the same server and now I am unable to access it from
any place. I'm wondering if having the domain name on my server the same as
our external registered domain name might be causing a problem. I have
alway thought that access to an IP address via a domain name only depends on
what our domain registry organization has for the name to relate to the IP
address. In other words, my active directory service host's name is xyz.com
at address xxx.xxx.xxx.76. Network solutions has xyz.com at
yyy.yyy.yyy.zzz. When I get all applications tested, I was going to point
xyz.com to xxx.xxx.xxx.76. Will that work?

Bud
"Bud Belles" <(E-Mail Removed)> wrote in message
news:%23ZWV$(E-Mail Removed)...
> Ok. It will be Wednesday before I can give it a try. Thanks, Todd
>
> "Todd J Heron" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Yes. Use a known-working IP.
>>
>> --
>> Todd J Heron, MCSE
>> Windows Server 2003/2000/NT; CCA
>> --------------------------------------------------------------------------
> --
>> This posting is provided "as is" with no warranties and confers no rights
>>
>> "Bud" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>> If I understand your suggestion, I should give someother workstation on
> the
>> network an address that should be reachable from the internet then try
>> pinging it from outside. Is that right?
>>
>
>

In IIS, on each of your web sites, set the IP address to (All Unassigned).

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights


"Bud" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
I changed the IP address of another PC in our network to xxx.xxx.xxx.74. I
was able to ping it with no problem from outside our network. My server has
two ports on it. One is for intranet services, the other for the internet
(xxx.xxx.xxx.73 thru 78). Based upon the previous success, I disabled my
intranet adapter then pinged my internet adapter from outside. It workedd.
I was able to make it work by turning of the registry value IPEnableRouting
off. Now I can ping from outside our network my server. However, there was
a price. My IIS is on the same server and now I am unable to access it from
any place. I'm wondering if having the domain name on my server the same as
our external registered domain name might be causing a problem. I have
alway thought that access to an IP address via a domain name only depends on
what our domain registry organization has for the name to relate to the IP
address. In other words, my active directory service host's name is xyz.com
at address xxx.xxx.xxx.76. Network solutions has xyz.com at
yyy.yyy.yyy.zzz. When I get all applications tested, I was going to point
xyz.com to xxx.xxx.xxx.76. Will that work?