Problem with multiples NIC

Hi,
I have a problem with two NIC´s on W2K3 Server. I think taht is a problem
with concepts of comunication process.
The Server has activate FTP and Microsoft network resource with IP
192.168.10.24 (DNS and NetBios name point it), Server has others NIC, one of
theirs with IP 10.12.34.250. I need configure route tables for when a
petition from an IP 10.12.34.x is received forward ftp or NetBios name, the
answer was on this interface always and not on NIC 10.12.34.250.

Information for "route print" and "ipconfig":
Rutas activas:
Destino de red Máscara de red Puerta de acceso Interfaz Métrica
0.0.0.0 0.0.0.0 192.168.10.1 192.168.10.24 10
10.12.34.0 255.255.255.0 10.12.34.250 10.12.34.250 5
10.12.34.250 255.255.255.255 127.0.0.1 127.0.0.1 5
10.255.255.255 255.255.255.255 10.12.34.250 10.12.34.250 5
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
169.254.0.0 255.255.0.0 169.254.49.12 169.254.49.12 10
169.254.49.12 255.255.255.255 127.0.0.1 127.0.0.1 10
169.254.255.255 255.255.255.255 169.254.49.12 169.254.49.12 10
192.168.10.0 255.255.255.0 192.168.10.24 192.168.10.24 10
192.168.10.24 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.10.255 255.255.255.255 192.168.10.24 192.168.10.24 10
192.168.30.0 255.255.255.0 192.168.30.38 192.168.30.38 10
192.168.30.38 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.30.255 255.255.255.255 192.168.30.38 192.168.30.38 10
224.0.0.0 240.0.0.0 10.12.34.250 10.12.34.250 5
224.0.0.0 240.0.0.0 169.254.49.12 169.254.49.12 10
224.0.0.0 240.0.0.0 192.168.10.24 192.168.10.24 10
224.0.0.0 240.0.0.0 192.168.30.38 192.168.30.38 10
255.255.255.255 255.255.255.255 10.12.34.250 10.12.34.250 1
255.255.255.255 255.255.255.255 169.254.49.12 169.254.49.12 1
255.255.255.255 255.255.255.255 192.168.10.24 192.168.10.24 1
255.255.255.255 255.255.255.255 192.168.30.38 192.168.30.38 1
Puerta de enlace predeterminada: 192.168.10.1
================================================== =========================
Rutas persistentes:
Ninguno


Configuración IP de Windows


Adaptador Ethernet Red de almacenamiento 192.168.30.38:

Sufijo conexión especÃ*fica DNS:
Dirección IP. . . . . . . . . : 192.168.30.38
Máscara de subred . . . . . . : 255.255.255.0
Puerta de enlace predet.. . . :

Adaptador Ethernet Red de Servidores Internos 192.168.10.24:

Sufijo conexión especÃ*fica DNS:
Dirección IP. . . . . . . . . : 192.168.10.24
Máscara de subred . . . . . . : 255.255.255.0
Puerta de enlace predet.. . . : 192.168.10.1

Adaptador Ethernet Conexión de área local 2:

Sufijo conexión especÃ*fica DNS:
Dirección IP de autoconfig. . : 169.254.49.12
Máscara de subred . . . . . . : 255.255.0.0
Puerta de enlace predet.. . . :

Adaptador Ethernet Soporte (10.12.34):

Sufijo conexión especÃ*fica DNS:
Dirección IP. . . . . . . . . : 10.12.34.250
Máscara de subred . . . . . . : 255.255.255.0
Puerta de enlace predet.. . . :


Thanks

