Microsoft networking client and NLB conflict
From: TIwang (TIwang_at_discussions.microsoft.com)
Date: 11/12/04
- Next message: Luc: "Re: Joining node error"
- Previous message: Jeff Qiu [MSFT]: "RE: Move quorum to new disk"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 12 Nov 2004 01:43:01 -0800
Hi out there
I have a problem in a 6-server NLB based cluster with windows 2000 AS. They
have all an "ap-net" interface which is used for connectivity to a database
and a "intranet" interface which is running NLB (all with a common secondary
ip which is the "big ip" for the NLB). I need SMB access to a fileshare on
the intranet which only has the nlb & ip binded as protocols - the ap-net
interface has a standard setup without nlb but with microsoft networking
client, file & print-share & the ip-protocol.
I have access to a UNC path from 4 of the 6 servers - which are identical
configured - but on the las two the session fails with "the networking path
not found". If I enable the client for microsoft networking on that interface
I am able to connect to the share.
If I look a trace from what happens from one the serveres which "works" and
compare it with one which does not work I have a difference in that the
serveres which works try to connect to the UNC path from the interface (the
ap-net interface) where it has the protocol binded - even though the ip for
the fileserver in question is on the same subnet as the interface we are
running NLB on - but those which does not work doesnt try to establish a
session at all from that interface.
Question: has anyone else seen a similary problem and what could be done??
and - what will happen with netbios names and browsing if I try to solve my
problem by enabling the microsoft networking client on the same interface
which I am running NLB on ?
Regards /thomas iwang
- Next message: Luc: "Re: Joining node error"
- Previous message: Jeff Qiu [MSFT]: "RE: Move quorum to new disk"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
