Jump to content

Francis

Members
  • Content Count

    74
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Francis

  1. Hey Ritchie, Unfortunately I can't add much to what Brian has stated above, but I can say that the general roadmap we have already outlined will not be changing drastically any time soon (in fact when things do begin to change, it will be gradually). For the next couple of months or so, business will remain as usual. Thanks, - Francis
  2. Hi Thiago, Yes indeed, Immunet is free for anyone and everyone to use (including corporations). Welcome to the community! - Francis P.S. I'm moving this Topic into the General Forum which is a better suited location for this type of inquiry
  3. Hello, Sorry about the delay on this one. One of our support members will (if they haven't already) reach out to you with some information on how to go about this. For future reference to anyone else in this same situation, please send an email to support@immunet.com. Thanks so much, - Francis
  4. Hi spywar, I can assure you that Immunet hasn't died and that the next release will be coming later this year, although it will still be in the 3 range rather than 4, version wise. Thanks, - Francis
  5. You could also think about signing up as an affiliate. More details here.
  6. Basically yes, and that's already in place which is the reason the community feature in the UI doesn't serve any additional purpose.
  7. I don't believe that it is possible. On the bright side, we're actually headed towards of complete removal of the community feature as it doesn't serve any real purpose anymore, so it hopefully won't matter for much longer.
  8. Yes, unfortunately English is the only language that fully supports Immunet's latest build. All other language options will download the 2.0 version.
  9. Unfortunately not. When you perform an uninstall and select "No" when prompted if you're going to install again, the agent nukes all of those .db and .xml files for you, so when you do re-install you're getting fresh copies of those files created once more.
  10. Sorry that I still don't have a resolution for this one, but we do have the issue logged and most likely it will be fixed in the next major release. Thanks for your patients in the mean time!
  11. Hi guys, This is actually an odd issue. Usually when we used to see this error it's due to some resource contention between the agent and the iptray. The both try to lock onto the local.xml and both fail (this can lead to a corrupted xml file). In this case, a simple re-install of Immunet (clearing out the xmls) or even just a plain old computer restart can do the trick. The other way we've seen this is if you have multiple instances of the iptray running (for instance if you're logging into your computer using multiple users and starting the tray in more than one of these accounts), then the tray can't lock into the xml either. However, a simple restart will fix this issue as well. What makes this odd is that Immunet hasn't been updated in a little while (no code changes to the tray or agent), and yet I've suddenly started seeing more instances of this issue appear. We're currently looking into it now, but xonz, could you email me at support@immunet.com and link this thread. I'd like to get you a logging build that will hopefully help us debug the issue and get a fix out for it right away. Thanks, - Francis
  12. Absolutely! If Immunet is currently running for you without any issues than you have nothing to worry about.
  13. Hey guys, We actually aren't releasing a new version of the agent just yet. What you're seeing is the version number of the installer, of which we've just released a new version that addresses some fixes that take place during installation. We'll be sure to post an update in the announcement section as soon as the new agent is ready to go. Thanks, - Francis
  14. There aren't any other ranks for normal forum users.
  15. Francis

    白+黑樣本

    Hi Ryuusei, I'll be honest, I'm not completely sure if we do support this or not. I'll be looking into this however, and it's definitely a great idea if we don't already. Thanks, - Francis
  16. Hi Zurchiboy, Thanks for the input! Immunet is actually more diverse than you think though. Our Clam and TETRA engines are mostly signature based (TETRA having some extra rootkit detection to boot) but we also have our in-cloud ETHOS and SPERO engines which work off of fuzzy hashes and decisions trees, respectively. We also do a lot of extra work in the cloud by comparing data coming in from various computers at once in order to track how programs are spreading, what they're connecting to, etc... to see if they might indeed be malicious or not. We do all of this in the cloud so that your computer doesn't suffer the performance penalties itself, which is why you don't see any of these settings in the UI. Thanks, - Francis
  17. Hi Maurie, Sorry that our User Interface isn't as clear as it could be. Immunet is asking for your Windows Administrator username and password (don't worry, this is all local and we don't look at any of this information). This simply allows Immunet to run the scheduled scan even if your computer is currently logged out of its admin role. Thanks, - Francis
  18. Question: My Immunet console is displaying a message saying, "Disconnected" and the "Scan Now" and "Settings" buttons are greyed out. Clicking on the "Scan Now" button gives me the following error: How do I resolve this issue? Answer: Let me start with a brief explanation of what's going on. Immunet is mainly composed of two applications: agent.exe - the engine that handles connecting to the cloud and detections iptray.exe - the User Interface you see and interact with (aka the Immunet Console) The above issue occurs when something causes the connection between these two applications to be interrupted. This also means that even though you might see the disconnection message your agent might still be running and actively protecting you (you can check this by going into the Task Manager, you'll have to select the "show processes from all users" option if applicable, and locating the agent.exe; if it's there then it's probably running correctly). So, what can cause this interruption between the agent and the tray processes? 1) Logging in with multiple users. If you log into and try to open the Immunet Console in more than one profile on your computer, then multiple instances of the iptray.exe get instantiated and all try to connect to the agent.exe at once. Unfortunately, the agent.exe can only handle a single connection at a time. This is a known bug that has yet to be resolved, however, manually closing the iptray.exe processes from the Task Manager or just restarting your computer will fix the issue. 2) Corrupted configuration files. We have services running that stop other processes or users from tampering with our files, by things do go wrong on occasion. The way to clear out these files is to trigger a full uninstall of the application. You can start the uninstaller through Add or Remove Programs on Windows XP or through Programs and Features for Vista and 7. The entry is called Immunet 3.0. After the uninstaller completes, you will see the following message: Selecting the No option will tell Immunet to clean up all of the local configuration, policy, .db files and logs. This also means you will be erasing your quarantine history. After Immunet has finished uninstalling, re-install and the corrupted files will now have been replaced. 3) Firewalls. If your computer has a firewall (or multiple) it may be blocking our agent's connection to our cloud server. In order to make sure traffic is getting through, ensure that ports 53, 80, 443 and 32137 are all open. 4) Other Anti-Virus programs. It possible that another AV product has quarantined parts of our service. In order to stop this from happening, add an exclusion into these other AVs (if you're not sure how to setup an exclusion a quick Google search should help you out) for Immunet's program directory (by default at the location C:\Program Files\Immunet). 5) Oudated version. Make sure you're up to date with the latest version of Immunet. Many issues people experience with Immunet have already been addressed in it's latest version. Unfortunately for non-english users, our language pack builds are very far behind. This means that using one of the versions will still offer you the latest and up-to-date protection, but you will probably run into a lot more problems (like this one) as well as not being able to take advantage of our newest features. I regret to say that currently, our only workaround is to install the product in English.
  19. Hi Susan, I'm a little biased in this regard so I'd recommend googling it. If you're having difficulty finding anything useful cnet.com is a pretty good place to start. Thanks, - Francis
  20. Hi warp, The commands Ritchie posted will certainly do the trick; if the service is not found then it's not installed. If you'd like more details you can check the install logs by going to the temp directory (enter %TEMP% into any file browser) and looking for a file called "immpro_install.log". You can also send this file to support@immunet.com (also with a note referring to this forum thread) and we'll see if we can figure out what's going wrong. Thanks, - Francis
  21. Hi mpalka, Could you please gather the answers to the following questions and send them (along with a reference to this forum post) to support@immunet.com: 1) If you open the Immunet interface and hover over the About link on the bottom left, can you tell me what text is being displayed? 2) Do you run any other Firewall or Antivirus software on the server? 3) Do you by any chance have multiple users logging into your server and switching between different user accounts? 4) What version of windows are you running and is it 32-bit or 64-bit (you can find out by right-clicking on My Computer and selecting properties)? 5) Open the Task Manager (by pressing Ctrl+Alt+Delete), click on the Processes tab at the top, ensure that the "Show processes from all users" checkbox is checked and tell me if both agent.exe and iptray.exe are listed. 6) Could you do the following and send me a screenshot of the result: - Open the Start menu - In the search bar enter cmd - Right click on the search result cmd.exe and select Run as administrator - Enter the command: fltmc 7) Generate Support Diagnostics Report by doing the following: - Click Start -> All Programs -> Immunet 3.0 -> Support Diagnostics Tool - A new file will be created on your desktop with a name like Immunet_Support_Tool_[date andtimestamp].7z - Please email this file to me Thanks, - Francis
  22. Hi Ceb65, Yes, you are correct they are all remnants of past versions and Immunet does not need them. You can remove the Immunet Protect folder as well as the 3.0.0, 3.0.1 and 3.0.5 sub-folders in Immunet, however you'll have to open up your services and stop Immunet manually (or through the command line with net stop immunetprotect) delete the folders and then restart Immunet (net start immunetprotect) as we stop any user or program from tampering with our files while the service is running. Let us know if you have any other questions. Thanks, - Francis
  23. Ok, the first thing to try would be to install Immunet once more. When the DNS starts failling look in the Immunet Console at the quarantine list. If anything important is being quarantined simply restore it. You can then add whichever directory that contains that file to Immunet's exclusion list so it doesn't detect anything else that might be important to the inner workings of your DNS. Another thing you could try is to disable Blocking Mode as this security feature will slow all of your file accesses and your server requests may just be timing out. Let us know what you find out. Thanks.
  24. Hi Dionisy, I just want to make sure I understand you correct before I offer any suggestions: - You have a Windows 2003 machine configured as your DNS server - You had an older version of Immunet installed on the server and it was working - You updated Immunet and the DNS started failing - You restarted the DNS service and it started working again - You then removed Immunet, restarted the server and the DNS continued to work well - You re-installed Immunet and your DNS started failing again Are any of these points incorrect? Thanks.
  25. Hi JanTom, Sorry, but I'm not entirely sure what you're asking. If you're asking if Immunet is supported on 64-bit architectures then you can find all the requirements information by following this link. Please let me know if you meant something completely different. Thanks.
×
×
  • Create New...