Cliff Johnson yrsuser@televar.com wrote:

We have a new F230 installed here (5.1R1, 1.9i firmware), with a Quad 10/100 card in it. I've configured the 4 ports, and have no problems talking to (or mounting NFS from) any of them from the Unix side of the house.

Unfortunately, the only network connection that shows up on the NT side of the house is the one on the F230 mother- board (e0), which is not the one I want the users accessing.

I can map a network drive using the 4 "other names", (only if I attach as "nobody", but that's probably another problem), but I can only "see" the main port in the network neighborhood. And I'd rather the users not have to memorize the names of the different ports.

[..]

Hi Cliff,

Is your filer's CIFS configured for WINS?

If it is, then the filer should be registering all your interfaces with the WINS server using the standard WINS multihomed registration protocol. (This is how a multihomed NT server would register with WINS.) In that situation, CIFS clients that use WINS resolution will choose one of the filer's IP addresses from the registered list. (Depending on the type of client, the address selection algorithm varies; for example, older Microsoft clients tend to choose the address randomly, while NT4 SP3 clients try to be more intelligent. Microsoft's MSDN support web site has some articles detailing this -- try searching for "multihomed" and/or "WINS".) (By the way, as of version 5.1 of Data ONTAP there is a new ifconfig option, "-wins", that can be used to disable WINS registration for a particular interface. It's documented in the na_ifconfig(1) man page. Maybe you should try setting that option on your e0 interface?)

If your filer's CIFS is *not* configured for WINS, then CIFS should be broadcasting its presence on each of its interfaces. For example, if you have two interfaces, e0 at 10.0.0.1 and e1 at 192.168.0.1, CIFS will periodically send a broadcast on e0 that reads "FILER is at 10.0.0.1", and on e1 the broadcast will read "FILER is at 192.168.0.1". (Note that each packet only mentions the IP address for its particular interface.) This is how an NT server that isn't configured for WINS would announce itself.

Hope that helps some - let me know!

Matt Day mday@netapp.com Network Appliance, Inc.