I have a small LAN of 3 machines. W2K Server, W2K Pro, and Suse 7.1. My server (W2K Server) has 3 NIC's. NIC1 is connected to a Cisco router which does NAT and the address is 10.0.0.3. NIC2 is connected to W2K Pro machine and it's IP is 192.168.0.1. NIC3 is connected to a machine running Suse 7.1 and it's address is 192.168.0.119. I need help connecting the Suse box to my NT LAN. From my Suse box (192.168.0.120) I can only ping 192.168.0.119, every other connection times out. W2K Server and Pro can ping anything but my Suse box. I know I need to configure Samba before I can share directories on my NT LAN, but do I need to configure Samba for an internet connection.
Also, my server has Active Directory set up, along with DNS, WINS, DHCP, and so forth, just in case that would make a difference. Is the default gateway of my Suse NIC 192.168.0.119, 10.0.0.3, or my outside IP address? Any help or suggestions would be great, thanks in advance guys....

Changed the address of the SuSE NIC in my server to 192.168.1.1, and the address of my SuSE machine to 192.168.1.2, and I can now ping everything. Still have no internet connection though. Anyone got anything for me, or see what I'm doing wrong from the info I gave.

Your default gateway will be the address of your router. You'll clearly also need to ensure that your DNS is working correctly so have a look at /etc/resolv.conf and put your DNS servers in there. You can always test DNS from the command line by using nslookup

cheers

Jamie...

I checked to resolv.conf file just to make sure, and the entries were there. I also tried switching the default gateway of the NIC in my SuSE machine to both the address of my router before and after NAT, and neither of those changed anything. I am really starting to think it is a problem with active directory and not my NIC configuration, but I can't figure out where. DHCP works fine for my 2000 Pro machine, so why not my Linux box as well. Well thanks for trying jharris.......

In W2k did you share the interface that is your internet connection.

The common interface between the server and clients must also be on the same network.

I figured out last night that it wasn't a Linux problem. I had ICS configured in Windows, but I have 3 NIC's. ICS only works with one NIC therefore I have to look else where for a cure. I wouldn't stoop nor plague this forum with a Winblows question. I do appriciate all the advise though, thanks a lot......

It should work.

You just enable sharing of the one nic that is connected to the internet, in the connection properties/sharing tab. then the ip of your other nic needs to be on the network of your other machines. I replaced my linux server at work with my win2k laptop temporarily while installing a zip drive, using an onboard nic and a pcmcia one.