No Internet Activity beyond DNS

I'm working on a brand new 2003 server install and I
cannot browse the web. I've disabled the enhanced security
feature and I can ping anything on my private network, but
nothing beyond my firewall to the outside world. DNS seems
to be working fine; I attempt to ping external URL's and
the IP comes back while the Ping itself times out.

Any help would be appreciated.

Hi James,

Check TCP/IP configuration on your Windows 2003 server, specially Default
Gateway setting -- is (correct) IP entered for default gateway?

Mike

"James" <(E-Mail Removed)> wrote in message
news:869e01c495e7$757ee150$(E-Mail Removed)...
> I'm working on a brand new 2003 server install and I
> cannot browse the web. I've disabled the enhanced security
> feature and I can ping anything on my private network, but
> nothing beyond my firewall to the outside world. DNS seems
> to be working fine; I attempt to ping external URL's and
> the IP comes back while the Ping itself times out.
>
> Any help would be appreciated.

It is correct there, and I can ping the gateway as well as
even bring up its web based interface. I'm going to check
with the firewall support team to make sure we're not
limited to a certain number of NAT'ed Addresses within the
network.

Thank you for your time!


>-----Original Message-----
>Hi James,
>
>Check TCP/IP configuration on your Windows 2003 server,
specially Default
>Gateway setting -- is (correct) IP entered for default
gateway?
>
>Mike
>
>"James" <(E-Mail Removed)> wrote in message
>news:869e01c495e7$757ee150$(E-Mail Removed)...
>> I'm working on a brand new 2003 server install and I
>> cannot browse the web. I've disabled the enhanced
security
>> feature and I can ping anything on my private network,
but
>> nothing beyond my firewall to the outside world. DNS
seems
>> to be working fine; I attempt to ping external URL's and
>> the IP comes back while the Ping itself times out.
>>
>> Any help would be appreciated.
>
>
>.
>

> It is correct there, and I can ping the gateway as well as
> even bring up its web based interface.

Gateway is always on same network as your computer and you don't need
gateway address configured to actually ping it or access it's website. You
only need gateway configured when you need to access anything beyond your
gateway (beyond your network) including anything on internet.

> I'm going to check with the firewall support team to make sure we're not
> limited to a certain number of NAT'ed Addresses within the
> network.

OK

Mike