Endpoint Protection

 View Only
Expand all | Collapse all

Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

Migration User

Migration UserAug 20, 2010 05:23 AM

Rafeeq

RafeeqAug 20, 2010 10:51 AM

Migration User

Migration UserSep 03, 2010 07:39 AM

Migration User

Migration UserOct 05, 2010 04:18 AM

Migration User

Migration UserNov 19, 2010 10:52 AM

Migration User

Migration UserFeb 01, 2011 02:11 AM

  • 1.  Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Jul 12, 2010 11:04 AM
    Hello,

    I have a number of Windows 7, Vista and XP workstations that are installed with SEP 11 ru6 and ru6a.  I also have a Windows 2008 file server that is also installed with SEP 11 ru6a.

    Users who are using the Windows 7 and Vista workstations are unable to copy files from the workstation to the Windows 2008 file server, the file copy process hangs with either no files being copied or only a few files and then the rest do not complete.  But users on Windows XP can copy the same files to the file server no problem.  I also notice that users on Windows 7 and Vista can copy to a Windows 2003 file server without problems.

    From the experimentation I have done, I have found that if the process smc.exe (Symantec Management Client) is terminated, then the copy from Windows 7 and Vista to Windows 2008 works correctly without problems.  When I delved into this problem a bit deeper, I found that if I disable the SMB 2.0 support on the Windows 2008 file server, users on Windows 7 and Vista can copy files correctly without problems, but they can't with SMB 2.0 enabled.

    Windows Vista, 7 and 2008 by default use the SMB 2.0 protocol for file share, but Windows XP and 2003 use SMB 1.0.  Forcing all clients to use SMB 1.0 fixes the problem, so there looks to be an issue with SMB 2.0 support in SEP.  I tried downgrading the version of SEP to SEP 11 ru5, but there is a problem with this version and "Offline" files used by Enterprise Vault and many other archiving programmes (SEP 11 ru5 causes an archive recall failure), again, using the SMB 2.0 protocol, but turning off SMB 2.0 fixes this.

    This problem seems to be present in SEP 11 ru5, ru6 and ru6a, I have not tried earlier versions.

    Is Symantec aware that there is a problem with the SMB 2.0 support in SEP and what is the ETA on fixing this?

    Many thanks.

    Richard.


  • 2.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Jul 12, 2010 04:35 PM
    It seems like other users (including me) have reported similar problems with RU6a and NTP.

    http://www.symantec.com/connect/forums/copy-over-network-freeze-when-copying-large-files

    The file copy proces freezes/stalls (the file copy window is still "responding" but no data transfer occurs) when you try to copy files from a Windows Vista or 7 PC (32bit or 64bit) running RU6a and NTP component to a Windows Vista or Windows Server 2008 machine. The problem occurs on the source machine because the file copy process also stalls when there is no SEP installed on the target machine. The problem does not occur when the NTP component is not installed.






  • 3.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Jul 13, 2010 04:56 AM
    Many thanks.

    From the reasearch I did, it does appear that many other people are experiencing the same problem, there are several threads about this on this forum.  I did try disabling NTP but that didn't make any difference.  I will uninstall SEP and re-install it without NTP on all my Windows 7 clients and see what happens.


  • 4.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Jul 13, 2010 10:05 AM
    I deployed a new package to my client PCs without NTP and don't have any issues anymore on my Windows Vista and 7 clients so there is definately a problem with RU6a, NTP and SMB2.0. Don't want to downgrade to RU5 so temporarely uninstalling NTP until they fix this seems like the only workaround right now.


  • 5.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Jul 14, 2010 04:47 AM
    I have uninstalled NTP on all of the Windows Vista, 2008 and 7 clients, the file copy now works correctly.  So I concur, there is a problem with NTP in ru6a when used with SMB 2.0

    Disabling NTP doesn't work, it must be uninstalled.

    How was this not caught in the QA labs? 


  • 6.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Jul 20, 2010 05:58 AM
    Hello everyone,

    I'm experiencing the same issue here. What I have found out so far:

    There is a special kind of files involved everytime it hangs. I suspect packed *.exe Files to be a problem. Like the dotnetfx35.exe Installer package wich I tried to move between my client and a server cannot be copied and freezes the transfer. Other files, like a 4GB image of a DVD work fine.

    To finish the transfer I go to task manager, kill the smc.exe prozess (it comes back up) but the transfer proceeds fine then.

    Any further information if this will be fixed? Thinking about rolling back to ru5... Why is there a problem every time I update my clients? I'm having a hard time telling people why we still rely on this Symantec product.

    Cheers,
    Chris


  • 7.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Jul 20, 2010 09:15 AM
    Not to excuse them, because, as you stated should have been caught by QA...

    Most best practices for SEP indicate not to install NTP on Servers. 

    Regardless of that fact, there is something broken in SMB 2 on all platforms connecting to 2008 server.  MAC OS 10.x requires an SMB (Samba) share to be written out "SMB://[servername]:139/[share name] ONLY when connecting to Windows 2008 box.  Port number required because it is not handling NETBIOS sessions properly. 

    One would think that SMB 2 to SMB 2 from M$ would work right, but you are not the first to experience issues and a few hotfixes (KBs) have been released addressing several of the issues.

    Have you tried connecting with a Client that has NTP enabled, but not installed Server side?

    I don't personally use NTP at all here, had too many issues in the past, but would you consider a FW rule (I know it's redundant) allowing all traffic from internal to internal ono port 139.

    One other thing, I have been considering, and probably going to build a TEST LAB for, is to test the SPI factor of the NTP Firewall from Symantec.  Often times, people have complained about issues related to large files.  If the system is not allowing a certain MTU through, it could cause this issue.  Some SANs use Jumbo frames for example to pass along traffic, fiber connections, MUXes , etc.  All hypothetical at this point, but definitely would like to get some Answers if these things were tested in the Symantec Labs or if we have to do the testing for them...  

    Fun with Firewalls...  *sigh*


     


  • 8.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Jul 23, 2010 11:28 AM
    Hi Richard,

    I am trying to log a case with support.

    In the mean time I found out that the problem only occurs when you copy from a Vista or Windows 7 machine (which has NTP installed) to a Vista or Windows 2008 server. It does not happen when the target is Windows 7 or Windows Server 2008 R2 (or Windows 2003/XP = SMB 1.0) so it is not related to SMB 2.0 in general but how SMB 2.0 is handled in Windows Vista and Windows Server 2008.

    Another funny thing I noticed is that it occurs on PCs that are able to transfer files really fast. On one of my Dell workstations which is able to achieve almost 100% network throughput  at 120MB/s it happens almost instantly. SEP NTP does not block any ports because when the freeze occurs because you can open a second explorer window and start copying another file to the same server.

    I also tried to copy the same file I used for simulating the problem from the Vista Machine with NTP to the Windows Server 2008 without NTP by intiating the copy on the Windows Server 2008 (pull transfer) and this works fine. It only occurs when you push a file from a machine running Windows Vista or Windows 7 and NTP to a Windows Vista or Windows Server 2008.

    I don't have any firewall, intrusion prevention or application and device policy enabled (the components are installed).


  • 9.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 02, 2010 06:46 AM
    I've posted on the other thread mentioned above but does Symantec have any response or fix for this problem?


  • 10.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 02, 2010 07:35 AM
    Hi All,

    SMB 2.0 is quite different in how it deals with files, from what I understand, the file is actually cached, prior to being written to the disk, this can at times cause problems with some software where files are modified across the network.  AV is one of those pieces of software, there are others too.

    Can you try adding/changing the following registry key?

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\DirectoryCacheLifetime

    The default setting is 10 (seconds), can you try setting that to 0 and try your tests again?

    thanks




  • 11.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 02, 2010 12:05 PM
    Hi Paul,

    I made the registry setting on the client test PC and restarted the workstation service. File copy process still hangs. It only hangs when you copy from a SMB2.0 capable machine with RU6a and NTP module installed to a Windows Vista or Server 2008 machine. I don't have any lockups when a copy files to Server 2008 R2 and Window 7 machines.

    We are not using the SEP Firewall so no policy is defined for that. The target servers don't have SEP installed and the windows firewall is disabled. We are only using NTP for application and device control and IPS. We tested extensively with RU5 before deploying and the lockups never occurred with RU5. The lockup is completely random (it does not always stall at the same position in the file if you try to copy the same file over and over again) but it occurs much quicker if you take a large file (a 4GB DVD iso for example) or a large set of files. I also noticed it while copying windows user profiles.

    No lockups occur when you unistall the NTP component. Disabling the policy does not help.

    I have already reported this case. The case number is 421-498-511.


  • 12.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 02, 2010 12:11 PM
    Thanks ETH0, any chance you can try setting the regkey on the server too, just to cover all bases?

    I'll take a look at the case you have logged.


  • 13.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 02, 2010 12:33 PM

    Still Freezes when registry key is added to target server (and workstation services is restarted). I noticed that  if the file copy proces freezes you can still open another explorer window (on the same source machine) and start copying files to the same server, so it seems that SMC.EXE locks the copy process. If you kill the SMC.EXE process the file copying resumes.

    In one of my earlier posts I mentioned that the lockup did not occur on Windows 7and Server 2008 R2. Now after running some new tests it also locks up if I copy files to a Windows 7 machine.



  • 14.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 03, 2010 08:26 AM

    Hi Paul,

    I applied your registry setting on a number of clients (didn't try it on the server) and it made no difference.

    Stephen



  • 15.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 03, 2010 10:19 AM
    "quoting"
    [...]You can create registry keys below to control the cache lifetime.  Under  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters:
     
    FileInfoCacheLifetime
    FileNotFoundCacheLifetime
    DirectoryCacheLifetime
     
    They are all REG_DWORD type in seconds.
     
    For your reference, you can refer to the link here:
    http://blogs.msdn.com/winsdk/archive/2009/07/10/file-exists-access-getfileattributes-findfirstfile-findnextfile-stat-behavior-over-smb-2-0.aspx
     
    [...]

    "End Quote"
    * * * * * * * * *
    Courtesy:
    Wilson Jia

    http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2networking/thread/2b4b34f3-b2e3-47f1-9859-b5fd7db36d3e


  • 16.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 03, 2010 01:10 PM

    The lockup occurs during file copy (bytes are already transferred meaning that the file was already created and the 10 seconds already have passed). The article refers to problems when (programmatically) creating new files on SMB2.0 shares and because of local caching you cannot use file exists to check if the file was created succesfully.  Bottom line is that the copy proces does not lockup if  the NTP component is not installed so we should not be messing with LanMan parameters anyway because file copying works fine without NTP.

    Can someone from Symantec please indicate ift hey are able to reproduce the problem ?



  • 17.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 04, 2010 06:57 PM
    We can.. but we also see that changing the SMB2 parameters does fix this in most cases.

    Can you confirm your case ID, I can't find it on our tracking system

    thanks


  • 18.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 05, 2010 11:15 AM
    Case 412-498-511 (Cannot copy files using SMB 2.0     protocol with   SEP 11 ru6 and ru6a when NTP ...)

    Thanks for the update


  • 19.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 11, 2010 08:24 AM
    Paul... is there any update on this? We are still experiencing this problem even after the registry change(s).


  • 20.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 16, 2010 05:39 AM
    Are there any updates?

    We are experiencing the same problem in our environment.  I have been monitoring this thread, but it seems to have gone quiet!


  • 21.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 16, 2010 09:19 AM
    Hi,

    Case got escalated. Still trying to convince the tech support guys that it is a bug. They are still convinced that they can solve it by changing policy settings opening firewall ports etc. I guess we all have to wait until they find out that it is a bug in RU6a.



  • 22.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 20, 2010 03:42 AM
    It still happens in RU6 MP1. I did not expect it to be fixed because it was not mentioned in the release notes. I am still waiting for a fix so we can start using NTP again.


  • 23.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 20, 2010 05:23 AM
    Too bad! I was hoping for a fix on that sooner :(


  • 24.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 20, 2010 10:38 AM
    Got a call from support this morning. It is considered a defect in the product. I don't know when (in what version) they will fix it.


  • 25.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 20, 2010 10:51 AM
    Thanks for the valuable info...


  • 26.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Aug 24, 2010 04:24 AM
    ETH0, thank you for the update. At least Symantec now realise it's a bug.

    It's still causing major headaches here - I will have to consider disabling NTP until it's fixed.


  • 27.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Sep 03, 2010 07:39 AM
    Is this bug sorted, does anyone know this ?


  • 28.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Sep 04, 2010 01:16 AM
    Is there any official knowledgebase article where Symantec agree this bug? surprise

    Rgds, Jyrki


  • 29.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Sep 07, 2010 09:24 AM
    We have an update on this case. The issue is targetted to be fixed in next release 11.0_RU7. We do not have information about when it will be released. But I'll update you as soon as I get any update information on this.
    The currect available version on fileconnect site is RU6MP1, so it will definitely take some more time for RU7 to be released.

    In the meantime I have to choose between disabling SMB2.0 on my entire network or disabling NTP, Firewall and Application and Device Control.

    The bug was introduced in RU6. In RU5 it was working fine so how hard can it be to fix it.


  • 30.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Sep 09, 2010 08:47 AM
    Asked Symantec support and they replied that there is no public KB article available.


  • 31.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Oct 05, 2010 04:18 AM

    any news on the fix-release date?



  • 32.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Oct 05, 2010 04:53 AM

    Still waiting for a statement from Symantec when this bug will be fixed.

    It is not acceptable that you have to disable SMB2.0 for NTP to work properly.



  • 33.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Oct 11, 2010 07:27 AM

    Why can't Symantec prioritize this and get it fixed immediately? I was planning to deploy SEP RU6 MP1 with NTP to over 1900 Windows 7 systems. Now I have to not install NTP until this is resolved.



  • 34.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Oct 12, 2010 10:43 AM

    Found this thread to be a saviour as we have a case pending with issues of this nature and haven't been able to track it. If it helps, Case 412-321-038 (Customer is seeing file transfers taking a long time if they have "trust fi...). Started back at the beginning of August and no resolution yet.

    Although we have been going at this for months now, upgraded to RU6 MP1 and everything and didn't fix the problem, so I am assuming Symantec will fix this on another maintenance release or another patch.

    The problem is that our file servers are all 2008 R2 64-bit and all computers are now being replaced with Windows 7, jsut increasing our problem.

    If I find a workaround, will surely post it. That registry setting did not help either. 



  • 35.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Oct 12, 2010 02:02 PM

    According to Symantec support you have to disable SMB2.0. I have not tested this myself but I think it is only necessary to disable SMB2.0 on the workstation service on the PCs that are running SEP witn NTP.  The follwoing website has details on how to disable SMB2.0. If this works you can probably disable the SMB2.0 on your workstations via Group Policy.

    http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm

    So, for troubleshooting purposes, mostly in an environment that has mixes operating systems, you might want to consider disabling SMB 2.0. You need to do so on both the "client" and the "server" operating systems. To disable SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems run the following commands:

    sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
    sc config mrxsmb20 start= disabled
    

    Note there's an extra " " (space) after the "=" sign.

    To enable back SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems run the following commands:

    sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
    sc config mrxsmb20 start= auto
    

    Again, note there's an extra " " (space) after the "=" sign.

    ===



  • 36.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Oct 12, 2010 03:46 PM

    I tried the above steps without success.

    I'm copying from a Windows 7 64bit machine to a Windows Server 2008 R2 machine.

    Seems to start the copy process, then hangs on "Calculating..." until I run "smc -stop".

    I will reboot my workstation and see if that makes any difference.

    Thanks for the suggestion as the last I've heard...it will be RU7 before the Teefer2 driver is fixed and then approved by Microsoft and finally quality tested by Symantec. :-(

    -Mike

    P.S. Just noticed in the document you referenced: "You need to do so on both the "client" and the "server" operating systems." Not sure if our server manager is willing to try this, but hey, it's worth a shot.



  • 37.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Oct 12, 2010 04:12 PM

    Now I don't want to get to excited...but sure enough, I rebooted and yes, a copy job of 4 120meg files completed!! I plan to test this on a few more machines before I jump for joy. This was by changing the SMB2 settings on the local machine ONLY.

    Thanks for the glimmer of hope ETH0.

    -Mike



  • 38.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Oct 13, 2010 09:10 AM

    SEP RU6 MP2 will goes in December and SEP 12.0 in the first half of 2011.

    You should ask support for a Duty Manager and escalate this defect and ask him where in the defect queue is the bug and time to resolution.

     

    Best regards,

    Vladimir



  • 39.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Oct 13, 2010 09:45 AM

    I've written a little utility (based on ETH0's suggestion above) that will toggle the current state of SMB2 and reboot the machine. So far I've run it on 3 machines and it appears that the Network Disconnect/SMB2/Large file copy issue has been temporarily mitigated.

    If anyone is interested, I can post the utility in the downloads section.

    If this continues to work, it will be huge for us...our previous work around was to disable the SMC service for a few minutes while the copy completes and then re-enable it. Less than optimum.

    Vladimir...I have spoken with an escalation manager at Symantec who gave us a spring time frame for the SMB2/Teefer2 defect fix. It may be called RU7 or SEP 12...who knows. Rumor also has it that RU6 MP2 may be as early as mid November.

    -Mike



  • 40.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Oct 20, 2010 02:11 PM

    Pretty much have the same problems going on here and NTP seems to be the culprit.  Had to un-install from all my Windows 7 PC's.  Not at all happy about it. 



  • 41.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Oct 21, 2010 04:17 PM

    Used the same script I mentioned in an earlier post to disable SMB2.0 on the workstation service of my Windows Vista and 7 Clients. You only have to run the script on the workstations. Servers can still use SMB2.0 to communicate which each other (if you don't have NTP installed on your servers)

    Going to deploy the SMB1.0 settings via Group Policy to all my workstations.



  • 42.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Nov 16, 2010 02:16 PM

    Is there any word on when this will be addressed in the software release?



  • 43.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Nov 19, 2010 09:11 AM

    from Symantec was sometime in the spring.

    Here is the work around we've implemented until then.

    http://www.symantec.com/connect/downloads/smb2-toggle-too-mikes-tool-set

    Hope this helps,

    -Mike



  • 44.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Nov 19, 2010 10:52 AM
      |   view attached

    view SEP_SBS2003_BestPractices

    Attachment(s)



  • 45.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Nov 19, 2010 11:34 AM

    I'm not exactly sure what you're trying to point out in reference to this thread.

    Can you please enlighten me/us?

    Thanks,

    -Mike



  • 46.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Dec 03, 2010 06:04 AM

    Deployed SEP RU6 MP2 today and the bug is still present (tested on Windows 7 x64 and x86)



  • 47.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Dec 10, 2010 04:41 PM

    Thank you for saving me the hard work of installing and testing, only to find out it's still not fixed.

    Symantec:  Boo!

    I don't understand how this has gone on this long not as "high priority." 

    You need to make this high priority and waiting to RU7 is no excuse when there's been 2 "maintenance patches" since.  I can understand missing it on MP1, but not MP2.



  • 48.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Dec 11, 2010 11:20 AM

    Why hasn't there been atleast a KB article about this huge issue?

    This is what we get for purchasing Symantec products?



  • 49.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Dec 11, 2010 04:21 PM

    I have recently opened a case about Windows 7 Backup hanging when the target is a Vista network share.   I have now stumbled across this thread with very similar issues.  Add me to the list of those surprised that this has not been fixed.  Waiting and .... waiting for RU7!!



  • 50.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Dec 12, 2010 02:42 PM

    We Really need a positive Response from Symantec.

    This problem has been a known issue for some time.

    Give us a status update.

    There has been several threads in multiple forums etc...

    I had to turn off Network Threat protection to allow my Windows Vista and Windows 7 users to effectively use our network the way Microsoft intended it to be.

    My opinion on this is that we should be compensated for a product that is not functioning, be given an option to change to a solution that does work, or have the program fixed Now!

     



  • 51.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Dec 12, 2010 04:02 PM

    Has anyone called Support to find out if this is being addressed?



  • 52.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Dec 14, 2010 12:40 AM

    http://kb2.adobe.com/cps/860/cpsid_86063.html

     

    Don't understand why this smb2 fix is too difficult for Symantec?

     

    /Jyrki



  • 53.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Dec 14, 2010 09:55 AM

    I received from Symantec a couple months ago. I don't know what the current status of the Symantec fix is, because in all honesty, we have implemented the work around I posted above and have put the issue on the back burner.

    From what I understand (Someone from Symantec please corrent me if I'm wrong)

    1) The issue lies in an incompatibility with SMB2 and the Teefer2.sys (Firewall aka: NTP) driver.

    2) The incompatibility has already been identified, and fixed, by Symantec.

    3) The Teefer2.sys driver has to go through the Microsoft (WHQL?) signing process which I guess takes some time (months?) for testing and approval. On both the Symantec and Microsoft sides.

    4) The last I heard what that we "us in particular" would probably not see the new Teefer2.sys driver until sometime in the spring. (RU6 MP3 or RU7 or SEP12)

    Again, if someone from Symantec would like to clarify my points above, feel free...this is all from what I remember from a couple months back and may now have a new, updated, timeline.

    In our environment, not all machines exhibit the problem so that's why we have implemented the "fix" I posted above.

    An official reply from Symantec would really be nice, but if that doesn't happen...this is the information I have to offer.

    -Mike 



  • 54.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Dec 15, 2010 02:50 AM

    Teefer2 driver was updated in RU6MP2. Please have a look at the release notes:

    http://www.symantec.com/business/support/index?page=content&id=TECH103087

    Components included in this version (RU6 MP2):

    Teefer2 11.0.6170.27

    Components included in this version (RU6 MP1, RU6a, RU6):

    Teefer2 11.0.5708.18 (The Bug was introduced in this version. In RU5 SMB2.0 is working)

    Components included in this version (RU5)

    Teefer2 11.0.5

    The FixIds relating to Teefer/NTP are in the same range as the other bugs that were fixed in MP2 so it seems that there is another reason for Symantec not to fix the problem.



  • 55.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a



  • 56.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Dec 23, 2010 03:41 PM

    My fix to this is uninstalling the NTP part of SEP.  I can't wait months for another solution.



  • 57.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Dec 27, 2010 06:33 AM

    Hi All,

    as per last update in the defect notes on the 24th Dec. the issue will be fixed in RU6 MP3. And no, I have no ETA for that yet.

    Regards, Tom



  • 58.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a



  • 59.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Jan 12, 2011 09:10 AM


  • 60.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Feb 01, 2011 02:11 AM

    Info from kb.

    Rgds, Jyrki



  • 61.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Feb 23, 2011 12:14 PM

    I just reinstalled the NTP component of SEP 11 ru6 mp2 and I could not reproduce this problem.  ?  I did this with plans to see if Win 7 SP1 would fix the problem.   I have now installed Win 7 SP1 and I have retested with NTP still installed.... no hangs!   Anybody else doing any new testing?



  • 62.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Feb 24, 2011 10:01 AM

    Using my utility posted above, I re-enabled SMBv2 (after upgrading to SP1) on my Windows 7 Enterprise, 64Bit machine.

    I first tried 1.5 GB up to a 2008 R2 Server, the copy job hung on the "Calculating" window (stopping the smc service allowed it to finish). I then tried 325 MB to the same server...same result.

    So from that basic testing, I would content that no, Windows 7 SP1 does not resolve the large file copy issue.

    -Mike



  • 63.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Feb 24, 2011 10:55 AM

    Yes, I agree it is still broken....   I realized this morning that my target machine still had NTP removed.   I just reran my test with Win 7 SP1 saving to a Win 7 SP1 with both running NTP 11 RU6 MP2 and sure enough it hung at approximating the same point.   Before I had thougth that it was only the source machine causing the problem. 

    Sorry for the false hope.

    John



  • 64.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Feb 24, 2011 11:45 AM

    Symantec has investigated this issue and has it scheduled to be resolved in RU6 MP3.

    http://www.symantec.com/docs/TECH139768



  • 65.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Feb 24, 2011 02:23 PM

    Ran a quick test with Windows 7 SP1 x64 and RU6 MP2 copying files to Windows Server 2008 (SMB2) and the copy process still stalls after a while so SP1 does not fix it for me.



  • 66.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Feb 28, 2011 03:56 PM

    Following this M$ document, we created the 3 registry entries herein listed.

    We noticed that on our x64 systems (because those are the only ones we use in Win 7) connecting to and copying to / from a Windows 2008 server with NTP enabled on the workstation, the issue seems to have dissappeared.

    Not only that, but the NIC activity itself, peaks to 95 - 96% capacity when tranfeering large files.  I.E 4 gigs in 30 seconds...

    http://technet.microsoft.com/en-us/library/ff686200%28WS.10%29.aspx

    If others are interested in trying and giving feedback...



  • 67.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Trusted Advisor
    Posted Mar 21, 2011 02:26 PM

    Hello All,

    Symantec Endpoint Protection RU6 MP3 is Released.

     

    Please Check the same and download it from https://fileconnect.symantec.com



  • 68.  RE: Cannot copy files using SMB 2.0 protocol with SEP 11 ru6 and ru6a

    Posted Mar 21, 2011 05:04 PM

    Did some quick tests on my test machine I used to simulate and report the bug (Windows 7 x64) and after installing RU6 MP3 and enabling SMB2.0 file copying process does not freeze/stall anymore if you have NTP installed.

    I guess I have to figure out now how to enable SMB2.0 again on all my workstations using Group Policy.