Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 5 subscribers
  • Views 3694 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Safeguard 6.00.0.155 slow using Windows XP and Netware connected drive letters

MatthewMITS

I have a requirement to encrypt a number of PCs (20+), however I have the following problem:

Windows XP (sp3), Novell Client (4.91) connecting to Netware volumes, reasonable spec PCs (Intel SWB motherboards - i3), a policy has been created which does not encrypt other media (usb etc).

When I login to the PC with a local login in works OK, the local drive is encrypted and accessible, however when I login to the network and browse to any netware volumes the drives take a very long time to display - 30 seconds just to see a directory. Without Safeguard the drives display instantly, the processor is idle so not a CPU problem.

Anyone any ideas what I have done wrong on the policies

Thanks in advance

:26143


This thread was automatically locked due to age.
Parents
  • 0
    It might be because netware is using a different mounting system that the windows CIFS UNC share mount points and the safeguard system is trying to either check them for encryption or use encryption on them because it thinks it's a local drive and not removable or network drive. Make sure you policy only specifies the boot volume be encrypted and see if that helps. You can create policies to exclude other volume drive that it's being mounted as, I would also try creating a policy that fobids encryption on say drive letter X and manually mount a test volumes as dive letter X to see if it fixes it, mount a comparison volume without exclusions on letter Y. Give that a shot first.
    :26363
Reply
  • 0
    It might be because netware is using a different mounting system that the windows CIFS UNC share mount points and the safeguard system is trying to either check them for encryption or use encryption on them because it thinks it's a local drive and not removable or network drive. Make sure you policy only specifies the boot volume be encrypted and see if that helps. You can create policies to exclude other volume drive that it's being mounted as, I would also try creating a policy that fobids encryption on say drive letter X and manually mount a test volumes as dive letter X to see if it fixes it, mount a comparison volume without exclusions on letter Y. Give that a shot first.
    :26363
Children
No Data
Unfiltered HTML