Windows 2003 - 2 NIC license problem.

redhat_newbie

Dear All,

Server: 2 NIC's
OS : Windows server 2003

3D application license is configured to NIC 1 IP

NIC 1 = 10.1.1.201
NIC 2 = 192.168.128.111 connected to disk storage

3D application launches when NIC 2 is disabled. When NIC 2 is enabled it says license error and aborts the application launch.

Any Windows Admin enthusiasts here to help me out to solve this problem. I am new to Channel bonding and NIC teaming. Any help in this regard would e appreciated.

Contact the support team to revoke NIC 1 (IP) license and issue for the IP on NIC 2. But this doesn't really give solution to the problem if there are 200 more machines are to be added.

Cheers

Capt'n Midnight

the license is most likely bound to the MAC of one of the cards

at the command prompt type
ipconfig /all to see the MAC


If the binding is done by the network driver then there should be a utility that allows you to choose which of the MAC's to use when bound together.

redhat_newbie

No license is bound to the IP and not to the MAC.
I have confirmed that.

Thanks for thinking here.

cance

this isn't nic teaming, this is using two network cards.

Its a software vendor issue, escalate it to them.

LoLth

Just out of curiosity, is NIC temaing with 2 Ipaddresses applied to the virtual interface an option or do the nics *have* to (physically) be on two seperate LANs ?

irishpartyboy

NIC teaming is to provide redundancy. There are various different options, depending on manufacturer. You would normally configure the virtual interface with a single IP address, same LAN. You may configure one of the nics to act as primary / active and leave the other as standby. The two nics may be plugged into separate switches. That would typically be called Switch Fault Tolerant, again depending on manufacturers terminology.

Capt'n Midnight

it can also provide more bandwidth depending on how it's setup

if you do it at the network driver level not only do you get one IP you can also get one MAC

and yes you can put both in to the same switch


on a different note you can have two IP's on one NIC , very handy when doing an IP changeover , one trick is to setup ipenablerouting in the registry on the box that gets most traffic so clients on either subnet don't try to go through a router if they get the other IP from a dns request or whatever.

redhat_newbie

Thanks for all the thinking and discussion here lads. Seems to be
1) NIC teaming
2) Channel Bonding/Binding
3) Vendor issue here.

Will escalate the problem to the respective groups.

Many thanks.