The only way we have found to get it to run is by taking the customer's machine out from behind the firewall (done this on 3 machines so far). We have a machine running m0n0wall sitting between the switches that the customers' machines connect to and the internet. It has very stringent rules, allowing only ports 53 (DNS), 80 (HTTP), 443 (Secure HTTP), 21 (FTP), and 5722 (Jabber) outgoing.
We have also tried disconnecting the machines from the internet completely before running ComboFix, but that doesn't work either. This is odd, since ComboFix used to run just fine without an internet connection, usually in a reduced mode because the Windows Recovery Console isn't installed.
I found a version of ComboFix we downloaded 11/14/09 at 11:10am EST, and it runs OK right now (tested on 1 machine still behind the firewall).
Would anyone know if ComboFix was recently updated in a way that would cause this error if the computer has no or heavily firewalled internet connectivity?

Help
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.
This topic is locked

Back to top










