I have had the same problem that showed up in my trouble shooting log. When I ran netstat -an I found that the wireless device was trying to connect to a black hole domain and not the ip address of my router. MSFT was managing the device and not the proset. I had to disconnect and reboot the router in order to have a normal ip address. It seems that somehow I must have a hacker inserting a OCX or DLL into the boot stream for the wireless router as the prowireless is starting in services BEFORE my Anti Virus. It appears that this might be an exploit by trying to connect to a public domain before it connects to my own router??????
Calla Lily
2 Intern
•
243 Posts
0
July 21st, 2007 05:00
rudibduddy
54 Posts
0
May 11th, 2009 08:00
I have had the same problem that showed up in my trouble shooting log. When I ran netstat -an I found that the wireless device was trying to connect to a black hole domain and not the ip address of my router. MSFT was managing the device and not the proset. I had to disconnect and reboot the router in order to have a normal ip address. It seems that somehow I must have a hacker inserting a OCX or DLL into the boot stream for the wireless router as the prowireless is starting in services BEFORE my Anti Virus. It appears that this might be an exploit by trying to connect to a public domain before it connects to my own router??????