David, Suggest you update to samba-2.2.6 or later (there will be an update later this week). The /root/tmp issue was a known problem with 2.2.2 and has been fixed. Best advice is to update to 2.2.6. If you then still have a problem, email me <[EMAIL PROTECTED]> and I will try to assist.
- John T. On Mon, 11 Nov 2002, David Donahue wrote: > I've been running Samba 2.2.2 for a while as a domain controller on my > mostly Windows network. It's been working great up to this point. > Anyway, I just put together a new Linux server and installed 2.2.2 on it > as well. > > I copied the conf file and pretty much mirrored everything on the > existing server, changed the paths and the "workgroup" field in the conf > file to match the new server, and ran the software. I'm able to join > the domain, but when I attempt to login to it after rebooting, it says > the domain is not available. And when I login to the Windows machine as > the local Administrator and try to connect to the domain it says "the > server is not configured for transactions." > > The log file samba generated for that client's connection repeats > attempts to access /root/tmp (I don't know why) and keeps saying that a > password server is unavailable. Any ideas? > > Could the problem be some kind of conflict with the current server on > the other machine? Until the new one is fully working I still have the > old one running on the other computer. Admittedly, I don't know what > every setting in the conf file does. So is it likely that, for certain > fields, identical settings on both machines would cause some kind of > conflict during a logon? > > > > David P. Donahue > [EMAIL PROTECTED] > First Call Computer Solutions > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba > -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
