New
#1
Stopping automatic wireless connection- Possible issue aft online help
By remotely accessing my computer, Microsoft Consumer Security Support just helped rid my computer of the Win64/Sirefef & Win64/Sirefef.AA trojans, which caused Windows Firewall and Windows Security Center to shut down and be unable to start again. After the virus was removed, I returned to using Comodo Internet Security Premium (which has antivirus, defense+ and a firewall), which I've had for the past 9 months.
Normally I boot up with my ethernet cable in my computer, unless I'm out at a cafe working.
Here's the problem: When I rebooted a 2nd time without my ethernet, my Comodo firewall came up with a New Network Detected message showing a Wired IP address & saying that "your computer has joined a new network," asking if I'm in a home, work or public place.
I've seen notices that wireless networks are available, and a list of them was provided if you choose to look, but I've never been automatically connected to one, even in the many dozens of times I've been to cafes & hotspots.
a) I want to know how to make sure this doesn't happen again. It's surprising to me there seems to be no easy "do not automatically connect to wireless networks" switch on Win7 Home Premium. The instructions I've seen online seem to be to go to Control Panel\Network and Internet\Manage Wireless Networks, right click to get Properties on each of the 6 shown and uncheck the "Connect automatically..." box from each...
...but does this prevent automatic connections from new wireless networks when you move your computer? or are the 6 on the list the "first 6" Windows is set to go through before connecting to any wireless network, meaning it wouldn't line up a new one in a new area?
b) I want to know if the trojan, or Microsoft's remote access program, or the online 3rd party "ESET online scanner" they used in the fix, somehow made wireless automatically available. Perhaps part of one of their programs put the identified wireless network at the top of that list for a bit. (No unsecured networks are among the 6 on that list now, but others are available when I click the Wireless Network Connection tab. Not sure which one, if any, matches the IP address that came up)
When Microsoft called back, they ran two programs: netsh int ip reset resetlog.txt (to reset the tcp/ip) and ipconfig /flushdns (to reset/clear my website history) as a fix, and no automatic connection happened the next time I rebooted. Maybe that fix was permanent, but I want to be sure - any thoughts out there?
Here was the original thread:
www.sevenforums.com/system-security/241340-windows-firewall-windows-security-center-cant-started.html