I have a VERY worrying situation. This is all SAMBA_2_2_5 with ldap. I have a SAMBA PDC with several SAMBA servers and loads of WindowsXP workstations. The SAMBA servers and XP Pcs are all joined into the PDC domain. Logging on the PDC is ..../%m.log so that I get a log for each PC. When I look at the cpu usage on the PDC system one process is continuouly using 25%. If I set debug level 10 there is continuous output to one PC's log file. I am not good at working out what exectly is happening but it appears that there are repeated login attempts for one user from that PC (in any event, SAMBA keeps looking up the user's ldap entry, successfully). I look at the PC and it is sitting on the XP login window waiting to be given a username and password. If I re-boot the PC the problem moves to another PC which is just sitting on the XP login window. The same username all the time, though it is now a different unix process ID. I can't start to imagine what is going on. Help please. Phil. --------------------------------------- Phil Chambers (postmaster@exeter.ac.uk) University of Exeter
On Tue, Sep 17, 2002 at 10:30:58AM +0100, Phil Chambers wrote:> I have a VERY worrying situation. This is all SAMBA_2_2_5 with ldap. I have a > SAMBA PDC with several SAMBA servers and loads of WindowsXP workstations. The SAMBA > servers and XP Pcs are all joined into the PDC domain. Logging on the PDC is > ..../%m.log so that I get a log for each PC. > > When I look at the cpu usage on the PDC system one process is continuouly using 25%. > If I set debug level 10 there is continuous output to one PC's log file. I am not > good at working out what exectly is happening but it appears that there are repeated > login attempts for one user from that PC (in any event, SAMBA keeps looking up the > user's ldap entry, successfully). I look at the PC and it is sitting on the XP login > window waiting to be given a username and password. If I re-boot the PC the problem > moves to another PC which is just sitting on the XP login window. The same username > all the time, though it is now a different unix process ID.Can you get a debug level 10 (use smbcontrol) from that process so we can see where it's looping please ? Thanks, Jeremy.
I first sent a message about this problem 8 days ago, but have still not resolved it. However, I now have a much clearer idea of what is happening, so can provide a better description. We have a SAMBA_2_2_5 PDC (using LDAP) with dozens of XP PCs as members of the domain. This all seems to work OK as such. We also have on the same network loads of XP PCs which are not members of the domain, but are just members of various workgroups. Our problem is that there are times when (so it seems to me) some of these non-domain PCs are thrashing away trying to get at the IPC$ share on one or more of the PCs which are members of SAMBA's domain. I have used a sniffer on the network connection of a domain member while this is happening (this PC was sitting on the XP login window at the time). This is the sequence of packets to/from the PC: