2 NIC's in one win2k server box to run NAT

[mgm]

I would like to have a public (cable modem & using router) external network
and a private local network (crossover utp) between my 2 pc's
The box with the 2 nic's is Win03 and the client box is a WinXP Pro box.
Windows 2003 will not recognize the second nic correctly. Hardware is IDed
as a second rlt8139 nic when in fact it is a DLink. There is only 1 rlt8139
nic installed in the win03 server. the other nic is a DLink. How do I get
Win03 to properly identify and distinguish these NIC's?
I want to run NAT.

 

[Phillip Windell]

If the DLink is using a RealTech Chip, then it will detect it as RealTech.
NICs from AOpen do the same thing.

 

[mgm]

This is an AOpen nic... hmm.. will this "confusion" render the nic useless?
When placed in another pc, this aopen nic is recognized as the DLink brand
instead of the chipset.

If the DLink is using a RealTech Chip, then it will detect it as RealTech.
NICs from AOpen do the same thing.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

I would like to have a public (cable modem & using router) external network
and a private local network (crossover utp) between my 2 pc's
The box with the 2 nic's is Win03 and the client box is a WinXP Pro box.
Windows 2003 will not recognize the second nic correctly. Hardware is IDed
as a second rlt8139 nic when in fact it is a DLink. There is only 1 rlt8139
nic installed in the win03 server. the other nic is a DLink. How do I get
Win03 to properly identify and distinguish these NIC's?
I want to run NAT.

 

[Phillip Windell]

If it works then it works. The chip *is* the NIC reguardless of who packaged
it an sold it. If you have the actual driver from the manufacturer for the
correct OS then use it, otherwise just let the OS go with whatever it
"thinks" it is and let it run.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

This is an AOpen nic... hmm.. will this "confusion" render the nic useless?
When placed in another pc, this aopen nic is recognized as the DLink brand
instead of the chipset.

If the DLink is using a RealTech Chip, then it will detect it as RealTech.
NICs from AOpen do the same thing.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

I would like to have a public (cable modem & using router) external network
and a private local network (crossover utp) between my 2 pc's
The box with the 2 nic's is Win03 and the client box is a WinXP Pro box.
Windows 2003 will not recognize the second nic correctly. Hardware is IDed
as a second rlt8139 nic when in fact it is a DLink. There is only 1 rlt8139
nic installed in the win03 server. the other nic is a DLink. How do I get
Win03 to properly identify and distinguish these NIC's?
I want to run NAT.

 

[Mike Brown]

This is an AOpen nic... hmm.. will this "confusion" render the nic useless?
When placed in another pc, this aopen nic is recognized as the DLink brand
instead of the chipset.

The problem you're having is pretty common. I've had the same issue with
teaming NICs, dual-display video, and "shotgunning" modems, all in cases
where the two pieces of hardware were the same or similar. The easiest way
around this is to get two pieces of hardware that are not so similar. In
your case, a NIC from 3Com or Intel would work fine.

There should be an easier solution for you though. Just open Device
Manager, and update the driver for the NIC you are having trouble with.
When prompted, insert the driver disk and browse to the folder for the
driver. This should load the same driver that your other box is using
(which makes it detect as "DLink" instead of the generic "Realtek".) You
may want to do this with your other NIC as well, if you can find a good
driver for it. Realtek does not sell network cards, they only produce the
chips for other companies. Your OEM manufacturer of the card should provide
a driver.

--

Mike Brown
Process Manager

Asset Forwarding Corp.
EPA-compliant Recycling
DoD 5220.22-M Data Elimination
http://www.assetforwarding.com