TCP/IP with two NICs

So if I can't have the same IP adress on the NICs how do I configure them to work with two different IP adresses but still on the same subnet.

The thing is that I want to run TCPBUI on both my NICs.

I've installed Warp Server for E-business on the server just because of it's support for running TCPBEUI on multiple NICs.
I have MPTS V 6.0 (fix level WR08705) and TCP/IP 4.32 installed now.

Requirements for having TCPBEUI on all NICs is that TCP/IP is installed on all NICs.

I've checked redbooks and they clearly state that it shouldn't be a problem at all to run TCPBEUI on several NICs (and TCP/IP must be installed on every NIC you want to run TCPBEUI on since it's the carrier).
There are however no examples at all on how the configuration should be set up when running TCP/IP on several NICs.

I get a "duplicate name" error when trying to have both NICs on the same subnet with different IP adresses.

How do I solve this?

Thanks.

> How do I solve this?

Use only one NIC per network,
i.e., connect the second NIC to a second network.

Why are you trying to put two NICs on the same network?
Performance? (One 100Mbit NIC should be enough ?!?!)

It's for redundancy and performance (Tokenring - 16Mbit).

So Otta, is the answer that I cannot have two NICs on the same network running TCP/IP ?

Hmmm.  The performance of a token-ring cannot be improved
by putting two NICs on the same ring.  Each computer on
the ring has to wait for the token to be passed around the
ring.  So, whether a computer addresses a packet to the
first NIC on the server, or addresses a packet to the
second NIC on the server, the packet flows around the ring
at the same speed.  

The topology of a "ring" is quite-different than an
Ethernet-based LAN.  The point of a ring is to give
predictable(!) performance of the network, no matter how
busy the network gets. A lightly-loaded Ethernet-based LAN
will give better performance than a token-ring network,
but performance will signicantly degrade on a heavily-loaded
Ethernet-based LAN.

I've solved the problem with duplicate name error and now have the two NICs on the same network with two different IP adresses.

It seems to work great.

Well maybe I cannot increase performance in the way of overall throughput but since there is a limit on 254 NETBIOS/TCPBUIE sessions per NIC there is a performance increase with two NICs in a way of more users being able to access the server at the same time.

Then there is the question of redundancy. In case one NIC breaks down I still want the server to be accessible and that is quite hard to accomplish with just one NIC.

> I've solved the problem with duplicate name error

How?  All the readers of this question, now and in the future,
would like to benefit from your experience.

> In case one NIC breaks down ...

:-)  The only time that has happened to me
is when the cable connecting into the NIC
was accidentally pulled,
and it damaged the socket on the NIC.

The problem was the duplicate name error I got when connecting two NICs on the same network and that problem was indeed related to the hostname as I suspected.

The solution was very simple...it was just to remove the hostname from the IP config.

Everything seems to be working great now.

legend_aza:
This old question needs to be finalized -- accept an answer, split points, or get a refund.  For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations!  No comment means you don't care.