I don't have a sun nfs client to test this, but I think either of these could work: -- Make a static WINS entry for FILE1 in your WINS servers and then force wins replication. -- on your filer use cifs.netbios_aliases to make a CIFS alias for your filer as "FILE1"
Here is my (untested) logic: Windows is resolving names in this order: NetBIOS name cache -> WINS -> broadcast -> LMHOST -> hosts file -> dns (unless you have modified the name resolution order).
when you map to \file1\users, the host "file1" cannot be resolved by NetBIOS, WINS, broadcast, LMHOSTS, or hosts, so it is resolved via dns. Windows has given up on a CIFS connection and allows the nfs client to open the connection as a socket and nfs gets the connection.
mjb
--------------------------------------------------------
neil lehrer writes:
we are ontap 6.01r3d3, nfs and cifs. clients are winnt 4.0 sp5 using sun nfs client sw and native winnt cifs.
filer dns name = file1 filer wins name = joe users is the nt share
if i do
net use * \joe\users
i get a cifs connection
if i do
net use * \file1\users
i get an nfs connection
if i try to map a drive from the explorer gui to \file1\users i get network path not found.
our normal syntax to map drives using nfs is
net use H: sunbox:/usr/local/h
is there anyway to get a cifs connection using the dns name on a client that has both nfs and cifs on it??
we want to migrate from nfs to cifs. we want to use the dns names, and we can't [easily] remove the nfs client.
thanks.
--
regards