Hello List, I am running a 3.0.24 server on redhat EL4. I have a user that has mapped a drive to his home directory on the server. When he copies a file from the share to a local disk location, desktop for example, it goes just fine. When he attempts to copy / move / cut and paste a file from one location on the share to another location in the same share, it will literally crash his local machine and it reboots. Other users can do the same no problems. He can map to a different samba server and is able to copy a file within that share. I am suspecting some corrupt file entry or possibly something strange in the registry not sure. I have looked in his home directory and do not see any thing out of the ordinary. Ideas / Suggestions? Many Thanks -- Jim Summers School of Computer Science-University of Oklahoma -------------------------------------------------
More info. I went the user's workstation and created a new user. Then mapped a drive to a different share. Attempted to copy a file within that share and boom, reboot. Hmmmm. TIA Jim Summers wrote:> Hello List, > > I am running a 3.0.24 server on redhat EL4. I have a user that has > mapped a drive to his home directory on the server. When he copies a > file from the share to a local disk location, desktop for example, it > goes just fine. When he attempts to copy / move / cut and paste a file > from one location on the share to another location in the same share, it > will literally crash his local machine and it reboots. Other users can > do the same no problems. He can map to a different samba server and is > able to copy a file within that share. > > I am suspecting some corrupt file entry or possibly something strange in > the registry not sure. I have looked in his home directory and do not > see any thing out of the ordinary. > > Ideas / Suggestions? > > Many Thanks-- Jim Summers School of Computer Science-University of Oklahoma -------------------------------------------------
Thought I would post this for Rhiannon. As mentioned that patch can not be removed safely. When I tried to remove it, it listed four or five other patches that may not work correctly. So I cancelled out. I may try and do a windows repair and see if that will put a fresh copy of the affected file(s) back on the machine. The repair I mention is the repair option you get when the installer finds a copy of windows on the hd and then asks to repair or whatever. Not the one where you use recovery console. Ideas / Suggestions. Many Thanks Rhiannon.Henning@sungard.com wrote:> Hi, > I have tried to post this to the samba list a couple times but keeps > getting bounced back for some reason...anyway here's my response -- > I am running samba version 3.0.23 on RHEL 4. Last week I had experienced > a similar problem with a couple samba users. The reboot would occur when > trying to perform a save or save as...from a Word or Excel file on the > samba share. What I discovered to be the problem is the recent MS patch, > KB925902. I tried uninstalling the patch but for whatever reason it does > not fully uninstall, so I had to reinstall WinXP SP2 to fix the issue. > If your users are trying to copy MS office files, I would check to see > if your users have this patch installed. > Rhiannon > > If this fixes the problem for you feel free to post to the list for me. > Thanks! > > -----Original Message----- > From: samba-bounces+rhiannon.henning=sungard.com@lists.samba.org > [mailto:samba-bounces+rhiannon.henning=sungard.com@lists.samba.org] On > Behalf Of Jim Summers > Sent: Wednesday, April 11, 2007 9:01 AM > To: Samba > Subject: Re: [Samba] Drag and Drop and Crash > > New Update. > > Went to the user machine this morning. Using regedit I went through the > > registry and removed any keys / values that contained the samba server > name. > > Rebooted and then re-mapped a drive. Still no joy. Trying to do a > simple > drag and drop copy form one location in the share to another location in > the > same share causes the machine to reboot. > > Ideas / suggestions? > > Many Thanks > > Jim Summers wrote: >> More info. I went the user's workstation and created a new user. > Then >> mapped a drive to a different share. Attempted to copy a file within > >> that share and boom, reboot. >> >> Hmmmm. >> >> TIA >> >> Jim Summers wrote: >>> Hello List, >>> >>> I am running a 3.0.24 server on redhat EL4. I have a user that has >>> mapped a drive to his home directory on the server. When he copies a > >>> file from the share to a local disk location, desktop for example, it > >>> goes just fine. When he attempts to copy / move / cut and paste a >>> file from one location on the share to another location in the same >>> share, it will literally crash his local machine and it reboots. >>> Other users can do the same no problems. He can map to a different >>> samba server and is able to copy a file within that share. >>> >>> I am suspecting some corrupt file entry or possibly something strange > >>> in the registry not sure. I have looked in his home directory and do > >>> not see any thing out of the ordinary. >>> >>> Ideas / Suggestions? >>> >>> Many Thanks >-- Jim Summers School of Computer Science-University of Oklahoma -------------------------------------------------
This is becoming an interesting problem. The user of the affected machine I was dealing with was in dire need of it working. I ended up using the repair option from the install cd and when that finished and the user logged in everything worked. So at this point I am unsure as to what the cause is. We also are running the dreaded Symantec AV. If I get another machine that this pops up on then hopefully I can have the time to try and isolate the cause. Thanks again for the info. --jim Thomas McNeely wrote:> Hi Jim, > > The Samba listserv rejected this post, so I?m sending it to you > directly. Feel free to try posting it to the listserv if you like, as > you did for Rhiannon. > > ----- > > We also have this problem. We are using Samba 3.0.23d and 3.0.24, both > installed from source code (as opposed to the packages that come with > the operating system), running on Slackware Linux 10.2 and 9.1, > respectively. The problem first appeared for us on April 5th. Our > servers had been running fine with no changes since Christmas when the > problem first appeared. > > The problem manifests as a sudden workstation reboot (without proper > shutdown) when users do most any kind of write operation to a Samba > share ? copying, renaming, or saving files. The affected workstations do > not have a problem performing these operations on Microsoft servers ? > just Samba. Elsewhere on our campus is a Solaris server (unknown > version) running an unknown version of Samba that does not have this > problem. I?ll try to get more info about this. > > There is considerable variation among the workstations exhibiting the > problem ? different generations of hardware, some are domain members and > others not, some are logged into Novell and other not. At this point I > think all the affected workstations run the Novell Client, but that > thought just now came to me and I haven?t experimented with it yet. All > affected workstations have been running Windows XP with SP2. > > We have definitely determined that a key cause of this problem is > Symantec AntiVirus. We can induce and cure the problem at will by > installing or removing Symantec, and we?ve done so many times now. I > don?t have the version info available right now; I?ll try to get it soon. > > Although the timing with regard to MS patch KB925902 is extremely > suspicious, we haven?t been able to experimentally establish any > correlation with that patch. We haven?t ruled out that it could be a > contributing factor though. > > > Tom McNeely > > Western Washington University Libraries > > > >-- Jim Summers School of Computer Science-University of Oklahoma -------------------------------------------------
Hello List,
This looks like it is beginning to happen more frequently. Unfortunately I do
not have a test machine to work with. I was able to get mine resoved by doing
a Windows Repair. The repair option found after the installer has located an
installed windows. You can press 'r' and it seems to simply copy files
from
the cd to the disk. User accounts, most of the registry settings seem intact.
Will need to re-apply patches though.
HTH
-------- Original Message --------
Subject: RE: [Samba] Drag and Drop and Crash
Date: Wed, 18 Apr 2007 10:54:32 -0600
From: <Rhiannon.Henning@sungard.com>
To: <jsummers@cs.ou.edu>
References:
<F43E397F01F82C4088F714D0D1FAE6AB033B85D1@EVS2.univ.dir.wwu.edu>
<461E463B.1090405@cs.ou.edu>
Jim,
I am wondering if either you or Thomas were able to shed any additional
light upon this issue. Yesterday I built up a new XP install, installed
all available MS updates, except KB925902.
We also use Symantec AV + client firewall so of course I installed that
as well. Late yesterday afternoon I gave the user his new laptop.
Today the user was experiencing the same problem where the machine would
crash and reboot after trying to save a file located on the rhel 4
server.
Again I reinstalled winxp sp2 and this has fixed the problem.
Looking at the event logs before the crash I noticed a lot of activity
from Symantec services stopping and starting - not sure if this would be
part of the cause.
This issue is perplexing and time consuming to fix!
I am wondering if there was another recent MS update that is causing
Symantec to crash the pc? As this problem has only occurred within the
last few weeks.
Any thoughts would be greatly appreciated!
Thanks,
Rhiannon Henning * Network Administrator * SunGard iWORKS *
-----Original Message-----
From: samba-bounces+rhiannon.henning=sungard.com@lists.samba.org
[mailto:samba-bounces+rhiannon.henning=sungard.com@lists.samba.org] On
Behalf Of Jim Summers
Sent: Thursday, April 12, 2007 8:46 AM
To: Samba
Subject: Re: [Samba] Drag and Drop and Crash
This is becoming an interesting problem. The user of the affected
machine I
was dealing with was in dire need of it working. I ended up using the
repair
option from the install cd and when that finished and the user logged in
everything worked. So at this point I am unsure as to what the cause
is. We
also are running the dreaded Symantec AV. If I get another machine that
this
pops up on then hopefully I can have the time to try and isolate the
cause.
Thanks again for the info.
--jim
Thomas McNeely wrote:> Hi Jim,
>
> The Samba listserv rejected this post, so I'm sending it to you
> directly. Feel free to try posting it to the listserv if you like, as
> you did for Rhiannon.
>
> -----
>
> We also have this problem. We are using Samba 3.0.23d and 3.0.24, both
> installed from source code (as opposed to the packages that come with
> the operating system), running on Slackware Linux 10.2 and 9.1,
> respectively. The problem first appeared for us on April 5th. Our
> servers had been running fine with no changes since Christmas when the
> problem first appeared.
>
> The problem manifests as a sudden workstation reboot (without proper
> shutdown) when users do most any kind of write operation to a Samba
> share - copying, renaming, or saving files. The affected workstations
do> not have a problem performing these operations on Microsoft servers -
> just Samba. Elsewhere on our campus is a Solaris server (unknown
> version) running an unknown version of Samba that does not have this
> problem. I'll try to get more info about this.
>
> There is considerable variation among the workstations exhibiting the
> problem - different generations of hardware, some are domain members
and> others not, some are logged into Novell and other not. At this point I
> think all the affected workstations run the Novell Client, but that
> thought just now came to me and I haven't experimented with it yet.
All> affected workstations have been running Windows XP with SP2.
>
> We have definitely determined that a key cause of this problem is
> Symantec AntiVirus. We can induce and cure the problem at will by
> installing or removing Symantec, and we've done so many times now. I
> don't have the version info available right now; I'll try to get it
soon.>
> Although the timing with regard to MS patch KB925902 is extremely
> suspicious, we haven't been able to experimentally establish any
> correlation with that patch. We haven't ruled out that it could be a
> contributing factor though.
>
>
> Tom McNeely
>
> Western Washington University Libraries
>
>
>
>
--
Jim Summers
School of Computer Science-University of Oklahoma
-------------------------------------------------
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Confidentiality Notice: This email transmission may contain confidential or
legally privileged information that is intended only for the individual or
entity named in the e-mail address. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or reliance
upon the contents of this e-mail is strictly prohibited. If you have received
this e-mail transmission in error, please reply to the sender, so that
arrangements can be made for proper delivery, and then please delete the
message from your in-box.
--
Jim Summers
School of Computer Science-University of Oklahoma
-------------------------------------------------
> Looking at the event logs before the crash I noticed a lot of activity > from Symantec services stopping and starting - not sure if this would be > part of the cause. > This issue is perplexing and time consuming to fix! > I am wondering if there was another recent MS update that is causing > Symantec to crash the pc? As this problem has only occurred within the > last few weeks.Symantec has *always* been more problems than it is worth... We switched to NOD32 Enterprise from Symantec Corp about 2 years ago, and have been extremely happy with it - and it is *much* lighter on system resources. -- Best regards, Charles