In news:0D2707C8-BD51-4582-936B-(E-Mail Removed),
JFAnor <(E-Mail Removed)> stated, which I commented on
below:
> Hi,
> I have a problem with two NIC´s on W2K3 Server. I think taht is a
> problem with concepts of comunication process.
> The Server has activate FTP and Microsoft network resource with IP
> 192.168.10.24 (DNS and NetBios name point it), Server has others NIC,
> one of theirs with IP 10.12.34.250. I need configure route tables for
> when a petition from an IP 10.12.34.x is received forward ftp or
> NetBios name, the answer was on this interface always and not on NIC
> 10.12.34.250.
>
> Information for "route print" and "ipconfig":
> Rutas activas:
> Destino de red Máscara de red Puerta de acceso Interfaz
> Métrica
> 0.0.0.0 0.0.0.0 192.168.10.1 192.168.10.24
> 10
> 10.12.34.0 255.255.255.0 10.12.34.250 10.12.34.250
> 5
> 10.12.34.250 255.255.255.255 127.0.0.1 127.0.0.1
> 5
> 10.255.255.255 255.255.255.255 10.12.34.250 10.12.34.250
> 5 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
> 1 169.254.0.0 255.255.0.0 169.254.49.12 169.254.49.12
> 10 169.254.49.12 255.255.255.255 127.0.0.1
> 127.0.0.1 10 169.254.255.255 255.255.255.255 169.254.49.12
> 169.254.49.12 10 192.168.10.0 255.255.255.0
> 192.168.10.24 192.168.10.24 10 192.168.10.24
> 255.255.255.255 127.0.0.1 127.0.0.1 10
> 192.168.10.255 255.255.255.255 192.168.10.24 192.168.10.24
> 10 192.168.30.0 255.255.255.0 192.168.30.38 192.168.30.38
> 10 192.168.30.38 255.255.255.255 127.0.0.1 127.0.0.1
> 10 192.168.30.255 255.255.255.255 192.168.30.38
> 192.168.30.38 10 224.0.0.0 240.0.0.0
> 10.12.34.250 10.12.34.250 5 224.0.0.0
> 240.0.0.0 169.254.49.12 169.254.49.12 10 224.0.0.0
> 240.0.0.0 192.168.10.24 192.168.10.24 10 224.0.0.0
> 240.0.0.0 192.168.30.38 192.168.30.38 10 255.255.255.255
> 255.255.255.255 10.12.34.250 10.12.34.250 1
> 255.255.255.255 255.255.255.255 169.254.49.12 169.254.49.12
> 1 255.255.255.255 255.255.255.255 192.168.10.24 192.168.10.24
> 1 255.255.255.255 255.255.255.255 192.168.30.38 192.168.30.38
> 1 Puerta de enlace predeterminada: 192.168.10.1
>
> ================================================== =========================
> Rutas persistentes: Ninguno
>
>
> Configuración IP de Windows
>
>
> Adaptador Ethernet Red de almacenamiento 192.168.30.38:
>
> Sufijo conexión específica DNS:
> Dirección IP. . . . . . . . . : 192.168.30.38
> Máscara de subred . . . . . . : 255.255.255.0
> Puerta de enlace predet.. . . :
>
> Adaptador Ethernet Red de Servidores Internos 192.168.10.24:
>
> Sufijo conexión específica DNS:
> Dirección IP. . . . . . . . . : 192.168.10.24
> Máscara de subred . . . . . . : 255.255.255.0
> Puerta de enlace predet.. . . : 192.168.10.1
>
> Adaptador Ethernet Conexión de área local 2:
>
> Sufijo conexión específica DNS:
> Dirección IP de autoconfig. . : 169.254.49.12
> Máscara de subred . . . . . . : 255.255.0.0
> Puerta de enlace predet.. . . :
>
> Adaptador Ethernet Soporte (10.12.34):
>
> Sufijo conexión específica DNS:
> Dirección IP. . . . . . . . . : 10.12.34.250
> Máscara de subred . . . . . . : 255.255.255.0
> Puerta de enlace predet.. . . :
>
>
> Thanks

Is this a DC? If so, it will definitely be problematic and cause AD errors.

