NAT client ping request timed out

Hi, All:

I need some helps on this:

I have a NAT server Windows 2003 server that setup with two NICs, one for
public and one for private network. I connect the public NIC to the Internet
with a static IP, and private to a hub, then some other PCs to the hub. I
configured everything according to

How to configure Network Address Translation in Windows Server 2003

It seems working correctly on NAT server side because some mapping packets
are flowing through. But when I try to ping any outside address from a PC on
private network, every address is resolved correctly, but I keep getting
"Request Timed out" error. The gateway assigned on that PC is the NAT server
private IP address which should be ok, but I am not sure. Anyone can help on
this? I think it is gateway or routing issue but I don't know how to fix it.
Why DNS is able to resolve, but not IP packets? Thank you very much.

--Jay

Make sure that the private NIC on the server does NOT have a default
gateway.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"jay" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi, All:
>
> I need some helps on this:
>
> I have a NAT server Windows 2003 server that setup with two NICs, one for
> public and one for private network. I connect the public NIC to the
Internet
> with a static IP, and private to a hub, then some other PCs to the hub. I
> configured everything according to
>
> How to configure Network Address Translation in Windows Server 2003
>
> It seems working correctly on NAT server side because some mapping packets
> are flowing through. But when I try to ping any outside address from a PC
on
> private network, every address is resolved correctly, but I keep getting
> "Request Timed out" error. The gateway assigned on that PC is the NAT
server
> private IP address which should be ok, but I am not sure. Anyone can help
on
> this? I think it is gateway or routing issue but I don't know how to fix
it.
> Why DNS is able to resolve, but not IP packets? Thank you very much.
>
> --Jay
>
>


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.782 / Virus Database: 528 - Release Date: 10-22-2004

Yes. I didn't have a default gateway set on that private NIC. But I set a
default gateway on static route with Dest: 0.0.0.0, Mask: 0.0.0.0, Gateway:
ISP provided gateway IP address, Interface: public NIC name. If I don't set
this gateway, it won't work for client to see DNS. This really puzzles me.
Thanks.

--Jay

"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Make sure that the private NIC on the server does NOT have a default
> gateway.
>
> Doug Sherman
> MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
> "jay" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hi, All:
> >
> > I need some helps on this:
> >
> > I have a NAT server Windows 2003 server that setup with two NICs, one
for
> > public and one for private network. I connect the public NIC to the
> Internet
> > with a static IP, and private to a hub, then some other PCs to the hub.
I
> > configured everything according to
> >
> > How to configure Network Address Translation in Windows Server 2003
> >
> > It seems working correctly on NAT server side because some mapping
packets
> > are flowing through. But when I try to ping any outside address from a
PC
> on
> > private network, every address is resolved correctly, but I keep getting
> > "Request Timed out" error. The gateway assigned on that PC is the NAT
> server
> > private IP address which should be ok, but I am not sure. Anyone can
help
> on
> > this? I think it is gateway or routing issue but I don't know how to fix
> it.
> > Why DNS is able to resolve, but not IP packets? Thank you very much.
> >
> > --Jay
> >
> >
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.782 / Virus Database: 528 - Release Date: 10-22-2004
>
>

Your routing seems to be set correctly. Make sure you are pinging sites
which do not block ICMP - eg. google.com. Also, When you enable NAT on the
Server, you automatically enable the Basic Firewall. If you are also
running firewalls on the client machines, try disabling them. Sometimes if
you also run a firewall on a client PC behind a NAT firewall, you may
experience this problem.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"jay" <(E-Mail Removed)> wrote in message
news:%234%(E-Mail Removed)...
> Yes. I didn't have a default gateway set on that private NIC. But I set a
> default gateway on static route with Dest: 0.0.0.0, Mask: 0.0.0.0,
Gateway:
> ISP provided gateway IP address, Interface: public NIC name. If I don't
set
> this gateway, it won't work for client to see DNS. This really puzzles me.
> Thanks.
>
> --Jay
>
> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Make sure that the private NIC on the server does NOT have a default
> > gateway.
> >
> > Doug Sherman
> > MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >
> > "jay" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > Hi, All:
> > >
> > > I need some helps on this:
> > >
> > > I have a NAT server Windows 2003 server that setup with two NICs, one
> for
> > > public and one for private network. I connect the public NIC to the
> > Internet
> > > with a static IP, and private to a hub, then some other PCs to the
hub.
> I
> > > configured everything according to
> > >
> > > How to configure Network Address Translation in Windows Server 2003
> > >
> > > It seems working correctly on NAT server side because some mapping
> packets
> > > are flowing through. But when I try to ping any outside address from a
> PC
> > on
> > > private network, every address is resolved correctly, but I keep
getting
> > > "Request Timed out" error. The gateway assigned on that PC is the NAT
> > server
> > > private IP address which should be ok, but I am not sure. Anyone can
> help
> > on
> > > this? I think it is gateway or routing issue but I don't know how to
fix
> > it.
> > > Why DNS is able to resolve, but not IP packets? Thank you very much.
> > >
> > > --Jay
> > >
> > >
> >
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.782 / Virus Database: 528 - Release Date: 10-22-2004
> >
> >
>
>


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.782 / Virus Database: 528 - Release Date: 10-22-2004