Windows Unable To Resolve The Netbios Name Of The Cifs Server - Novell OPEN ENTERPRISE SERVER 2 SP2 - ADMINISTRATION Manual

5.6.1 Windows Unable to Resolve the NetBIOS Name of the
CIFS Server
Clients using Windows 2000 Service Pack 4 and Windows XP Service Pack 2 might have problems
following DFS junctions over CIFS because of a defect in Windows. (This problem exhibits itself in
a pure Windows environment.) When using DFS with CIFS, the CIFS server and Windows clients
are on different IP subnets. In this case, the client must have a way to resolve the CIFS server name
in order for DFS to work. This is a Microsoft/CIFS requirement, not a CIFS Linux requirement.
NOTE: This problem does not affect Windows clients that use the Novell Client
There are multiple ways the client can resolve the CIFS server name:
Install the Novell Client on the client machine.
Configure both the client and server for the same WINS server
Configure both the client and server to use the same DNS server
Modify the
servers that use DFS junctions
To modify the
1 In a text editor, open the
Windows 2000:
Windows XP:
If you do not have
2 For all the host and target servers, add a line at the end of the file that identifies the IP address
and NetBIOS name of the data server.
192.168.1.1
Replace
IMPORTANT: Modifying the CIFS server name of the virtual server using iManager is not
allowed. However, it is possible to modify the CIFS server name for a physical server.
We recommend that you do not modify the CIFS server name of the physical server that is the
DFS target.
For example, suppose you have the following server:
Server IP address:
<Cluster IP address> or <Cluster Resource IP address>
Server name:
NetBIOS server name:
If the target of the junction is a cluster resource, mention the <Cluster IP address> or
<Cluster Resource IP address> and instead of server name, mention the cluster name.
The line you add to the hosts file is:
10.10.1.1 USERSVR_W
48 OES 2 SP2: Novell CIFS for Linux Administration Guide
file for all client computers with appropriate entries for any volumes on OES
hosts
file on a client:
hosts
file and modify the hosts file.
hosts
c:\WINNT\system32\drivers\etc\hosts
c:\windows\system32\drivers\etc\hosts
file, create the file.
hosts
servername_W
with the actual IP address and servername with the name of your server.
192.168.1.1
10.10.1.1
USERSVR
USERSVR_W
. If the DFS target is a cluster resource, then mention
.
TM