Win2000 server with 2 NIC's ... help please!

[Bryan]

Hi,

I'm setting up a network with a server and one client. The server has a
two NIC's ( one for the cable connection and the other for the client ). The
server is able to connect to the internet .The
problem is that the client can't connect to the internet. I have the server
assigning an IP for the client using DHCP. The client and the server can
connect to each other and share files but for some reason neither can ping
each. Is there some way that the server can be used as a router and have the
client connect to the internet?

Thanks

 

[Guest]

If you are able to share files between your server and
your client, it means there is a connection and you should
be able to ping. Or may be you are using some other file
sharing protocols and not sharing files over TC/IP. If you
cant ping you might have ICMP blocked. Some firewall
installed in your server/client?
There are 2 NICs in your server. One must have IP as given
to you by your ISP and make sure you insert cable of ISP
in that NIC only. You can check which NIC is which by D/C
the ISP cable first, you will see "Local Area Network
unpluged" Rename that interface to MAIN. Second NIC is
your LAN. In the properties of MAIN select sharing. Tick
the check box, enable internet connection sharing. After
you click OK OK OK and its done, go to your second NIC.
Check if IP 192.168.0.1 was assiged to it.

Now client side.
Go to network properties and give it IP 192.168.0.2,
Subnet 255.255.255.0, gateway 192.168.0.1, DNS 192.168.0.1
Try pinging now.
Good Luck
-Nimit

 

[Bryan]

Thanks,

I'm able to ping from the server to the client and back but I'm still unable
to ping - or browse - past the server to the internet from the client. Also,
I entered the NDS suffexes and server names in the client ( although, I'm
not sure if I'm supposed to. ) Any other help would be great!!!

Thanks

 

[Doug Sherman [MVP]]

On the Server go to Administrative Tools/Routing and Remote Access. The
wizard will enable you to configure NAT to provide Internet access to the
client, or see:

http://support.microsoft.com/default.aspx?scid=kb;en-us;310357

Make sure that your DHCP scope gives the client the IP address of the
Server's internal NIC for a default gateway and the DNS server IP of your
internal DNS server, if you have one - otherwise use the ISP's DNS server
IP.

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

 

[Bryan]

Hi again,

That solved the problem. Thanks for the help.