I have two identical installations of samba v2.25 on linux boxes. On one system everything works fine but on the other, copies of smbd start but never terminate. The result is that the winduhs boxes that are trying to access the samba share get locked out and never find the samba server. The configurations of the two systems are identical and I am unable to determine why one works and the other does not. smbd and nmbd are started from inetd. Any ideas. Michael
Michael, I am unsure what you mean by "locked out" could you clarify? Do you mean that they connect and are able to browse, read and write to files in the share, but when the users come back to the share later they are unable to do those tasks, or are you saying that they are never able to see the server and that when they attempt to connect to the server/share, they are given the message that they are unable to connect. I would confirm that all the file permissions are properly set for the shares. Other then that, I am unsure what could be causing your issues. Regards, Robert Adkins II IT Manager/Buyer Impel Industries, Inc. Ph. 586-254-5800 Fx. 586-254-5804 -----Original Message----- From: Michael Robinton [mailto:michael@bizsystems.com] Sent: Friday, November 22, 2002 1:14 PM To: samba@lists.samba.org; Robert Adkins Subject: [Samba] smbd weirdness I have two identical installations of samba v2.25 on linux boxes. On one system everything works fine but on the other, copies of smbd start but never terminate. The result is that the winduhs boxes that are trying to access the samba share get locked out and never find the samba server. The configurations of the two systems are identical and I am unable to determine why one works and the other does not. smbd and nmbd are started from inetd. Any ideas. Michael -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
> Michael, > > I am unsure what you mean by "locked out" could you clarify? Do you > mean > that they connect and are able to browse, read and write to files in > the share, but when the users come back to the share later they > are unable to do those tasks, or are you saying that they are > never able to see the server and that when they attempt to connect > to the server/share, they are given the message that they are > unable to connect. > > I would confirm that all the file permissions are properly set for > the > shares. Other then that, I am unsure what could be causing your > issues. >the windows client is unable to connect, the message is that the server is not found. Upon examining the job table, there are several smbd instances running and no clients connected. This is a vanilla installation at a site that has been working for a couple of years. The other site belongs to them as well. I recently upgraded the OS to a newer version of linux distribution and kernel though the samba distributions were built by hand. Only one site exhibits this behavior. The problem is intermittant in that when it does happen I find the running copies of smbd whereas normally there would be none unless a client connected. I dont' understand why smbd terminates properly under some circumstances and not others.???> Regards, > Robert Adkins II > IT Manager/Buyer > Impel Industries, Inc. > Ph. 586-254-5800 > Fx. 586-254-5804 > > > -----Original Message----- > From: Michael Robinton [mailto:michael@bizsystems.com] > Sent: Friday, November 22, 2002 1:14 PM > To: samba@lists.samba.org; Robert Adkins > Subject: [Samba] smbd weirdness > > > > I have two identical installations of samba v2.25 on linux boxes. On > one system everything works fine but on the other, copies of smbd > start but never terminate. The result is that the winduhs boxes that > are trying to access the samba share get locked out and never find > the samba server. The configurations of the two systems are > identical and I am unable to determine why one works and the other > does not. > > smbd and nmbd are started from inetd. > > Any ideas. > > Michael > > --
Michael, Have you run the smbclient -L <servername> while logged in as a user that has access to the server? Do this from a terminal connection that is on the Samba server in question. This should give you some information as to why it isn't quite doing what it should be doing. Another thing that might have occurred is that during your upgrade one or more libraries and other packages, that the hand-built Samba install was dependent upon could have been changed or replaced with something that your Samba install is unable to utilize. If you are running Redhat and upgraded to 7.3 or even 8.0 do a quick check by uninstalling or simply moving your current Samba install and replace it with the latest RPM version of it. During the RPM install you should either receive several errors about missing libraries and such or have a clean install occur. If the latter happens put your settings into the smb.conf created by the RPM and see what happens. I have a feeling that one or more packages were inadvertently skipped or added to the install at this one site, that hadn't been done to the other servers that were upgraded. I hope that helps, let me know if my suggestion takes care of the issue. Regards, Robert Adkins II IT Manager/Buyer Impel Industries, Inc. Ph. 586-254-5800 Fx. 586-254-5804 -----Original Message----- From: Michael Robinton [mailto:michael@bizsystems.com] Sent: Friday, November 22, 2002 3:21 PM To: Robert Adkins Cc: samba@lists.samba.org Subject: RE: [Samba] smbd weirdness> Michael, > > I am unsure what you mean by "locked out" could you clarify? Do you > mean > that they connect and are able to browse, read and write to files in > the share, but when the users come back to the share later they > are unable to do those tasks, or are you saying that they are > never able to see the server and that when they attempt to connect > to the server/share, they are given the message that they are > unable to connect. > > I would confirm that all the file permissions are properly set for > the > shares. Other then that, I am unsure what could be causing your > issues. >the windows client is unable to connect, the message is that the server is not found. Upon examining the job table, there are several smbd instances running and no clients connected. This is a vanilla installation at a site that has been working for a couple of years. The other site belongs to them as well. I recently upgraded the OS to a newer version of linux distribution and kernel though the samba distributions were built by hand. Only one site exhibits this behavior. The problem is intermittant in that when it does happen I find the running copies of smbd whereas normally there would be none unless a client connected. I dont' understand why smbd terminates properly under some circumstances and not others.???> Regards, > Robert Adkins II > IT Manager/Buyer > Impel Industries, Inc. > Ph. 586-254-5800 > Fx. 586-254-5804 > > > -----Original Message----- > From: Michael Robinton [mailto:michael@bizsystems.com] > Sent: Friday, November 22, 2002 1:14 PM > To: samba@lists.samba.org; Robert Adkins > Subject: [Samba] smbd weirdness > > > > I have two identical installations of samba v2.25 on linux boxes. On > one system everything works fine but on the other, copies of smbd > start but never terminate. The result is that the winduhs boxes that > are trying to access the samba share get locked out and never find > the samba server. The configurations of the two systems are > identical and I am unable to determine why one works and the other > does not. > > smbd and nmbd are started from inetd. > > Any ideas. > > Michael > > --
On Fri, Nov 22, 2002 at 01:13:33PM -0800, Michael Robinton wrote:> I have two identical installations of samba v2.25 on linux boxes. On one > system everything works fine but on the other, copies of smbd start but > never terminate. The result is that the winduhs boxes that are trying to > access the samba share get locked out and never find the samba server. The > configurations of the two systems are identical and I am unable to > determine why one works and the other does not. > > smbd and nmbd are started from inetd. > > Any ideas.You have changed the host- and netbiosname of the second server? You have make sure the only one wins server is running? If you setup a windows domain, you have make sure that only one server has pdc setup? -- Frank Matthie? fm+samba@Microdata-pos.de