Servidor wins con dos interfaces de red

Recomiendo este artículo que es bastante viejo pero sirve:
http://www.winnetmag.com/Windows/Ar...7/107.html

Tiene el siguiente comentario:

I read Darren Mar-Elia's November 1997 article, "Implementing Enterprisewide
WINS." I have a Primary Domain Controller (PDC) with one network card (IP
address 148.53.78.5). This server is our primary Windows Internet Naming
Service (WINS) server. I don't have a second WINS server, and this WINS
server is not replicating its database. I needed to add a second network
card and I needed this server to be multihomed. When I added the second
network card-the same model as the first one-and configured with IP
148.53.78.6, I began to have strange problems. For example, the printer
stopped working, and some PCs could not reach our server. Is this the
meaning for the paragraph "Finally, forget about installing WINS on a
multihomed server. You can do this installation, but you're asking for
trouble?" To my surprise, when I tried to ping the hostname, I always got an
answer from the second network card. I changed the order of the bindings
with no success. The answer always comes from the second network card. Even
when I remove the WINS service from this server, I still get an answer to
the ping from the second network card. Many thanks and congratulations for a
good article.<br> --Fernando Pessoa Sousa<br><br>

<i>Yes, my warning about multihomed WINS applies to your configuration. Here
are a few suggestions. First, make sure you're running at least Windows NT
3.51 Service Pack 4 (SP4) on your WINS server before you attempt to
multihome it. Previous versions don't support multihoming. Next, you're
compounding your problems by having this box also be a PDC, because you have
to make other considerations for multihomed PDCs (see the Microsoft
Knowledge Base article, "Browse across subnets with a multi-homed PDC," at
http://premium.microsoft.com/suppor...903092.asp).
Remember that the WINS service (and the browser service) will bind to only
one NIC on your server. This NIC's IP address must be the one your clients
refer to in their WINS client configuration. The NIC that is bound is
supposed to be the one with the lowest binding number, as found in the
Registry under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Adapters. Several
Knowledge Base articles, including Q152705 and Q121003, discuss multihomed
WINS.<br> --Darren Mar-Elia</i>


Fernando Pessoa Sousa -August 10, 1999



"Yo mismo" escribió en el mensaje
news:

Hola.
Tengo un servidor Wins / Dns al que le he instalado una segunda tarjeta de
red, con ip fija al igual que la primera, con fines de enrutamiento.
Cuando habilito la interfaz, a partir de ese momento, la resolución

netbios

me da la ip nueva, tanto en el propio servidor como en la red local.
Cuando me voy a la consola de administración Wins, en la lista de

servidores

me aparece el servidor con la ip nueva y un símbolo de error, de que no
encuentra al servidor.
He probado a registrar el servidor con la ip primera, no funciona, al
momento me muestra la segunda ip con el error.
He intentado desabilitar netbios sobre tcpip en la segunda tarjeta, pero
nada.
He probado a borrar las entradas dns, que se crean sobre la segunda ip.

Por favor ¿me podeis indicar cómo puedo hacer para que la resolución

netbios

me reconozca la primera ip?