I've seen this behavior for months. It's real. The steps listed in the article (firewall, "Infrastructure Only", etc.) are sufficient to nullify this flaw.
~Jeff Has anyone tested this out? If so, what are you thinking about doing to prevent it? http://blogs.washingtonpost.com/securityfix/2006/01/windows_feature.html I'm trying to see if I can get my test machine to do it--incidentally I have noticed two ad-hoc networks these last two days. (One has a (1) appended to it--not sure what is adding the one). Kind Regards Murad Talukdar --------------------------------------------------------------------------- --------------------------------------------------------------------------- --------------------------------------------------------------------------- ---------------------------------------------------------------------------
