Can't netbios access W2k3 mutihomed server.

We migrate a W2k file server to a new W2k3 entreprise cluster.
This server is a multihomed server with 4 NIC on 4 dfferent IP
domains, and 4 different NT domains.
Sever is just a file and http server not PDC/BDC, shares are
clustered.
Our file server is netbios (acceding share) accesible and visible from
his primary Domain but netbios inaccessible from the others domain,
generating error 53, "network path not found"
(what were working under W2k, not visible in neihgbour but accesible
by share \\server\share), the server is accesible by pinging and for
http.
Could you help for that.

Thanks

Florian

"fatfreddy" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> We migrate a W2k file server to a new W2k3 entreprise cluster.
> This server is a multihomed server with 4 NIC on 4 dfferent IP
> domains, and 4 different NT domains.

It is impossible to be in 4 NT Domains at the same time. A machine can only
be a member of one NT Domain.

IP Domains?,...there really is no such thing. There are IP Networks and
there are IP Subnetworks,...no Domain.

Get rid of three NICs and run the machine in a single subnet with one NIC.
Route *to* the machine from other subnets instead of trying to make it
"live" in every subnet you have all at once.


--

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


> Sever is just a file and http server not PDC/BDC, shares are
> clustered.
> Our file server is netbios (acceding share) accesible and visible from
> his primary Domain but netbios inaccessible from the others domain,
> generating error 53, "network path not found"
> (what were working under W2k, not visible in neihgbour but accesible
> by share \\server\share), the server is accesible by pinging and for
> http.
> Could you help for that.
>
> Thanks
>
> Florian

>
> It is impossible to be in 4 NT Domains at the same time. A machine can only
> be a member of one NT Domain.

Thanks for the answer.
I know that it's impossible to subscribe to different domains, but
with the old server in W2k it was possible to use the share from the
different domain by net use * \\server\share even if the server wasn't
visible in the network neighbor (there is approbation beetween the
server primary domain and the others domains).

>
> IP Domains?,...there really is no such thing. There are IP Networks and
> there are IP Subnetworks,...no Domain.

Ok, terminology mistake, several Subnetwork.

>
> Get rid of three NICs and run the machine in a single subnet with one NIC.
> Route *to* the machine from other subnets instead of trying to make it
> "live" in every subnet you have all at once.

It's a production server, I could not test this kind of things.
Important information I forgot, my server is a 2003 cluster and we
experiment the problem with virtual network name (netbios resolution
checkbox is checked on the different virtual IP in the clustered group
of the virtual network name)

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

"fatfreddy" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> > IP Domains?,...there really is no such thing. There are IP Networks and
> > there are IP Subnetworks,...no Domain.
>
> Ok, terminology mistake, several Subnetwork.

That's ok, But I just have to take posts at face value, so we have to
clarify sometimes :-)

> > Get rid of three NICs and run the machine in a single subnet with one
NIC.
> > Route *to* the machine from other subnets instead of trying to make it
> > "live" in every subnet you have all at once.
>
> It's a production server, I could not test this kind of things.
> Important information I forgot, my server is a 2003 cluster and we
> experiment the problem with virtual network name (netbios resolution
> checkbox is checked on the different virtual IP in the clustered group
> of the virtual network name)

I can only say that server clustering is for multiple machines, not multiple
Nics. Even in clusters it is expected that each machine have only one Nics
(except for ISA proxy arrays). There are a ton of problems created with
multiple Nics and in your case the problems may be multiplied and
complicated by the fact that you are also clustering. If you can't "test" or
make changes because it is a production system, then you may have screwed
yourself by your design. Here are articles expressing an example of the
problems created by multihoming....

175767 - Expected Behavior of Multiple Adapters on Same Network
http://support.microsoft.com/default...b;EN-US;175767

157025 - Default Gateway Configuration for Multihomed Computers
http://support.microsoft.com/default...roduct=win2000

272294 - Active Directory Communication Fails on Multihomed Domain
Controllers
http://support.microsoft.com/default...b;en-us;272294

191611 - Symptoms of Multihomed Browsers
http://support.microsoft.com/default...b;EN-US;191611

Microsoft Windows XP - Multihoming Considerations
http://www.microsoft.com/resources/d..._tcp_qpzj.asp?


--

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