Only one NIC can be NetBIOS enabled. Disable it on the other NICs. I assume
the default NIC is: "Adaptador Ethernet Red de Servidores Internos
192.168.10.24:". If so, only have NetBIOS on this NIC enabled.

Cann you elaborate on this request please? I am having difficulty
understanding exactly what you are asking.
> "I need configure route tables for
> when a petition from an IP 10.12.34.x is received forward ftp or
> NetBios name, the answer was on this interface always and not on NIC
> 10.12.34.250."

--
Ace
Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...

Thanks for your quick reply.

I will intent to explain better the case.

This Server (W2K3) isn´t DC Server and is not belong to any AD. It´s in a
workGroup named SOPORTE. It has two NetBios names, "AULAS3" and "DESCARGAS"
and some alias in DNS.

I will intent explain better the question.

When a workstation in VLAN 10.12.34.0 makes one request NetBios or FTP to
this server, it goes through 192.168.10.24 and the response go on
10.12.34.250. I need that the response to NetBios and FTP go on 192.168.10.24
and other request tcp from 10.12.34.x will go to 10.12.34.250, that is to
say, the server must respond through the NIC by where the request arrives to
him.

, I know that this is possible in linux S.O. for example, but I don´t know
if this is possible in Windows.


The configurations NetBios and TCPIP are:

C:\Documents and Settings\Manager>nbtstat -n

Soporte (10.12.34):
Dirección IP: [10.12.34.250] Id. de ámbito : []

No hay nombres en la caché

Red de almacenamiento 192.168.30.38:
Dirección IP: [192.168.30.38] Id. de ámbito : []

No hay nombres en la caché

Red de Servidores Internos 192.168.10.24:
Dirección IP: [192.168.10.24] Id. de ámbito : []

Tabla de nombres locales NetBIOS

Nombre Tipo Estado
---------------------------------------------
AULAS3 <00> Único Registrado
SOPORTE <00> Grupo Registrado
AULAS3 <20> Único Registrado
SOPORTE <1E> Grupo Registrado
SOPORTE <1D> Único Registrado
..__MSBROWSE__.<01> Grupo Registrado
ConfigServer <1C> Grupo Registrado
pc-mi-nombre <2D> Único Registrado

Conexión de área local 2:
Dirección IP: [169.254.49.12] Id. de ámbito : []

No hay nombres en la caché


C:\Documents and Settings\Manager>ipconfig /all

Configuración IP de Windows

Nombre del host . . . . . . . : aulas3
Sufijo DNS principal . . . . :
Tipo de nodo. . . . . . . . . : hÃ*brido
Enrutamiento IP habilitado. . : SÃ*
Proxy WINS habilitado . . . . : No

Adaptador Ethernet Red de almacenamiento 192.168.30.38:

Sufijo conexión especÃ*fica DNS:
Descripción . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #2
Dirección fÃ*sica. . . . . . . : 00-13-72-5C-57-CD
DHCP habilitado . . . . . . . : No
Dirección IP. . . . . . . . . : 192.168.30.38
Máscara de subred . . . . . . : 255.255.255.0
Puerta de enlace predet.. . . :
Servidores DNS. . . . . . . . : 193.145.138.100
193.145.138.200
192.168.10.27
192.168.10.25
Servidor WINS principal . . . : 192.168.10.27
Servidor WINS secundario. . . : 192.168.10.25
NetBios sobre TCPIP . . . . . : Deshabilitado

Adaptador Ethernet Red de Servidores Internos 192.168.10.24:

Sufijo conexión especÃ*fica DNS:
Descripción . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Dirección fÃ*sica. . . . . . . : 00-13-72-5C-57-CC
DHCP habilitado . . . . . . . : No
Dirección IP. . . . . . . . . : 192.168.10.24
Máscara de subred . . . . . . : 255.255.255.0
Puerta de enlace predet.. . . : 192.168.10.1
Servidores DNS. . . . . . . . : 192.168.10.27
192.168.10.25
193.145.138.100
193.145.138.200
Servidor WINS principal . . . : 192.168.10.27
Servidor WINS secundario. . . : 192.168.10.25

