2 !== GOTCHAS.txt for Samba release 2.0.0-beta1 14 Nov 1998
4 This file lists Gotchas to watch out for:
5 =========================================================================
7 Description: Problem Detecting Interfaces
8 Symptom: Workstations do NOT see Samba server in Browse List
9 OS: RedHat - Rembrandt Beta 2
12 Submitted By: John H Terpstra
14 By default RedHat Rembrandt-II during installation adds an
15 entry to /etc/hosts as follows:-
16 127.0.0.1 loopback "hostname"."domainname"
18 This causes Samba to loop back onto the loopback interface.
19 The result is that Samba fails to communicate correctly with
20 the world and therefor may fail to correctly negotiate who
21 is the master browse list holder and who is the master browser.
23 Corrective Action: Delete the entry after the word loopback
24 in the line starting 127.0.0.1
25 =========================================================================
27 Description: Problems with MS Windows NT Server network logon service
28 Symptom: Loss of Domain Logon Services and failed Windows NT / 95
30 OS: All Unix systems with Windows NT Domain Control environments.
32 Date: February 1, 1997
33 Submitted By: John H Terpstra
35 Samba is configured for Domain logon control in a network
36 where a Windows NT Domain Primary Controller is running.
39 The Windows NT Server is shut down, then restarted. Then
40 the Samba server is reconfigured so that it NO LONGER offers
41 Domain logon services. Windows NT and 95 workstations can no
42 longer log onto the domain. Ouch!!!
45 The Windows NT Server which is running the Network logon
46 Service is shut down and restarted while Samba is a domain
47 controller offering the Domain LogOn service. Windows NT
48 Workstation and Server can no longer log onto the network.
51 Windows NT checks at start up to see if any domain logon
52 controllers are already running within the domain. It finds
53 Samba claiming to offer the service and therefore does NOT
54 start its Network Logon Service.
56 Windows NT needs the Windows NT network logon service to gain
57 from its Domain controller's SAM database the security
58 identifier for the user loging on.
60 Work-around: Stop the Samba nmbd and smbd processes, then on the Windows
61 NT Primary Domain Controller start the Network Logon Service.
62 Now restart the Samba nmbd and smbd services.
64 Better still: DO NOT CONFIGURE SAMBA AS THE NETWORK LOGON
65 SERVER, DO NOT SET SAMBA TO BE THE DOMAIN MASTER, DO NOT
66 SET SAMBA TO OS LEVEL GREATER THAN 0.
68 ie: Let Windows NT Server be the Domain Logon server, the
69 domain master browser and do NOT interfere with any aspect
70 of Microsoft Windows NT Domain Control.
71 =========================================================================