I'm having the same problem with crashing shares on Win Svr 2008 64-bit with SAV 10.2.2.2000 installed as a managed client.
I'm working with Symantect Tech support on this -- an ill-trained person who can't even keep track of the versions of Windows and SAV I'm running desperately seaching a database and telling me do try the same "fixes" over and over, Etc. I'm waiting for a call back from her now.
On my network, I have SAV Server and System Center version 10.1.7.7000 on Win Srv 2003 32-bit and SAV client 10.1.7000 on XP and Win Srv 2003. All were working fine. Some months back I added some Vista 64-bit clients with SAV version 10.2.0.298. It took some doing to get them configured as managed clients and I had to manually configure them to update their specs, but, after that, they seemed to work. I then added some more Vista 64-bit clients using SAV client 10.2.2.2000. These immediately had issues with latency and crashes when accessing shares on Win Svr 2003 machines. Backgrading them to 10.2.0.298 fixed the problem.
Now I'm testing and trying to bring a Win Srv 2008 64-bit online as a file server. I called Symantec tech support and was told to use the Vista 64 10.2.2.2000 client on this server.
Immediately my client machines -- both XP 32 and Vista 64 get latency and/or totaly unavailability of shares on this machine. Tech support, told me to disable SmartScan. Initially that seemed fix it, but then after applying this month's Windows patches to the server (coincidence?), the shares became totally inaccessible. I then switched off Auto Protect entirely and at least in my initial tests the shares seem to be accessible. Is this the best I can hope for? Any other fixes I might try? How about vers 10.2.0.298 which, as I said above, and unlike the vers 10.2.2.2000 doesn't cause the share access latency/crash problem on Vista 64-bit, shoud I try that vers on Win Svr 2008 64-bit?
Thanks,
Lee