Adaptador Ethernet Conexión de área local 2:

Sufijo conexión especÃ*fica DNS:
Descripción . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port Server
Adapter #2
Dirección fÃ*sica. . . . . . . : 00-04-23-CE-3D-CF
DHCP habilitado . . . . . . . : No
Autoconfiguración habilitada : SÃ*
Dirección IP de autoconfig. . : 169.254.49.12
Máscara de subred . . . . . . : 255.255.0.0
Puerta de enlace predet.. . . :
Servidor WINS principal . . . : 192.168.10.27
Servidor WINS secundario. . . : 192.168.10.25
NetBios sobre TCPIP . . . . . : Deshabilitado

Adaptador Ethernet Soporte (10.12.34):

Sufijo conexión especÃ*fica DNS:
Descripción . . . . . . . . . : TEAM : Team Aulas - Adaptive Load
Balancing Mode - VLAN : Soporte (10.12.34)
Dirección fÃ*sica. . . . . . . : 00-04-23-CE-3D-CE
DHCP habilitado . . . . . . . : No
Dirección IP. . . . . . . . . : 10.12.34.250
Máscara de subred . . . . . . : 255.255.255.0
Puerta de enlace predet.. . . :
NetBios sobre TCPIP . . . . . : Deshabilitado

Thanks for its attention.




"Ace Fekay [MVP]" wrote:

> In news:0D2707C8-BD51-4582-936B-(E-Mail Removed),
> JFAnor <(E-Mail Removed)> stated, which I commented on
> below:
> > Hi,
> > I have a problem with two NIC´s on W2K3 Server. I think taht is a
> > problem with concepts of comunication process.
> > The Server has activate FTP and Microsoft network resource with IP
> > 192.168.10.24 (DNS and NetBios name point it), Server has others NIC,
> > one of theirs with IP 10.12.34.250. I need configure route tables for
> > when a petition from an IP 10.12.34.x is received forward ftp or
> > NetBios name, the answer was on this interface always and not on NIC
> > 10.12.34.250.
> >
> > Information for "route print" and "ipconfig":
> > Rutas activas:
> > Destino de red Máscara de red Puerta de acceso Interfaz
> > Métrica
> > 0.0.0.0 0.0.0.0 192.168.10.1 192.168.10.24
> > 10
> > 10.12.34.0 255.255.255.0 10.12.34.250 10.12.34.250
> > 5
> > 10.12.34.250 255.255.255.255 127.0.0.1 127.0.0.1
> > 5
> > 10.255.255.255 255.255.255.255 10.12.34.250 10.12.34.250
> > 5 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
> > 1 169.254.0.0 255.255.0.0 169.254.49.12 169.254.49.12
> > 10 169.254.49.12 255.255.255.255 127.0.0.1
> > 127.0.0.1 10 169.254.255.255 255.255.255.255 169.254.49.12
> > 169.254.49.12 10 192.168.10.0 255.255.255.0
> > 192.168.10.24 192.168.10.24 10 192.168.10.24
> > 255.255.255.255 127.0.0.1 127.0.0.1 10
> > 192.168.10.255 255.255.255.255 192.168.10.24 192.168.10.24
> > 10 192.168.30.0 255.255.255.0 192.168.30.38 192.168.30.38
> > 10 192.168.30.38 255.255.255.255 127.0.0.1 127.0.0.1
> > 10 192.168.30.255 255.255.255.255 192.168.30.38
> > 192.168.30.38 10 224.0.0.0 240.0.0.0
> > 10.12.34.250 10.12.34.250 5 224.0.0.0
> > 240.0.0.0 169.254.49.12 169.254.49.12 10 224.0.0.0
> > 240.0.0.0 192.168.10.24 192.168.10.24 10 224.0.0.0
> > 240.0.0.0 192.168.30.38 192.168.30.38 10 255.255.255.255
> > 255.255.255.255 10.12.34.250 10.12.34.250 1
> > 255.255.255.255 255.255.255.255 169.254.49.12 169.254.49.12
> > 1 255.255.255.255 255.255.255.255 192.168.10.24 192.168.10.24
> > 1 255.255.255.255 255.255.255.255 192.168.30.38 192.168.30.38
> > 1 Puerta de enlace predeterminada: 192.168.10.1
> >
> > ================================================== =========================
> > Rutas persistentes: Ninguno
> >
> >
> > Configuración IP de Windows
> >
> >
> > Adaptador Ethernet Red de almacenamiento 192.168.30.38:
> >
> > Sufijo conexión especÃ*fica DNS:
> > Dirección IP. . . . . . . . . : 192.168.30.38
> > Máscara de subred . . . . . . : 255.255.255.0
> > Puerta de enlace predet.. . . :
> >
> > Adaptador Ethernet Red de Servidores Internos 192.168.10.24:
> >
> > Sufijo conexión especÃ*fica DNS:
> > Dirección IP. . . . . . . . . : 192.168.10.24
> > Máscara de subred . . . . . . : 255.255.255.0
> > Puerta de enlace predet.. . . : 192.168.10.1
> >
> > Adaptador Ethernet Conexión de área local 2:
> >
> > Sufijo conexión especÃ*fica DNS:
> > Dirección IP de autoconfig. . : 169.254.49.12
> > Máscara de subred . . . . . . : 255.255.0.0
> > Puerta de enlace predet.. . . :
> >
> > Adaptador Ethernet Soporte (10.12.34):
> >
> > Sufijo conexión especÃ*fica DNS:
> > Dirección IP. . . . . . . . . : 10.12.34.250
> > Máscara de subred . . . . . . : 255.255.255.0
> > Puerta de enlace predet.. . . :
> >
> >
> > Thanks
>
> Is this a DC? If so, it will definitely be problematic and cause AD errors.
>
> Only one NIC can be NetBIOS enabled. Disable it on the other NICs. I assume
> the default NIC is: "Adaptador Ethernet Red de Servidores Internos
> 192.168.10.24:". If so, only have NetBIOS on this NIC enabled.
>
> Cann you elaborate on this request please? I am having difficulty
> understanding exactly what you are asking.
> > "I need configure route tables for
> > when a petition from an IP 10.12.34.x is received forward ftp or
> > NetBios name, the answer was on this interface always and not on NIC
> > 10.12.34.250."
>
> --
> Ace
> Innovative IT Concepts, Inc (IITCI)
> Willow Grove, PA
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Directory Services
> Microsoft Certified Trainer
>
> Having difficulty reading or finding responses to your post?
> Instead of the website you're using, I suggest to use OEx (Outlook Express
> or any other newsreader), and configure a news account, pointing to
> news.microsoft.com. This is a direct link to the Microsoft Public
> Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
> to easily find, track threads, cross-post, sort by date, poster's name,
> watched threads or subject.
> It's easy:
>
> How to Configure OEx for Internet News
> http://support.microsoft.com/?id=171164
>
> Infinite Diversities in Infinite Combinations
> Assimilation Imminent. Resistance is Futile
> "Very funny Scotty. Now, beam down my clothes."
>
> The only constant in life is change...
>
>
>
>
>
>
>
>

