diff options
| author | John Terpstra <jht@samba.org> | 2005-07-08 15:07:53 +0000 |
|---|---|---|
| committer | Gerald W. Carter <jerry@samba.org> | 2008-04-23 08:47:04 -0500 |
| commit | 40ac96fb1bb098ee21bd34814ee1a6923b8c21ed (patch) | |
| tree | 1806198ee3abf7fe27a7812d211a1c1b4023ac84 /docs | |
| parent | 97e3e540f72021d81b34f7597506da6cdc552b8a (diff) | |
| download | samba-40ac96fb1bb098ee21bd34814ee1a6923b8c21ed.tar.gz samba-40ac96fb1bb098ee21bd34814ee1a6923b8c21ed.tar.bz2 samba-40ac96fb1bb098ee21bd34814ee1a6923b8c21ed.zip | |
Fix two small typos.
(This used to be commit 86d58c8f57c5f861319a86dc75e49a7988a6341b)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-DomainMember.xml | 2 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-HighAvailability.xml | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/Samba3-HOWTO/TOSHARG-DomainMember.xml b/docs/Samba3-HOWTO/TOSHARG-DomainMember.xml index 699cf9b5f0..f1691193e1 100644 --- a/docs/Samba3-HOWTO/TOSHARG-DomainMember.xml +++ b/docs/Samba3-HOWTO/TOSHARG-DomainMember.xml @@ -1320,7 +1320,7 @@ exists on the network &smbmdash; I know it does not. Why is this failing?</quote <indexterm><primary>nbtstat</primary></indexterm> The original name is still in the NetBIOS name cache and must expire after machine account deletion before adding that same name as a domain member again. The best advice is to delete -the old account and then add the machine with a new name. Alternately, the name cache can be flished and +the old account and then add the machine with a new name. Alternately, the name cache can be flushed and reloaded with current data using the <command>nbtstat</command> command on the Windows client: <screen> &dosprompt; nbtstat -R diff --git a/docs/Samba3-HOWTO/TOSHARG-HighAvailability.xml b/docs/Samba3-HOWTO/TOSHARG-HighAvailability.xml index ce86dc1bc5..1ce81d404e 100644 --- a/docs/Samba3-HOWTO/TOSHARG-HighAvailability.xml +++ b/docs/Samba3-HOWTO/TOSHARG-HighAvailability.xml @@ -178,9 +178,9 @@ from other sources, but it was Jeremy who inspired the structure that follows. </para> <para> -<indexterm><primary>IPC4 connections</primary></indexterm> +<indexterm><primary>IPC$ connections</primary></indexterm> <indexterm><primary>RPC calls</primary></indexterm> - One could split all IPC4 connections and RPC calls to one server to handle printing and user + One could split all IPC$ connections and RPC calls to one server to handle printing and user lookup requirements. RPC printing handles are shared between different IPC4 sessions &smbmdash; it is hard to split this across clustered servers! </para> |