No matter what networks interface I use, DHCP just doesn't want to work, the interface will just sit there sending and receiving DHCP traffic but nothing gets configured and I get "limited connectivity"
I've already done:
System Restore
Registry Restore
Checked Windows Firewall to see if DHCP is blocked
Reinstalled wireless driver (this was before I realized that all interfaces were affected)
The only things I remember that could have caused it were Windows Update or Bleachbit, those were the two things that I ran before restarting right before the problem started
>>58296838
Disable the Base Filtering Engine service and reboot. If that fixes it, you screwed up the Windows Firewall.
Also, make sure you didn't disable the DHCP service.
Finally, are you sure DHCP isn't working? Just because it says "limited connectivity" doesn't mean that DHCP is dead, it just means Windows can't connect to Microsoft to verify you're online.
>>58296838
A trojan is incrementally replacing files in your OS. Quit be an insensitive prick and let the man work.
>>58296838
run msinfo32, click components, network -- what do you have listed for protocols?
>>58296838
Reset winsock
Look it up
Are you getting a 169. IP? Also. Check your DNS settings
>>58296838
I know exactly whats going on here..
Something happened. (something happened).
See if it's actually a problem with DHCP or if it's just a problem with Windows
Boot into a Linux CD and see if you can get a DHCP Address
>>58297526
Second this.
Netsh windsock reset catalog.
Netsh int TCP reset
Netsh int ipv4 reset. Thank us later
>>58297735
That's the thing my interface settings are all set to automatic
>>58298564
Thanks, I'll try this when I get home
>>58298560
I've already done this, so I narrowed it down to Windows 7 being the problem