In news:86297D54-C58D-4659-88C6-(E-Mail Removed),
JFAnor <(E-Mail Removed)> stated, which I commented on
below:
> Thanks for your quick reply.
>
> I will intent to explain better the case.
>
> This Server (W2K3) isn´t DC Server and is not belong to any AD. It´s
> in a workGroup named SOPORTE. It has two NetBios names, "AULAS3" and
> "DESCARGAS" and some alias in DNS.
>
> I will intent explain better the question.
>
> When a workstation in VLAN 10.12.34.0 makes one request NetBios or
> FTP to this server, it goes through 192.168.10.24 and the response go
> on
> 10.12.34.250. I need that the response to NetBios and FTP go on
> 192.168.10.24 and other request tcp from 10.12.34.x will go to
> 10.12.34.250, that is to say, the server must respond through the
> NIC by where the request arrives to him.
>
> , I know that this is possible in linux S.O. for example, but I don´t
> know if this is possible in Windows.



Sorry for the late response. In IIS, under the FTP site properties, tell it
to only listen to that IP address. Say if you want two FTP services running,
one for IP address 10.12.34.250, and one for 192.168.10.24, then configure
each FTP site to only use that IP address. Change the IP address of the FTP
site from "All Unassigned" to the actual IP.


>
>
> The configurations NetBios and TCPIP are:
>
> C:\Documents and Settings\Manager>nbtstat -n
>
> Soporte (10.12.34):
> Dirección IP: [10.12.34.250] Id. de ámbito : []
>
> No hay nombres en la caché
>
> Red de almacenamiento 192.168.30.38:
> Dirección IP: [192.168.30.38] Id. de ámbito : []
>
> No hay nombres en la caché
>
> Red de Servidores Internos 192.168.10.24:
> Dirección IP: [192.168.10.24] Id. de ámbito : []
>
> Tabla de nombres locales NetBIOS
>
> Nombre Tipo Estado
> ---------------------------------------------
> AULAS3 <00> Único Registrado
> SOPORTE <00> Grupo Registrado
> AULAS3 <20> Único Registrado
> SOPORTE <1E> Grupo Registrado
> SOPORTE <1D> Único Registrado
> ..__MSBROWSE__.<01> Grupo Registrado
> ConfigServer <1C> Grupo Registrado
> pc-mi-nombre <2D> Único Registrado
>
> Conexión de área local 2:
> Dirección IP: [169.254.49.12] Id. de ámbito : []
>
> No hay nombres en la caché
>
>
> C:\Documents and Settings\Manager>ipconfig /all
>
> Configuración IP de Windows
>
> Nombre del host . . . . . . . : aulas3
> Sufijo DNS principal . . . . :
> Tipo de nodo. . . . . . . . . : híbrido
> Enrutamiento IP habilitado. . : Sí
> Proxy WINS habilitado . . . . : No
>
> Adaptador Ethernet Red de almacenamiento 192.168.30.38:
>
> Sufijo conexión específica DNS:
> Descripción . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection #2 Dirección física. . . . . . . : 00-13-72-5C-57-CD
> DHCP habilitado . . . . . . . : No
> Dirección IP. . . . . . . . . : 192.168.30.38
> Máscara de subred . . . . . . : 255.255.255.0
> Puerta de enlace predet.. . . :
> Servidores DNS. . . . . . . . : 193.145.138.100
> 193.145.138.200
> 192.168.10.27
> 192.168.10.25
> Servidor WINS principal . . . : 192.168.10.27
> Servidor WINS secundario. . . : 192.168.10.25
> NetBios sobre TCPIP . . . . . : Deshabilitado
>
> Adaptador Ethernet Red de Servidores Internos 192.168.10.24:
>
> Sufijo conexión específica DNS:
> Descripción . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection Dirección física. . . . . . . : 00-13-72-5C-57-CC
> DHCP habilitado . . . . . . . : No
> Dirección IP. . . . . . . . . : 192.168.10.24
> Máscara de subred . . . . . . : 255.255.255.0
> Puerta de enlace predet.. . . : 192.168.10.1
> Servidores DNS. . . . . . . . : 192.168.10.27
> 192.168.10.25
> 193.145.138.100
> 193.145.138.200
> Servidor WINS principal . . . : 192.168.10.27
> Servidor WINS secundario. . . : 192.168.10.25
>
> Adaptador Ethernet Conexión de área local 2:
>
> Sufijo conexión específica DNS:
> Descripción . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port
> Server Adapter #2
> Dirección física. . . . . . . : 00-04-23-CE-3D-CF
> DHCP habilitado . . . . . . . : No
> Autoconfiguración habilitada : Sí
> Dirección IP de autoconfig. . : 169.254.49.12
> Máscara de subred . . . . . . : 255.255.0.0
> Puerta de enlace predet.. . . :
> Servidor WINS principal . . . : 192.168.10.27
> Servidor WINS secundario. . . : 192.168.10.25
> NetBios sobre TCPIP . . . . . : Deshabilitado
>
> Adaptador Ethernet Soporte (10.12.34):
>
> Sufijo conexión específica DNS:
> Descripción . . . . . . . . . : TEAM : Team Aulas - Adaptive Load
> Balancing Mode - VLAN : Soporte (10.12.34)
> Dirección física. . . . . . . : 00-04-23-CE-3D-CE
> DHCP habilitado . . . . . . . : No
> Dirección IP. . . . . . . . . : 10.12.34.250
> Máscara de subred . . . . . . : 255.255.255.0
> Puerta de enlace predet.. . . :
> NetBios sobre TCPIP . . . . . : Deshabilitado
>
> Thanks for its attention.


