Cain And Abel Fucked Up My Friends Net Connection

[1337n00b]

My friend installed Cain and Abel on his desktop machine with XP Pro. After he ran a couple of scans, his computer froze and then crashed. When he rebooted, his net connection wasn't working. It just said "limited or no activity".

Any suggestions?

[Sparda]

Uninstall winPcap. Additionally, (assuming a router was used) some routers are stupid and very vulnerable to remote DoS attacks (i.e. crashing) even when no 'questionable*' traffic is sent to it. Try reseting the router, if this fails try factory reset.

*questionable been a blurry definition of course

[digip]

What kind of scan were you doing? Were you trying to use LSA Secrets to dump the passwords from lsass? Because I have noticed that since the last few Microsoft Updates, it will cause lsass.exe to crash and windows will be forced to reboot afterwards. About the only good thing Cain is good for is a MITM attack and dumping the protected storage for email passowrds.

[thisiam]

from the times i have seen limited or no connectivity it has been solved by one of the following or all.

1.reset router and or modem

2.release and and after modem/router are back then renew your IP

3.still not able to get online and not getting the proper IP  check out the following http://support.microsoft.com/kb/299357

4.uninstall your NIC

5.call your ISP and ask them to re provision your cable/DSL modem

worked for me.

[digip]

My friend installed Cain and Abel on his desktop machine with XP Pro. After he ran a couple of scans, his computer froze and then crashed. When he rebooted, his net connection wasn't working. It just said "limited or no activity".

Any suggestions?

Let me ask you a dumb question. Were you trying this scan on an ethernet connection and not wireless. And was it against a pc in your own lan? That will cause problems in getting logged back on as the arp gets all wacked because your router is tied tied directly to your conenction on the inernal lan. When doing this on a wireless connection you stand in the middle, but on an ethernet connection with your own router, it causes problems and may even cause other computers to point to you even after you reboot and will cause a sort of DOS attack against yourself, flooding you with packets your not looking for from their pc.

You can clear the arp cache to make sure, but might need to do it on any of the other pc's connected to your router(assuming you did it on your local lan and your using windows xp):

in windows XP goto start/run/ and enter the following: netsh interface ip delete arpcache

Then open a command window and type: arp -a

That should show no entries.

Then reboot and try and log onto the router. If you can see the router, then you should be ok. If not, you may need to reset the router, like in previous statements, but if you did that first and it still didn't work, try resetting the arp cache then the router, then reboot.