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.
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
But why would the Windows box "give up" on a CIFS connection? I make CIFS connections to a DNS name all the time.
I suspect that it is something that must be configured on the nfs client software.
Jordan
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]On Behalf Of Mark Johnson-Barbier Sent: Monday, October 15, 2001 1:01 PM To: neil lehrer Cc: toasters; Curt Huyser; Ken Smith Subject: Re: drive mapping issues
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
I should have been more specific rather than saying "gives up".
DNS name resolution in Windows can be turned off for NetBIOS name resolution and if it's turned off it will "give up" before going to dns (Q142309). That's what I meant by "gives up". More accurately I should have said "gives up -- cdepending on how the client is configured."
The setting is located on the WINS configuration tab in TCP/IP properties. If you check "use DNS for Windows name resolution" NetBIOS queries will use dns otherwise, it will not.
To prevent inconsistencies in NT4 domains, I've always made sure that all windows clients needing a NetBIOS connection to a server can find the server in WINS -- that way you don't get unpredictable results with different applications. The static wins entry allows for a centralized fix rather than changing a TCP/IP setting on every client.
One other thing to keep in mind is the dns suffix list which can alter NetBIOS resolution by appending multiple dns names to NetBIOS requests.
mjb
----- Original Message ----- From: "Jordan Share" iso9@phantasticant.com To: "Mark Johnson-Barbier" mjb-toasters@mj3.org; "neil lehrer" nlehrer@ibb.gov Cc: "toasters" toasters@mathworks.com; "Curt Huyser" ch@ibb.gov; "Ken Smith" ksmith@ibb.gov Sent: Monday, October 15, 2001 1:39 PM Subject: RE: drive mapping issues
But why would the Windows box "give up" on a CIFS connection? I make CIFS connections to a DNS name all the time.
I suspect that it is something that must be configured on the nfs client software.
Jordan
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]On Behalf Of Mark Johnson-Barbier Sent: Monday, October 15, 2001 1:01 PM To: neil lehrer Cc: toasters; Curt Huyser; Ken Smith Subject: Re: drive mapping issues
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
Mark Johnson-Barbier wrote:
I should have been more specific rather than saying "gives up".
DNS name resolution in Windows can be turned off for NetBIOS name resolution and if it's turned off it will "give up" before going to dns (Q142309). That's what I meant by "gives up". More accurately I should have said "gives up -- cdepending on how the client is configured."
The setting is located on the WINS configuration tab in TCP/IP properties. If you check "use DNS for Windows name resolution" NetBIOS queries will use dns otherwise, it will not.
DNS name resolution for NetBIOS name resolution is not being used.
the only way i get a cifs connection is by using the filer's host name, or its ip number in the net use command.
To prevent inconsistencies in NT4 domains, I've always made sure that all windows clients needing a NetBIOS connection to a server can find the server in WINS -- that way you don't get unpredictable results with different applications. The static wins entry allows for a centralized fix rather than changing a TCP/IP setting on every client.
One other thing to keep in mind is the dns suffix list which can alter NetBIOS resolution by appending multiple dns names to NetBIOS requests.
mjb
----- Original Message ----- From: "Jordan Share" iso9@phantasticant.com To: "Mark Johnson-Barbier" mjb-toasters@mj3.org; "neil lehrer" nlehrer@ibb.gov Cc: "toasters" toasters@mathworks.com; "Curt Huyser" ch@ibb.gov; "Ken Smith" ksmith@ibb.gov Sent: Monday, October 15, 2001 1:39 PM Subject: RE: drive mapping issues
But why would the Windows box "give up" on a CIFS connection? I make CIFS connections to a DNS name all the time.
I suspect that it is something that must be configured on the nfs client software.
Jordan
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]On Behalf Of Mark Johnson-Barbier Sent: Monday, October 15, 2001 1:01 PM To: neil lehrer Cc: toasters; Curt Huyser; Ken Smith Subject: Re: drive mapping issues
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
Well, if you aren't using DNS for NetBIOS resolution, then how do you expect to use DNS names to map drives via CIFS?
Jordan
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]On Behalf Of neil lehrer Sent: Tuesday, October 16, 2001 8:13 AM To: Mark Johnson-Barbier Cc: Jordan Share; toasters@mathworks.com Subject: Re: drive mapping issues
Mark Johnson-Barbier wrote:
I should have been more specific rather than saying "gives up".
DNS name resolution in Windows can be turned off for NetBIOS name resolution and if it's turned off it will "give up" before going to dns (Q142309). That's what I meant by "gives up". More accurately I should have said "gives up -- cdepending on how the client is configured."
The setting is located on the WINS configuration tab in TCP/IP properties. If you check "use DNS for Windows name resolution" NetBIOS queries will use dns otherwise, it will not.
DNS name resolution for NetBIOS name resolution is not being used.
the only way i get a cifs connection is by using the filer's host name, or its ip number in the net use command.
To prevent inconsistencies in NT4 domains, I've always made sure that all windows clients needing a NetBIOS connection to a server can find the server in WINS -- that way you don't get unpredictable results with different applications. The static wins entry allows for a centralized fix rather than changing a TCP/IP setting on every client.
One other thing to keep in mind is the dns suffix list which can alter NetBIOS resolution by appending multiple dns names to NetBIOS requests.
mjb
----- Original Message ----- From: "Jordan Share" iso9@phantasticant.com To: "Mark Johnson-Barbier" mjb-toasters@mj3.org; "neil lehrer" nlehrer@ibb.gov Cc: "toasters" toasters@mathworks.com; "Curt Huyser" ch@ibb.gov; "Ken Smith" ksmith@ibb.gov Sent: Monday, October 15, 2001 1:39 PM Subject: RE: drive mapping issues
But why would the Windows box "give up" on a CIFS connection? I make CIFS connections to a DNS name all the time.
I suspect that it is something that must be configured on the nfs client software.
Jordan
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]On Behalf Of Mark Johnson-Barbier Sent: Monday, October 15, 2001 1:01 PM To: neil lehrer Cc: toasters; Curt Huyser; Ken Smith Subject: Re: drive mapping issues
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
jordan,
that's a really good question. i have it working now and i have no idea what fixed it. file1 is in dns and in wins thru cifs.netbios_aliases.
it started working[getting a cifs connection, not nfs] after i -HUP'd a secondary dns that my workstation uses. but, the entry for file1 has been in dns for ages so that shouldn't have mattered and having it in wins should have been enough. we always blame the nfs client when we have strange things like this happening; it may have been interfering with 'normal' nt mapping.
i'm just happy it's working.
thanks to everyone on the list for their advice.
Jordan Share wrote:
Well, if you aren't using DNS for NetBIOS resolution, then how do you expect to use DNS names to map drives via CIFS?
Jordan
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]On Behalf Of neil lehrer Sent: Tuesday, October 16, 2001 8:13 AM To: Mark Johnson-Barbier Cc: Jordan Share; toasters@mathworks.com Subject: Re: drive mapping issues
Mark Johnson-Barbier wrote:
I should have been more specific rather than saying "gives up".
DNS name resolution in Windows can be turned off for NetBIOS name resolution and if it's turned off it will "give up" before going to dns (Q142309). That's what I meant by "gives up". More accurately I should have said "gives up -- cdepending on how the client is configured."
The setting is located on the WINS configuration tab in TCP/IP properties. If you check "use DNS for Windows name resolution" NetBIOS queries will use dns otherwise, it will not.
DNS name resolution for NetBIOS name resolution is not being used.
the only way i get a cifs connection is by using the filer's host name, or its ip number in the net use command.
To prevent inconsistencies in NT4 domains, I've always made sure that all windows clients needing a NetBIOS connection to a server can find the server in WINS -- that way you don't get unpredictable results with different applications. The static wins entry allows for a centralized fix rather than changing a TCP/IP setting on every client.
One other thing to keep in mind is the dns suffix list which can alter NetBIOS resolution by appending multiple dns names to NetBIOS requests.
mjb
----- Original Message ----- From: "Jordan Share" iso9@phantasticant.com To: "Mark Johnson-Barbier" mjb-toasters@mj3.org; "neil lehrer" nlehrer@ibb.gov Cc: "toasters" toasters@mathworks.com; "Curt Huyser" ch@ibb.gov; "Ken Smith" ksmith@ibb.gov Sent: Monday, October 15, 2001 1:39 PM Subject: RE: drive mapping issues
But why would the Windows box "give up" on a CIFS connection? I make CIFS connections to a DNS name all the time.
I suspect that it is something that must be configured on the nfs client software.
Jordan
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]On Behalf Of Mark Johnson-Barbier Sent: Monday, October 15, 2001 1:01 PM To: neil lehrer Cc: toasters; Curt Huyser; Ken Smith Subject: Re: drive mapping issues
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
--
regards
+++++++++++++++++++++++++++++++++++++++++++++++++
- Neil Lehrer
- United States International Broadcasting Bureau
- System Development Division
- voice 202 619-2524
- fax 202 619-3576
- nlehrer@ibb.gov
- " is this crisis an opportunity or just
- another grab the fire extinguisher moment?"
+++++++++++++++++++++++++++++++++++++++++++++++++
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
-
Jordan Share -
Mark Johnson-Barbier -
Mark Johnson-Barbier -
neil lehrer