|
Samba Server Name-Change Problem
“The name of the Samba server was changed, Samba was restarted, and now the Samba server cannot be
pinged by its new name from an MS Windows NT4 workstation, but it does still respond to pinging using
the old name. Why?”
From this description, three things are obvious:
-
WINS is not in use; only broadcast-based name resolution is used.
-
The Samba server was renamed and restarted within the last 10 or 15 minutes.
-
The old Samba server name is still in the NetBIOS name cache on the MS Windows NT4 workstation.
To find what names are present in the NetBIOS name cache on the MS Windows NT4 machine,
open a
cmd
shell and then:
C:\>
nbtstat -n
NetBIOS Local Name Table
Name Type Status
------------------------------------------------
FRODO <03> UNIQUE Registered
ADMINISTRATOR <03> UNIQUE Registered
FRODO <00> UNIQUE Registered
SARDON <00> GROUP Registered
FRODO <20> UNIQUE Registered
FRODO <1F> UNIQUE Registered
C:\> nbtstat -c
NetBIOS Remote Cache Name Table
Name Type Host Address Life [sec]
--------------------------------------------------------------
GANDALF <20> UNIQUE 192.168.1.1 240
C:\>
In this example, GANDALF is the Samba server and FRODO is the MS Windows NT4 workstation.
The first listing shows the contents of the Local Name Table (i.e., identity information on
the MS Windows workstation), and the second shows the NetBIOS name in the NetBIOS name cache.
The name cache contains the remote machines known to this workstation.
|
