Jump to content

nwarshawski@sourcefire.com

Members
  • Content Count

    14
  • Joined

  • Last visited

  • Days Won

    1

nwarshawski@sourcefire.com last won the day on September 19 2012

nwarshawski@sourcefire.com had the most liked content!

Community Reputation

4 Neutral

About nwarshawski@sourcefire.com

  • Rank
    Sourcefire Administrator

Profile Information

  • Gender
    Not Telling
  1. 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
  2. Hello, A restore can be reattempted after a reboot through the Immunet GUI. If this fails again, we can also attempt to decrypt the file if you email it to us at support@immunet.com. If possible, please include a Support dump, by using the Immunet Support Tool and attaching the file it drops on the desktop. Nick
  3. Hello mkultra, I'm sorry to hear that Immunet has been causing problems for you! Sorry for the delay. We would absolutely like to see the history files. An incompatibility with Dropbox is a priority bug. Currently, we have no known conflicts with these applications. If possible, I'd like you to send that to support@immunet.com. If the attachment is too large, you may be able to send it using gmail and their drive feature. I suspect that the quarantined files are largely going to be repetitions of the same temp file that was repeatedly dropped and quarantined. This directory may have been different from the main Dropbox directory. Was this the folder you initially excluded? Nick
  4. Looks like we had an issue with one of our servers. This has been resolved now and you should be able to connect to the cloud now!
  5. Hi riccasto, Thanks for the submission. We've received the Support Tool and are looking into this, and will get back to you ASAP. Nick
  6. Hello RocketWolf, Thanks for reporting this error. To be of any assistance I need a little more information. Please see the forum guidelines on support http://forum.immunet.com/index.php?/topic/909-how-to-post-an-effective-bug-report/&do=findComment&comment=4797 and include the required information in your submission. Could you also email support@immunet.com with the SDT report and your license key? Nick SDT report information http://support.immunet.com/tiki-read_article.php?articleId=10
  7. Hello All, The profile issue has been resolved, so profiles and PMs should work properly now. Thanks for your patience. Nick
  8. Here's an idea. Please download Process Explorer from http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx Attempt an install Run Process Explorer as admin and Ctrl+F search for BaseNamedObjects\P Look for anything that ends with that search, as in, ends with just a P. To help us out, could you highlight and copy any process that contains it, with the following columns visible: User Name, Description, Company Name, Image Path, Window Title, Window Status, Session, Command Line and Autostart Location. Then paste it in a reply here! If this exists within another process or another installer, it would be the reason why an install fails. If you find a process with it, shut that down and an install should go through. Nick
  9. Hi Dave, We're looking into this and will get back to you as soon as possible. Thanks for the heads up! Nick
  10. Another thing to do before an install would be to manually remove C:\Documents and Settings\All Users\Immunet or in Win7 C:\users\all users\immunet and any files in the directory. (After an uninstall) Nick
  11. Hi Dave, This is really strange! There are a few things that may be going on here. Sometimes, an install will queue itself until after a reboot, or there may be Immunet leftovers preventing a fresh install. I'd like you to try a few things. First would be to check Programs and Features for Immunet 3.0, and uninstall it if it's there. Next would be to also check for Suze Orman or Trusted ID Secure Scan, if you've ever had those, and uninstall that as well. Next would be to look at your Services (Windows key, type services). If you see Immunet 3.0 or any other Sourcefire/Immunet services, make sure they're stopped. Finally, check your msconfig (Windows key, msconfig, enter) boot settings and look for any Immunet artifacts there. Ensure there are none, or that they're disabled, and restart. After the restart, check your processes for agent.exe and your services for Immunet 3.0. Neither should be there. Wait a bit so that its clear that no Immunet installs are queued. Download an installer from http://download.immunet.com/push/immunet/ImmunetSetup.exe and run it once. Don't bother with the silent options because that will only keep information from us. Hopefully, this works! If it doesn't, let us know and we'll keep at it!
  12. Hi Brian, Currently, the best solution I can offer is to turn off Clam AV or Email Scanning through your Immunet Settings (Clam AV Detection Engine or Scan Settings, respectively). We'd like to fix any false positives we see, so it would be great if you emailed these .pdfs to support@immunet.com. We'll forward them to our Clam AV team and get this straightened out. Nick
  13. Hello jgroep, I have been unable to replicate this bug on the version of Immunet you're using. Could you please take a screen shot of the missing telemetry option? To fix this problem, please try temporarily disabling the community. If that does not work, a full uninstall/reinstall usually fixes problems like these. Thanks
×
×
  • Create New...