About NAT

[Henry@mobile]

Hi, I have the following problem.

I am going to use windows 2000 server as a router. The connection is:

Cable Modem -> Win2kServer -> Hub -> Client Workstation

I use NAT instead of ICS to route the packet. The server can ping internet
address (say, yahoo.com) and ping client workstation's IP assigned by DHCP
of the server. The problem now is that the client machine cannot connect to
the internet.

In the NAT under Route&RemoteAccess, I have check both interface configure
properly. Internet connection choose public interface connected to internet
and internal connection choose private interface connected to private
network.

I configure R&RA by selecting the option "configure as Internet connection
server". What should I check and what is missing?

thanks for any help in advance.

 

[William M. Smith]

Hi, I have the following problem.

I am going to use windows 2000 server as a router. The connection is:

Cable Modem -> Win2kServer -> Hub -> Client Workstation

I use NAT instead of ICS to route the packet. The server can ping internet
address (say, yahoo.com) and ping client workstation's IP assigned by DHCP
of the server. The problem now is that the client machine cannot connect to
the internet.

In the NAT under Route&RemoteAccess, I have check both interface configure
properly. Internet connection choose public interface connected to internet
and internal connection choose private interface connected to private
network.

I configure R&RA by selecting the option "configure as Internet connection
server". What should I check and what is missing?

Hi Henry!

Does the client workstation have problems connecting via IP address or just
name? Can you click on this link to Yahoo http://216.109.118.74/ and get
there from the client machine? If so, you have a DNS configuration problem
and may need to enter the DNS addresses manually for your workstation.

Also, be sure that the "Default Gateway" for the NIC on the private side of
your network is blank. It will automatically send Internet requests through
your public NIC.

Hope this helps! bill

 

[Gino]

I would check the IP range that the DHCP server is giving to the clients.
I'm sure that the NAT driver is is looking for 192.168.0 net ID range. When
you configure NAT on the server you have the option of using DHCP or
allowing the NAT driver to asign TCP/IP settings itself. This might be your
problem.