2nd Ethernet board causes problems

[TonyGroves]

I am setting up my small local network for DSL access by installing a second Ethernet board on the server to which I will attach the DSL "modem" which uses NAT. The second board has an address of 10.0.0.1, while the LAN has addresses of 192.168.0.x, with a subnet mask of 255.255.255.0 in both cases. Trouble is, if I enable TCP/IP for the second board (it needs it for configuration of the modem), the LAN suffers in that access to network resources on the server takes ages, as in minutes. When I disable TCP/IP on the second board, the LAN springs back to life again.

I'm sure I must be missing something simple; can anybody shed some light? Thanks.

 

[RACM]

I had a similar issue once. By uninstalling both cards and removing the TCP/IP bindings, then reinstalling both cards at the same time, the issue went away.

 

[TonyGroves]

Since then, I read in M. Minasi's Mastering NT Server that domain controllers don't like dealing with more than one subnet; apparently they get confused. So, I sacrificed a PC, put two Ethernet boards into it, installed NT Workstation which detected both boards correctly (they use the same driver), put each one into a different subnet as before, and tested. It turns out that I can ping the LAN board for about a minute at boot time before its TCP/IP silently collapses; that happens every time.

It looks like I'll have to wheel out my bootleg Win2k and see if that works (with Ethernet or USB), and then, of course, settle my debt with poor Mr. Gates.

 

[mattjurado]

For NAT translation, I would use a Linksys router. One can be had for fifty bucks or so, and you'll never have to worry about your server performing network addressing. Just an extra load that NT4 doesn't need to run. However, disabling all NetBIOS name resolution on the adapter should take care of it.

Open your bindings tab in IP properties. Make sure the card facing your lan is at the top of each protocol under the NetBIOS bindings, and I think you can disable the bindings for the second adapter altogether if memory serves. Remember the second card doesn't need to do any name resolution, only addressing.

Matt J.