I have 2 (well really 3, but 2 enabled) network cards in my windows 2000 machine. I have one set to automatically find an ip and connect to the internet. I have the other set statically to 192.168.0.2. My problem is that when i boot up and try to get to the internet, it tries to use 192.x.x.x to get there. I have to disable that NIC, then access the internet, then re-enable it. After i re-enable it, it will still have internet access. Is there any way to tell win2k to use the internet NIC to get to the internet? Also, the only reason I am doing this is because of a stupid flaw. If i statically assign one NIC with the proper internet address and local address, then i can connect to both networks no problem. The only problem is my internet address changes every so often, so i need to use DHCP. And of course thanks to windows you cannot use DHCP and static IPs on the same interface. Is there any way around that, possibly?

why dont you use the nic it goes to first for your wan connection, and the other one for your lan connections. you might also try getting a static ip from your service provider, and using dhcp on you lan w/ static srv ip.

The NIC that's getting your internet address can only be the one connected to the internet. Since you receive the DHCP assigned IP address from the ISP's DHCP server, the NIC that the internet cable is plugged into is the only NIC that can get that address...and the only NIC that can be used to access the external network. I'm not quite sure what the problem is you're having because the original post was a little unclear but I'm thinking it's very similar to a problem I've been having with one of my computers ever since I installed 2000 on it and added a second NIC. This is the problem I have: On a fresh boot, neither my internet or LAN work until I disable, then reenable the LAN NIC. Once I do that, everything works fine. I've spent quite a bit of time trying to prevent this from happening and have found no resolution for the problem. In the end, I've come to the conclusion it's an incompatibility issue between the hardware and the operating system. The problem is unrelated to the NIC's (I've tried many different NIC's in various configurations all with no luck) I'm thinking this is the same problem the original poster is having too. If it is, please email me with your system spec's. If yours has the same mobo and/or CPU as mine, I would be inclined to believe it is indeed an incompatibility issue. On a side note, I've tried various ways to automatically disable then reenable the LAN NIC using the netsh command....but never did find a way to do it...although, I did figure out how to change a NIC from DHCP to static (and back) on the fly using the the netsh command. It's a minor annoyance as I rarely ever reboot my server anyhow...but it would be nice to resolve the issue so I could remote reboot the server if it became necessary.

Did you mention whether your connected to a hub or router. I think what your trying to do is share both nic cards. The card your using for your internet connection can not be used for anything else.....unless you manually change the settings. Having the third card may not be advised. Having more than two nic cards is bound to cause mixups or conflicts. Especially if they are identical cards.....with Windows 2000 it can be difficult to tell which card is doing what.

Make sure that the 1st lan connection is the one connected to the internet or you can go into the advanced settings of the network properties to move your internet connection to the top of the "use" order.

Take a look at XP post 33120 and NT post 18902. The gist of these posts is to not have a default gateway on the internal LAN NIC. HTH

Thank you all for your awesome input! 1. I apologize for not posting clearly 2. I apologize for not replying sooner 3. Simply taking off the default gateway from the local network's NIC solved the problem entirely. Thanks again!