Hi, I recently installed samba (3.0.28) on a linux box as a PDC. The networks has about 20 windows xp professional and a few Linux (all Fedora 8). Basically the server works OK but I have run into a few problems: Initially windows roaming profile was not configured. At that time, sometimes when a user tries to log on a windows machines, it would say "server not found" and the user wouldn't be able to logon. Later on, roaming profile was configured (and the user profiles are stored on another Linux server), then sometimes when a user tries to log on a windows, it would say the roaming profile was not found and a local profile would be used, or sometimes it would say "your local profile can not be found" and a temporary profile was used. Up to now, this problem can be resolved by restarting the windows. Both problems do not always happen, so users can use the computers with no problem most of the time. But it is irritating when it happens. I thought I might have installed too much stuff on the PDC, since I checked almost all of the optional package to be installed when Fedora 8 was installed. But the PDC was only used for user athentication and it is not busy at all. I have tried to increase the priority of the smb and nmb processes, but it seems to have no effect. Anybody know what might have caused the problems? Any suggestion is appreciated. George
On Fri, Jun 6, 2008 at 3:26 PM, George He <georgehe2007@gmail.com> wrote:> Hi, > > I recently installed samba (3.0.28) on a linux box as a PDC. The networks > has about 20 windows xp professional and a few Linux (all Fedora 8). > Basically the server works OK but I have run into a few problems: > > Initially windows roaming profile was not configured. At that time, > sometimes when a user tries to log on a windows machines, it would say > "server not found" and the user wouldn't be able to logon. > > Later on, roaming profile was configured (and the user profiles are stored > on another Linux server), then sometimes when a user tries to log on a > windows, it would say the roaming profile was not found and a local profile > would be used, or sometimes it would say "your local profile can not be > found" and a temporary profile was used. Up to now, this problem can be > resolved by restarting the windows. > > Both problems do not always happen, so users can use the computers with no > problem most of the time. But it is irritating when it happens. I thought I > might have installed too much stuff on the PDC, since I checked almost all > of the optional package to be installed when Fedora 8 was installed. But the > PDC was only used for user athentication and it is not busy at all. I have > tried to increase the priority of the smb and nmb processes, but it seems to > have no effect. > > Anybody know what might have caused the problems? Any suggestion is > appreciated. >Probably a browsing issue. Do the windows machines find the PDC using dns or wins? If wins have you added the wins server to all of the windows machines? John -- John M. Drescher
> Hi John, > when you say wins, do you mean the lmhosts file?No. If you set the PDC to be a wins server then add this ip as the wins server in every windows client the windows machines will find the domain controller. But that should work. Have you added the proper format of a domain controller? Here is a very old example I dug up on how we did this years ago: 10.116.15.13 RADIMGDC0 #PRE #DOM:RADIMG 10.116.15.13 "RADIMG \0x1B" #PRE So RADIMGDC0 was the PDC on the RADIMG DOMAIN. The "" part has to be exactly 20 characters.> I edited that file on some of the windows machines to list both servers (PDC > and file server) but it didn't solve my problems. > The other windows machines, which don't have this lmhosts file, I guess they > use dns to find the servers?Not unless you added the needed _ldap._tcp.dc._msdcs entries in your dns server.>If it can be something else, how do I find out for sure?Go to the windows client and look at the event viewer. You will see errors. John
On Mon, Jun 9, 2008 at 10:43 AM, John Drescher <drescherjm@gmail.com> wrote:>> Anybody has any ideas about those "Autoenrollment" event errors (ID=15) >> listed in event viewer? >> > That is normal. I have seen these for many years. >Automatic certificate enrollment for RADIMG\jdrescher failed to contact the active directory (0x8007054b). The specified domain either does not exist or could not be contacted. Enrollment will not be performed. I believe this is because my XP client is trying to find an active directory domain. Which you do not have with samba 3.X. John