We're running a network of Windows 2000 SP3 machines with Samba 2.2.7 as
the PDC and roaming profile store. Certain users logging onto certain
machines will see an error dialogue pop-up saying explorer.exe has
generated errors and will exit. This keeps popping up and to only
course of action is to ctrl-alt-del and logout. For most people,
everything works fine.
I've been able to clear it up temporarily my moving the profile
directory out of the way on the server, but the problem can re-occur.
smb.conf:
[global]
username map = /etc/samba/smbusers
; nt acl support = no
;Run as a PDC
domain logons = yes
security = user
os level = 99
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
socket options = TCP_NODELAY
local master = yes
domain master = yes
preferred master = yes
logon script = %U.bat
logon path = \\%N\%U\profile
logon drive = H:
logon home = \\%N\%U
wins support = yes
domain admin group = @wheel
share modes = no
[netlogon]
comment = Net logon scripts
path = /var/netlogon
create mode = 0600
directory mode = 0700
writable = no
guest ok = no
browsable = no
This seems to have started after I made some changes to our samba
server, and may have lost certain machine trust information, but I'm not
sure.
Any help would be greatly appreciated.
TIA,
Orion Poplawski
We're running a network of Windows 2000 SP3 machines with Samba 2.2.7 as
the PDC and roaming profile store. Certain users logging onto certain
machines will see an error dialogue pop-up saying explorer.exe has
generated errors and will exit. This keeps popping up and to only
course of action is to ctrl-alt-del and logout. For most people,
everything works fine.
I've been able to clear it up temporarily my moving the profile
directory out of the way on the server, but the problem can re-occur.
smb.conf:
[global]
username map = /etc/samba/smbusers
; nt acl support = no
;Run as a PDC
domain logons = yes
security = user
os level = 99
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
socket options = TCP_NODELAY
local master = yes
domain master = yes
preferred master = yes
logon script = %U.bat
logon path = \\%N\%U\profile
logon drive = H:
logon home = \\%N\%U
wins support = yes
domain admin group = @wheel
share modes = no
[netlogon]
comment = Net logon scripts
path = /var/netlogon
create mode = 0600
directory mode = 0700
writable = no
guest ok = no
browsable = no
This seems to have started after I made some changes to our samba
server, and may have lost certain machine trust information, but I'm not
sure.
Any help would be greatly appreciated.
TIA,
Orion Poplawski
Hi,
Reading your email, are u implying that the default user settings are updated in
the SP3. If this is the case if you have a Default User directory under the
netlogin share does this mean it will have to updated. If this is the case then
our highly modified NTUSER.dat will need to be updated from SP3 then all the
mods will need to be reapplied. Is this the case???
Cheers
-------------
Kristyan Osborne IT Technician
Longhill High School
01273 391672
------
Computers are like airconditioners: They stop working properly if you open
windows.
Win95: A 32-bit patch for a 16-bit GUI shell running on top of an
8-bit operating system written for a 4-bit processor by a
2-bit company who cannot stand 1 bit of competition.
-----Original Message-----
From: Sam Hart [mailto:hart@physics.arizona.edu]
Sent: 19 February 2003 16:54
To: Orion Poplawski
Cc: samba@lists.samba.org
Subject: Re: [Samba] explorer.exe crashing at login
I don't think I'll be able to help solve your problem completely, but I
may be able to send you in the right direction. We recently had this
problem as well, and found that giving the users higher priviledges on
their local client machines solved the problem (which, for our users, was
not a desirable solution).
It turns out in our situation it had nothing to do with samba being
configured incorrectly, but in the fact that the ntuser.* files in their
profile directories had older (now incorrect) information in them (after
the upgrade).
The way I had to solve it was to log in the users (non-priviledged) with
out having their profiles roaming (so that Windows created a new profile
for them) and then manually copy their new ntuser.* (uh... ntuser.dat,
ntuser.dat.log and ntuser.ini, I think) files from the new profile back
into their old profile (and then setting them back up to access their old
profile) Doing this kludge solved the problem you are talking about in our
system.
I am guessing (and this is just a shot in the dark) that in our case, the
upgrade caused Winwoes (W2K) to think the domain had changed, and that
this caused the previous profile information on the client machine to be
lost (at least, when viewing ownership on the client machine, the user
name was replaced with a long string of garbage).