Re: [Samba] explorer.exe crashing at login
Sam Hart wrote: 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). begin quote: On 03-02-19, Orion Poplawski wrote: 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. After going through Microsoft support, they pointed me to the following support article: 326572 Explorer.exe Repeatedly Generates Access Violation Error Messages After _http://support.microsoft.com/?id=326572_ In addition to the hotfix mentioned in the article, upgrading to IE 6 it supposed to do the same thing, which I tried, and it worked. - Orion -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] explorer.exe crashing at login
> 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??? I'm not certain, I guess they could be. We did recently apply SP3 (very recently) and I actually hadn't made the connection. In our situation, we don't have a Default user directory, everyone has their own unique login. Also, we have roaming profiles disabled (which is retained for legacy purposes, i.e., certain members of our staff would have a cow if they lost their bookmarks/backgrounds ;-) so the profiles are stored on the client machines. If you do have a highly modified NTUSER.dat file, then you may need to have it be recreated... I dont know. Was this an NTUSER.dat file that was modified by hand? (Not like I can help you further one way or the other, it's just that I've always been far too squeemish to look much in, let alone mess with, these files, so I'm curious.) -- Sam Hart University/Work addr. <[EMAIL PROTECTED]> Personal addr. <[EMAIL PROTECTED]> end -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] explorer.exe crashing at login
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:[EMAIL PROTECTED]] Sent: 19 February 2003 16:54 To: Orion Poplawski Cc: [EMAIL PROTECTED] 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). -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
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). begin quote: On 03-02-19, Orion Poplawski wrote: > 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. > > 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. -- Sam Hart University/Work addr. <[EMAIL PROTECTED]> Personal addr. <[EMAIL PROTECTED]> end -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba