Mark Johnson-Barbier wrote:
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.
this by itself does not work, even on a pc with only netbios. i can ping, but nbtstat and net use fail.
-- on your filer use cifs.netbios_aliases to make a CIFS alias for your filer as "FILE1"
this works on a pc that only has tcp and netbios, no nfs client.
it seems to work entirely properly with a local host file entry.
the other thing we see that may have nothing at all to do with it is that the filers host name is in dns as an "A" record, but file1 is a CNAME. this should have nothing to do with it, but i may try another "A" record to see.
thanks for the cifs.netbios_aliases option, i did a search of the 6.01 SAG and found no mention.
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