On Fri, 2004-12-10 at 18:44 -0500, A. Rick Anderson wrote: > Ever since I upgraded my machine from FC2 to FC3, I've been having > network issues. In the course of debugging problems with my samba > shares, I discovered that named.conf had been swapped out. Switching > the file names back seems to have resolved the samba shares problem. > I'm not sure that issues related to it operating as a PDC have been > resolved. > > After my FC3 machine is up for 15 to 30 minutes, all the connected Win2k > resources start failing. The various PC's no longer can access each > other's shares, including shared printers. If a user attempts to log > into one of the machines, if the user hasn't already logged in on that > particular machine, she will get a message saying that the domain is not > available. If you try to access one of the shares, it will present you > with an authentication dialog box, but you will fail every time. > > Now I could write a cron job to reboot my FC3 server every fifteen > minutes, but that doesn't seem like a real good solution. What would be > getting re-initialized on a reboot, that would change within the first > thirty minutes? > > -- > A. Rick Anderson > This sounds like a windows domain controller master conflict. You need to make sure that the Winblows machines are not being hosed on SMB by the Linux machine and iron out the conflicts in domain controllers. There should only be one master controller, or set the priorities to avoid conflicts and make sure that one becomes the default master and they do not fight over that. >
