Windows xp will only connect to the internet in safe mode w/ networking
 

I've checked the router and modem, tried disabling norton 360, did a rootkit scan and system scan, got zeroaccess out of there, but still no dice.

WTF? any help from the gurus would be appreciated.

so...

Are you trying to get it to connect to the internet in normal mode? Are there other things it's not doing properly? Presuming this *is* the case, what is it doing when you start normally? What kinds of errors are being reported?

Did you try the following?
 

Open up a Command Prompt (start -> all programs -> accessories -> command prompt) and enter in the following:

netsh winsock reset

hit enter after that.

That resets the network stack.

That reset the network stack, but still no connection.
I get
"Windows could not finish repairing the problem because the following action cannot be completed: Renewing your IP address"

Checked network adapters
did a few safemode system restores to a week ago, and ran NPE,

I'm not seeing tcp/ipv4. I'm only seeing tcp/ipv6 and tcp/ip. not sure if that is relevant.

can you run ipconfig /all from safe mode?
 

Can you run ipconfig /all from a command prompt in safe mode and tell me the IP?

IP address 0.0.0.0
subnet mask 0.0.0.0
IP Address fe::213:72ff:fec4:99c2%4

I ran ipconfig last night as administrator and got this variant

fe::213:72ff:fec4:99c2%5



I managed to remove zeroaccess!inf2 and zeroaccess!kmem, and reinstalled all my drivers. I first tried to drag the file (netbt.sys) into the trash, but it would re-appear seconds later. I tried over writing it and the same thing would happen. I tried delete on boot and it would be back. finally, I managed to remove it and as far as I could tell all its friends while in safe mode. I ran norton scan again and it showed up as all clean, I used search everything to check the drives and none of the files remained. it seems all clear now as far as zeroaccess is concerned.

Still having connectivity issues though.

Also still getting the can't connect to RPC, I went an made sure autoconnect was checked.

What happens when you try this in Safe Mode:
From the command prompt type:
ipconfig /renew then hit enter
ipconfig /flushdns then hit enter


Also, are using a dynamic (supplied by your ISP and changes every time you restart your machine) or a static (always the same, all the time) configuration for your IP?

nothing except >
Windows IP Configuration.

lately when I have been using cmd prompt nothing at all has been happening...

I'm about to try a system repair.

Do not change anything until important facts are obtained. Fixing without identifying the problem can exponentially complicate the problem.

ISO defines three relevant layers of communication. Start by defining what is happening at the lowest level (especially since IPCONFIG reported that as a potential defect).

An ethernet cable terminates at the computer and at the router. On the computer receptacle should be some lights. As the cord is disconnected, what happens to those lights. Repeat the same test on the router end. These lights will be on the front panel. Report those lights (and router model).

NIC's computer must talk with the router's computer. Those lights are reporting a conversation that you otherwise never see or know about. Are NIC and router computers talking? Do they talk both in Safe modem and when booted normally?

Next, go to Device Manager (obtained via Computer Management or Control Panel or Help). What is reported for the Network Adapters?

Do not try to change drivers by deleting software. First delete the device in Device Manager. And reboot. Or use Device Manager to Update Driver. But do not do that yet. First collect facts.

Helpful would be the manufacturer and model of that computer. Some manufacturers provide comprehensive hardware diagnostics to immediately solve such problems without all this sweat and confusion. Since Windows only tries to work around problems. But diagnostics seek to identify hardware problems even before you know the problem exists.

A diagnostic may also be available from the NIC manufacturer.

All this is about defining the first layer as good or bad. If the NIC appears good, then go back to Device Manager to update what should have been a perfectly good driver. Reboot. And report back what IPCONFIG /ALL reports.

I went out on a limb and just did a system repair and now everything is fine and the machine is running as fast as lighting.

Thanks for everyone's input and help.

fuck zeroaccess

Who / what is zeroaccess?

a Trojan of some note. Wiki has a good primer on it.

Good grief.

more

Good grief is right. Any word on whether Macs are affected?