2 NICs in one box, both won't work at the same time. (Cable company trick to keep people from sharing the connection?)

[Smash144]

Here's the situation. I have two NIC's in my server running windows 2k server. One nic is connected to the cable modem, the other is to another computer via crossover cable. I'm trying to share the internet connection to the second computer through the crossover. If I have my cable nic enabled, the two computers cannot see each other or ping each other. However, if I disable the nic that the cable modem is connected to, the two computers can see just fine. I am sure windows 2k server supports a computer with two NIC's, so I'm guessing my cable company has rigged it so that the cable nic can be the only nic in the computer, in order to keep people from doing what I am trying to do. Does anyone know any way to work around this? The help is *GREATLY* appreciated.

 

[marat]

<< Here's the situation. I have two NIC's in my server running windows 2k server. One nic is connected to the cable modem, the other is to another computer via crossover cable. I'm trying to share the internet connection to the second computer through the crossover. If I have my cable nic enabled, the two computers cannot see each other or ping each other. However, if I disable the nic that the cable modem is connected to, the two computers can see just fine. I am sure windows 2k server supports a computer with two NIC's, so I'm guessing my cable company has rigged it so that the cable nic can be the only nic in the computer, in order to keep people from doing what I am trying to do. Does anyone know any way to work around this? The help is *GREATLY* appreciated. >>



Do you have DHCP enabled on second computer? Turn it off.
All network cards NOT connected to the cable company have to have static IP's (unless you want to install DHCP server or 1 machine) and they must be different - someting like 192.168.0.X/255.255.255.0
Also, check if they don't have the same hostname.

 

[Smash144]

still not working... there *is* a dhcp server on it, and it works. details of setup:

box 1:
NIC 1 - DHCP - Connected to cable modem
NIC 2 - 192.168.0.1 - DHCP/NAT server

box 2:
NIC 3 - DHCP - Connected to box1/nic 2


NIC 1 always works, box2/1 can only ping/connect to each other if NIC 1 is off.


any other suggestions?

 

[marat]

<< still not working... there *is* a dhcp server on it, and it works. details of setup:

box 1:
NIC 1 - DHCP - Connected to cable modem
NIC 2 - 192.168.0.1 - DHCP/NAT server

box 2:
NIC 3 - DHCP - Connected to box1/nic 2


NIC 1 always works, box2/1 can only ping/connect to each other if NIC 1 is off.


any other suggestions? >>



So, change NIC 3 to 192.168.0.2 ans you're in

 

[kimagurealex]

so, there is no way to have DHCP server installed on the server machine with the Cable connection?

 

[Silan]

Have you tried wingate?

 

[StuckMojo]

you've got something else wrong.
i suspect your routing tables aren't being set up right.

while the cable nic is connected and working, and the other is conencted and
not working, pull up a "dos" window and do:

ipconfig /all
route print

and post the output

[edit] in case its not obvious, run those on the server machine [/edit]

 

[Thor86]

You give your cable company too much credit, most aren't that smart.

 

[HereThereandEverywhere]

True, true, but it could be an IRQ conflict. Is your computer ACPI compatible? Cause I find when installing Win2k on older computers, it automatically thinks it's ACPI compatible, and some devices don't work due to IRQ conflicts because 2k assigns everything to 9 thinking it's a good computer when it's not (I.E. MINE!) Anyway, go to device manager, and go to computer, and see if 2k put "ACPI" on, and if your computer itself isn't ACPI (i think you can check in your bios) double click it, update driver, and go to standard PC. See if that works. ONLY DO THIS IF YOUR COMPUTER DOES NOT TO ACPI AND WINDOWS 2000 THINKS IT DOES!

good luck.

 

[dajeepster]

i'm using sygate.... works pretty well for me.... it's made by sohoware

 

[mastertech01]

Before going 2 way cable I used Wingate and it worked well. Now I use WinXP and it does all the home network setup for you so I dont need it any more.

I used 2 NIC in the server and one in the client, and a hub between the two. The one to the modem was dynamic IP, the one for sharing was 192.168.0.1, and the one in the client was 192.168.0.2.

 

[MikeMAN]

this is my vote for sygate... works well..

mike

 

[marat]

<< this is my vote for sygate... works well..

mike >>



Why pay for programs if you can do it for free ??? You CAN share network connection with windows 98, 2000, xp.

 

[SPB]

This problem is eactly what was pointed out in the first reply. Change the second pc to a static ip and your in like flyn. Then there is always the option to use 98se, ME, 2000, and XP's internet connection sharing thingy, works like a charm (its more fun to do it yourself though).

It would be entirely impossible for your cable company to rig your nic so that you couldn't share the connection. They can however see that you are sharing the connection unless your box is secure.

 

[rahvin]

YOU DON'T NEED DIFFERENT SOFTWARE.

You can't use DHCP on the server computer, why would you want to? The DHCP request is failing because the first computer is passing it on to the cable modem because you are setting the first computer up to route the connections. Disable the DHCP service on the first computer, set a static IP on the second NIC for 192.168.0.1 then set a static IP for the second computer of 192.168.0.2. It will work beautifully at that point. I still don't know why you want to run DHCP on a cross-over cable. (Hint your nameservers don't change IP, the only thing that DHCP on the cable modem changes is your IP and that doesn't matter to the second computer).

 

[JotaJ]

I don't know how to solve your problem, but its not the cable company. Me and my friend both have home networks and the two NIC/ Cable modem connection, but are running XP. I just plugged mine and i was on my way after enabling sharing.