jbonner Posted November 26, 2012 Report Share Posted November 26, 2012 I'm unable to scan. The "scan now" button is grayed out, when I click it I get the message : The sourcefire agent can not connect to the internet. Please ensure your computer is connected to the internet and rety. Since I'm posting, I am connected obviously. I uninstalled, rebooted, then reinstalled latest version, same effect. I did a wireshark trace and I see port 32137 traffic going out to 107.22.2.73 & 50.17.62.228. I see the three way handshake, and then some retransmits, then the remote end RST's the connection. Seems like an issue with the remote servers. agent.exe is running, I've stopped and restarted the service with no effect. Link to comment Share on other sites More sharing options...
ritchie58 Posted November 26, 2012 Report Share Posted November 26, 2012 The first thing to check is make sure that agent.exe and iptray.exe have internet access and is not being blocked by anything, such as your firewall or other 3rd party security software (another AV, behavior blocker, H.I.P.S. program, etc...). If you're sure nothing is blocking these processes you can also try to relaunch iptray.exe manually by right clicking on the System Tray Icon and choose Hide Tray Icon. Then relaunch the GUI using the Desktop or All Programs Icon. You can also use CMD commands. Type: net stop immunetprotect wait about 10 seconds, then type: net start immunetprotect There is something else that can cause this behavior too. If you were to switch user accounts (for instance, going from Administrator to a Guest account) without rebooting the system, or using "Fast User Switching" as it's called, this will cause two process instances of iptray.exe to be launched. Only one instance of iptray.exe (the GUI) can interact with agent.exe. If you want to switch users it's important to do a reboot or use Task Manager and kill iptray.exe for the account that's not being used afterwards as Fast User Switching is not supported at this time. If you're using a Proxy service go into Settings and click on Proxy Settings and make sure that Immunet is auto detecting your Proxy server (Proxy service is supported for 3.0.8 & 3.0.6 builds only). If you continue to experience issues could you please submit a SDT Report directly to Support. Info on how to create and submit a SDT Report can be found at this forum link. http://forum.immunet...ic-tool-report/ Best wishes, Ritchie... Link to comment Share on other sites More sharing options...
chen Posted November 26, 2012 Report Share Posted November 26, 2012 The first thing to check is make sure that agent.exe and iptray.exe have internet access and is not being blocked by anything, such as your firewall or other 3rd party security software (another AV, behavior blocker, H.I.P.S. program, etc...). If you're sure nothing is blocking these processes you can also try to relaunch iptray.exe manually by right clicking on the System Tray Icon and choose Hide Tray Icon. Then relaunch the GUI using the Desktop or All Programs Icon. You can also use CMD commands. Type: net stop immunetprotect wait about 10 seconds, then type: net start immunetprotect There is something else that can cause this behavior too. If you were to switch user accounts (for instance, going from Administrator to a Guest account) without rebooting the system, or using "Fast User Switching" as it's called, this will cause two process instances of iptray.exe to be launched. Only one instance of iptray.exe (the GUI) can interact with agent.exe. If you want to switch users it's important to do a reboot or use Task Manager and kill iptray.exe for the account that's not being used afterwards as Fast User Switching is not supported at this time. If you're using a Proxy service go into Settings and click on Proxy Settings and make sure that Immunet is auto detecting your Proxy server (Proxy service is supported for 3.0.8 & 3.0.6 builds only). If you continue to experience issues could you please submit a SDT Report directly to Support. Info on how to create and submit a SDT Report can be found at this forum link. http://forum.immunet...ic-tool-report/ Best wishes, Ritchie... hi ritchie58 107.22.2.73 and 50.17.62.228,Please ritchie58 use the ping command to test immunet in amazonaws Ec2 server, 107.22.2.73 and 50.17.62.228 presence or absence of response. Link to comment Share on other sites More sharing options...
ritchie58 Posted November 26, 2012 Report Share Posted November 26, 2012 Immunet does use the Amazon servers for such things as product updates pushed through the GUI and the bootstrapper installers to reduce the workload on the Immunet cloud servers. This is normal. If you are using some 3rd party software firewalls or if your modem or router has a built in hardware firewall it may be necessary to manually configure port access for Immunet. More info on that can be found at this link. http://forum.immunet...-your-firewall/ Link to comment Share on other sites More sharing options...
nwarshawski@sourcefire.com Posted November 26, 2012 Report Share Posted November 26, 2012 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! Link to comment Share on other sites More sharing options...
jbonner Posted November 27, 2012 Author Report Share Posted November 27, 2012 Confirmed, everything is working now. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.