From 5ab7c2e3c1773612ea7a53504c04ebac3ad07c16 Mon Sep 17 00:00:00 2001 From: Samba Release Account Date: Fri, 31 Jan 1997 15:39:31 +0000 Subject: JHT ===> Guys, please check this out before release of 1.9.16p10 I added it to answer the one-two-many time this matter has been raised to me. If you are not comfortable with the added info please zap it from the final release. (This used to be commit 8d6d31c002f67b6378fe060c9af9cecce51d4883) --- docs/textdocs/GOTCHAS.txt | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) (limited to 'docs') diff --git a/docs/textdocs/GOTCHAS.txt b/docs/textdocs/GOTCHAS.txt index c9f78a1053..279b3453dc 100644 --- a/docs/textdocs/GOTCHAS.txt +++ b/docs/textdocs/GOTCHAS.txt @@ -20,3 +20,41 @@ Details: Corrective Action: Delete the entry after the word loopback in the line starting 127.0.0.1 ========================================================================= +Item Number: 2.0 +Description: Problems with MS Windows NT Server network logon service +Symptom: Loss of Domain Logon Services and failed Windows NT / 95 + logon attempts. +OS: All Unix systems with Windows NT Domain Control environments. +Platform: All +Date: February 1, 1997 +Submitted By: John H Terpstra +Details: + Samba is configured for Domain logon control in a network + where a Windows NT Domain Primary Controller is running. + + Case 1: + The Windows NT Server is shut down, then restarted. Then + the Samba server is reconfigured so that it NO LONGER offers + Domain logon services. Windows NT and 95 workstations can no + longer log onto the domain. Ouch!!! + + Case 2: + The Windows NT Server which is running the Network logon + Service is shut down and restarted while Samba is a domain + controller offering the Domain LogOn service. Windows NT + Workstation and Server can no longer log onto the network. + + Cause: + Windows NT checks at start up to see if any domain logon + controllers are already running within the domain. It finds + Samba claiming to offer the service and therefore does NOT + start it's Network Logon Service. + + Windows NT needs the Windows NT network logon service to gain + from it's Domain controller's SAM database the security + identifier for the user loging on. + +Work-around: Stop the Samba nmbd and smbd processes, then on the Windows + NT Primary Domain Controller start the Network Logon Service. + Now restart the Samba nmbd and smbd services. +========================================================================= -- cgit