Hi, Our environment: HP-UX 11.00 server / Samba 3.0.21a as PDC / OpenLDAP backend We're developping a migration from AS/U to a Samba PDC. Currently we have following problem: logging onto an NT4 workstation is almost instantaneous, but when logging onto an XP workstation, this happens: (1) We type the user and password in Windows logon. (2) Windows logon immediately accepts user and password, so far so good. (3) Windows says "Please wait... Loading your personal settings..." and we have to wait about one to two minutes. This is our problem. (4) After these on to two minutes, logon continuous normally, and everything seems fine. Furthermore, during the time that XP locks up, the corresponding smbd process eats up the server's CPU at almost 100%! These are the log.smbd messages during the locking up of XP and smbd: .... [Fri Apr 21 15:25:29 2006 , 0] rpc_server/srv_netlog_nt.c:_net_sam_logon(665) _net_sam_logon: creds_server_step failed. Rejecting auth request from client RSL4 machine account RSL4$ [Fri Apr 21 15:26:47 2006 , 0] smbd/server.c:open_sockets_smbd(394) open_sockets_smbd: accept: No buffer space available [Fri Apr 21 15:26:50 2006 , 1] smbd/service.c:make_connection_snum(666) rsl4 (10.5.71.168) connect to service netlogon initially as user veron004 (uid =517, gid=20) (pid 11053) .... And as I already said: logging onto NT works fine. Any ideas?
We don't use roaming profiles, they're disabled ('logon path'
and
'logon home' are null for all users and in smb.conf).
Moreover, I'm really under the impression that the smbd process just
freezes. During a couple of minutes there's no activity in log.smbd. I
also monitored the smbd with HP's 'tusc' tool, which allows
monitoring
the system calls a process makes, and the smbd process just seems to
do nothing at all (no system calls) but take up all CPU.
We do have logon scripts, and an NT system policy file, but disabling
those didn't help either.
BTW, this is our current smb.conf:
--- smb.conf ---
[global]
workgroup = VERONIKX_DOM
domain master = yes
domain logons = yes
passdb backend = ldapsam:ldap://localhost:390
ldap port = 390
guest account = www
admin users = admin
create mask = 0664
directory mask = 0775
Unix charset = ISO8859-1
printcap name = lpstat
ldap admin dn = cn=smbadmin,dc=fedpol,dc=be
ldap group suffix = ou=Groups
ldap machine suffix = ou=Computers
ldap suffix = dc=fedpol,dc=be
ldap ssl = no
ldap user suffix = ou=People
ldap idmap suffix = ou=Idmap
logon path logon drive = X:
logon home
log level = 1
# smbldap-tools requirements
ldap delete dn = Yes
add user script = /opt/smbldap-tools/sbin/smbldap-useradd -m
"%u"
delete user script = /opt/smbldap-tools/sbin/smbldap-userdel -r
"%u"
add machine script = /opt/pip/system/smb-add-machine "%u"
add group script = /opt/smbldap-tools/sbin/smbldap-groupadd -p
"%g"
delete group script = /opt/smbldap-tools/sbin/smbldap-groupdel
"%g"
add user to group script = /opt/smbldap-tools/sbin/smbldap-groupmod -m
"
%u" "%g"
delete user from group script = /opt/smbldap-tools/sbin/smbldap-groupmod
-x "%u" "%g"
set primary group script = /opt/smbldap-tools/sbin/smbldap-usermod -g
"%
g" "%u"
# All services (shares) are defined in this seperate file, which
# is automatically generated by lmshare (lmshare.pkg):
include = /usr/local/samba/lib/smb-shares.conf
--- End of smb.conf ---
2006/4/21, Gary Dale
> While the developers in this forum can probably give you some ideas on
> how to improve the situation, I suspect that it is a by-product of
> roaming profiles. The way I understand it, a copy of your
"C:\Documents
> & Settings\username" folder is stored on the server and this is
> synchronised with your local version on startup and shutdown. Depending
> on what you've been doing, this synching can take a considerable amount
> of time.
>
> One way to minimize the impact is to store your documents in a personal
> folder on the network, rather than in "My Documents". This way,
the
> synching has less to do.
>
Hi Roel, Try Googling "Loading your personal settings". Looks like there is a lot of stuff to try on the client side, and the problem appears to be common regardless of server platform. I am concerned about your "No buffer space available" log, though. Can you email me the entire logfile? Eric Roseme Hewlett-Packard Roel Slegers wrote:> Hi, > > Our environment: HP-UX 11.00 server / Samba 3.0.21a as PDC / OpenLDAP backend > > We're developping a migration from AS/U to a Samba PDC. > Currently we have following problem: logging onto an NT4 workstation > is almost instantaneous, but when logging onto an XP workstation, this > happens: > (1) We type the user and password in Windows logon. > (2) Windows logon immediately accepts user and password, so far so good. > (3) Windows says "Please wait... Loading your personal settings..." > and we have to wait about one to two minutes. This is our problem. > (4) After these on to two minutes, logon continuous normally, and > everything seems fine. > > Furthermore, during the time that XP locks up, the corresponding smbd > process eats up the server's CPU at almost 100%! > > These are the log.smbd messages during the locking up of XP and smbd: > .... > [Fri Apr 21 15:25:29 2006 > , 0] rpc_server/srv_netlog_nt.c:_net_sam_logon(665) > _net_sam_logon: creds_server_step failed. Rejecting auth request > from client RSL4 machine account RSL4$ > [Fri Apr 21 15:26:47 2006 > , 0] smbd/server.c:open_sockets_smbd(394) > open_sockets_smbd: accept: No buffer space available > [Fri Apr 21 15:26:50 2006 > , 1] smbd/service.c:make_connection_snum(666) > rsl4 (10.5.71.168) connect to service netlogon initially as user veron004 (uid > =517, gid=20) (pid 11053) > .... > > And as I already said: logging onto NT works fine. > Any ideas?
Roel Slegers wrote:> Hi, > > Our environment: HP-UX 11.00 server / Samba 3.0.21a as PDC / OpenLDAP backend > > We're developping a migration from AS/U to a Samba PDC. > Currently we have following problem: logging onto an NT4 workstation > is almost instantaneous, but when logging onto an XP workstation, this > happens: > (1) We type the user and password in Windows logon. > (2) Windows logon immediately accepts user and password, so far so good. > (3) Windows says "Please wait... Loading your personal settings..." > and we have to wait about one to two minutes. This is our problem. > (4) After these on to two minutes, logon continuous normally, and > everything seems fine. > > Furthermore, during the time that XP locks up, the corresponding smbd > process eats up the server's CPU at almost 100%! > > These are the log.smbd messages during the locking up of XP and smbd: > .... > [Fri Apr 21 15:25:29 2006 > , 0] rpc_server/srv_netlog_nt.c:_net_sam_logon(665) > _net_sam_logon: creds_server_step failed. Rejecting auth request > from client RSL4 machine account RSL4$ > [Fri Apr 21 15:26:47 2006 > , 0] smbd/server.c:open_sockets_smbd(394) > open_sockets_smbd: accept: No buffer space available > [Fri Apr 21 15:26:50 2006 > , 1] smbd/service.c:make_connection_snum(666) > rsl4 (10.5.71.168) connect to service netlogon initially as user veron004 (uid > =517, gid=20) (pid 11053) > .... > > And as I already said: logging onto NT works fine. > Any ideas?You may want to look at the DNS/DHCP server. If there is a 2003 DC and it is not the DNS/DHCP server then things can slow down. I believe it is a reverse DNS issue. -- Regards -------------------------------------- Gerald Drouillard Technology Architect Drouillard & Associates, Inc. http://www.Drouillard.ca