Jump to content
pspencer

Can Not Scan Redirected Folders Or Network Drives On Winxp

Recommended Posts

We were evaluating Immunet (Free+ClamAV) for potential use on some Windows XP workstations, but find Immunet is unable to scan anything on a network drive or a folder that's been redirected by group policy to a network share. And since our users' desktops and "My Documents" folders are all redirected, that means nothing on the desktop or documents folders can be scanned.

 

Is this a fundamental limitation of Immunet, or just a bug in the current version (3.0.8.9205)? Is it connected to the issue I've seen posted about elsewhere that this version messes up NetBIOS name resolution and file sharing on Windows XP and Server 2003 platforms?

 

Symptoms:

  • If you right-click a file or folder and choose "Scan Now", the dialogue box that pops up shows "0 files scanned, 0 threats found, ... etc."
  • In agent.exe.log, an error message like the following is logged (if trying to scan a file named index.txt on network mapped drive W:):
     
    (84221, +32707 ms) Dec 18 12:13:27 [2632]: ERROR: unable to open handle using filename(W:\index.txt)... : 3 : The system cannot find the path specified.

Thanks for any info, particularly as to whether immunet is expected to be able to scan redirected folders and network drives, and, if so, whether a fix is likely in the next version (and when that next version is likely to come out).

  • Like 2

Share this post


Link to post
Share on other sites

I believe what you are seeing is the compatibilty issue with Win XP Pro being used in a business enviroment and the newest version of Immunet as you mentioned. I've been told that these issues will be ironed out in the next build but when the release date will be I have no info on that. Hopefully Soon! If you would like to uninstall the 3.0.8.9025 version and try an older version as a temporary measure until the newest build that has the fixes is released here is an installer for the 32bit 3.0.6.8523 version: https://sourcefire-a...n-us-32-tcp.exe Immunet Protect does not support 64bit versions of XP. Cheers, Ritchie...

Share this post


Link to post
Share on other sites

I believe what you are seeing is the compatibilty issue with Win XP Pro ... If you would like to uninstall the 3.0.8.9025 version and try an older version as a temporary measure until the newest build that has the fixes is released here is an installer for the 32bit 3.0.6.8523 version: https://sourcefire-a...n-us-32-tcp.exe

 

Thanks -- but that url seems to link to the 3.0.8.9025 version not the 3.0.6.8523 version (if I run it, it installs 3.0.8.9025; I thought maybe it was pulling some updates from the Internet silently during installation, but then I saw that if I simply right-click on the installer downloaded from that url and choose "Properties", it shows "3.0.8.9025" in the "version" field.)

Share this post


Link to post
Share on other sites

You are correct. I just tried that link and got the 3.0.8 version too. That's weird because that off-line installer should be the older version. Sourcefire must have changed the URL so you only get the newest version. Sorry about that! I don't have any other off-line installer link for you to try at the moment either darn it! Using the bootstrapper you automatically get the newest version.

Share this post


Link to post
Share on other sites

No Brian, I don't have access to any older off-line installers anymore. I think your best bet would be to send support an email asking if it's possible to recieve an off-line installer for an older version that doesn't have the bug present. I'm really crossing my fingers that the developers roll out the next version soon but alas I have no info when that will be. I'm not kept very well informed at all when it comes to things like this but I do try my best with the limited resources at my disposal.

Share this post


Link to post
Share on other sites

Hi pspencer,

 

This is indeed a fundamental limitation of Immunet at this time. Due to latency issues, we do not do any scanning of network drives. Attempting this has caused unacceptable performance issues. We have plans to address this bug in the future. As it stands though, Immunet may not be the solution you're looking for. I am sorry I could not be of more assistance!

 

Nick

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...