Duplicate NetBIOS names do not work with Windows. A Windows operating system
can only have ONE NetBIos name, no more. That's why on multi-home machines,
if you'll need to disable NetBIOS on all NICs but the one you want to work
with.

You can have multiple aliases, but that may not work with NetBIOS either.
Here's are some articles to read up on it.

How can I define multiple NetBIOS names for a machine:
http://www.windows2000faq.com/Articl...rticleID=14475

Connecting to SMB share on a Windows 2000-based computer or a Windows Server
2003-based computer may not work with an alias name:
http://support.microsoft.com/default...b;en-us;281308

297087 - An Additional NetBIOS Name computer name$03 Is Registered By
Windows 2000:
http://support.microsoft.com/default...en-us%3B297087

The additonal [mulitple] NetBIOS name of my server does not work for print
services.:
http://www.windows2000faq.com/Articl...rticleID=14529

Windows NT Windows Names Aliases - cnames and dupe names:
http://www.experts-exchange.com/Oper..._20410956.html


Ace

>
> Sorry for the late response. In IIS, under the FTP site properties, tell it
> to only listen to that IP address. Say if you want two FTP services running,
> one for IP address 10.12.34.250, and one for 192.168.10.24, then configure
> each FTP site to only use that IP address. Change the IP address of the FTP
> site from "All Unassigned" to the actual IP.
>

Thanks, but the problem persists, the second NIC 10.12.34.250 is used to
transmit larger file of imaging of our PC WorkStation community, and donot
need NetBios Service, nor FTP Service. Since this services are behind
firewall, the TCP connection doesnt established when the server respond
through this NIC and it does not response through firewall NIC.

The solution encountered is to put the NIC 192.168.10.24 out the firewall
and then don´t matter for which NIC response go on.

Thanks for all in any case

In news:E6A8A808-18F8-407B-BD52-(E-Mail Removed),
JFAnor <(E-Mail Removed)> stated, which I commented on
below:

> Thanks, but the problem persists, the second NIC 10.12.34.250 is used
> to transmit larger file of imaging of our PC WorkStation community,
> and donot need NetBios Service, nor FTP Service. Since this services
> are behind firewall, the TCP connection doesnt established when the
> server respond through this NIC and it does not response through
> firewall NIC.
>
> The solution encountered is to put the NIC 192.168.10.24 out the
> firewall and then don´t matter for which NIC response go on.
>
> Thanks for all in any case

Glad you figured out a solution.

Ace