diff options
| author | John Terpstra <jht@samba.org> | 2003-05-27 07:08:04 +0000 |
|---|---|---|
| committer | John Terpstra <jht@samba.org> | 2003-05-27 07:08:04 +0000 |
| commit | 6647e15cc7c08982038de9fd599ab36e29c0371b (patch) | |
| tree | 009cea887d332e74b523d0af83a30fd9bb27918f /docs/docbook/projdoc/Integrating-with-Windows.xml | |
| parent | b68e0b3aaea800ac668f9ee22b42fae6a783c8b5 (diff) | |
| download | samba-6647e15cc7c08982038de9fd599ab36e29c0371b.tar.gz samba-6647e15cc7c08982038de9fd599ab36e29c0371b.tar.bz2 samba-6647e15cc7c08982038de9fd599ab36e29c0371b.zip | |
Another little edit. Still much more to be done.
(This used to be commit d6b8a8ab492d49971f8c9a4b1aed23146a32c779)
Diffstat (limited to 'docs/docbook/projdoc/Integrating-with-Windows.xml')
| -rw-r--r-- | docs/docbook/projdoc/Integrating-with-Windows.xml | 65 |
1 files changed, 63 insertions, 2 deletions
diff --git a/docs/docbook/projdoc/Integrating-with-Windows.xml b/docs/docbook/projdoc/Integrating-with-Windows.xml index eae51295df..0ee65a771c 100644 --- a/docs/docbook/projdoc/Integrating-with-Windows.xml +++ b/docs/docbook/projdoc/Integrating-with-Windows.xml @@ -573,7 +573,7 @@ carelessness. Of course, noone is every deliberately careless! </para> <sect2> - <title>My Boomerang Won't Come Back<title> + <title>My Boomerang Won't Come Back</title> <para> Well, the real complaint said, "I can ping my samba server from Windows, but I can @@ -584,7 +584,7 @@ carelessness. Of course, noone is every deliberately careless! The Windows machine was at IP Address 192.168.1.2 with netmask 255.255.255.0, the Samba server (Linux) was at IP Address 192.168.1.130 with netmast 255.255.255.128. The machines were on a local network with no external connections. - <para> + </para> <para> Due to inconsistent netmasks, the Windows machine was on network 192.168.1.0/24, while @@ -610,6 +610,67 @@ carelessness. Of course, noone is every deliberately careless! </sect2> + <sect2> + <title>Samba server name change problem</title> + + <para> + The name of the samba server was changed, samba was restarted, samba server can not be + pinged by new name from MS Windows NT4 Workstation, but it does still respond to ping using + the old name. Why? + </para> + + <para> + From this description three (3) things are rather obvious: + </para> + + <itemizedlist> + <listitem><para>WINS is NOT in use, only broadcast based name resolution is used</para></listitem> + <listitem><para>The samba server was renamed and restarted within the last 10-15 minutes</para></listitem> + <listitem><para>The old samba server name is still in the NetBIOS name cache on the MS Windows NT4 Workstation</para></listitem> + </itemizedlist> + + <para> + To find what names are present in the NetBIOS name cache on the MS Windows NT4 machine, + open a cmd shell, then: + </para> + + <para> + <screen> + C:\temp\>nbtstat -n + + NetBIOS Local Name Table + + Name Type Status + ------------------------------------------------ + SLACK <03> UNIQUE Registered + ADMININSTRATOR <03> UNIQUE Registered + SLACK <00> UNIQUE Registered + SARDON <00> GROUP Registered + SLACK <20> UNIQUE Registered + SLACK <1F> UNIQUE Registered + + + C:\Temp\>nbtstat -c + + NetBIOS Remote Cache Name Table + + Name Type Host Address Life [sec] + -------------------------------------------------------------- + FRODO <20> UNIQUE 192.168.1.1 240 + + C:\Temp\> + </screen> + </para> + + <para> + In the above example, FRODO is the Samba server and SLACK is the MS Windows NT4 Workstation. + The first listing shows the contents of the Local Name Table (ie: Identity information on + the MS Windows workstation), the second shows the NetBIOS name in the NetBIOS name cache. + The name cache contains the remote machines known to this workstation. + </para> + + </sect2> + </sect1> </chapter> |