I have encountered a virus on three systems in our office it appears to be a new varation of the Gaobot blaster.exe trojan. Its called Penis.exe. I was able to finally get two of the three back up by deleting the files manually and then deleting the registry keys as well. However the third system when booting up after login takes approx 30 mins to get a desktop and after that any program you try to open takes approx 10 mins or longer to work. Any suggestions on something I am missing? Has anyone else encountered this virus? Sad part is after working for over 5 hours with Symantec they were clueless to this new varation and unable to offer any real assistance other than reformat harddrive. Thanks for the help.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Extreme slowness booting after virus repair
- Thread starter FHWA
- Start date
- Thread starter
- #3
- Thread starter
- #5
I'm not using DNS on these three systems they are setup as Peer to Peer Network under XP PRO on a local workgroup called MSHOME.... so DNS should not be an issue should it??? I feel that somehow configuration settings have been lost hence the login password and then waiting for loading of personal settings just hangs for 30 mins or less. But that would not explain the slowness issue just opening programs once Xp finally loads to desktop. I did not want to but guess I will have to do a full reformat of hard drive and new install....
Okay, lots of things going on, and they are interdpendent.
1. There is an issue with your Winsock service. The WinsockFix utility I linked above should have cleared any issues except in the instance that some of your required services are not running.
. Click Start, select Run, and type C:\WINDOWS\INF in the textbox.
. Click OK.
. Locate the Nettcpip.inf file.
. Right-click the file Nettcpip.inf and select Install from the menu.
Reboot.
2. There are some odd things that can interfere with DHCP services on a machine.
. Check that NAV is not a problem:
. Check that "hidden" firewall components are not an issue. PC-Illan, for example, will create this if you use standard default settings for the installation. Other antivirus programs can do the same thing. "Disabling" firewall products such as ZoneAlarm, Sygate and Norton is not enough to prevent issues. Either uninstall or set them up so that your local LAN is a Trusted Zone for all traffic and all traffic types.
3. I want you to carefully check that the NTFS permissions, (not the Windows Share settings), make the folders available for your LAN users. Steve Winograd has a great checklist, do not skip any steps:
4. If still no joy, re-run the WinsockFix utility.
5. If still no joy, replace the network adapter, or update the drivers for the existing one.
6. Consider again both choices from #5 above. It might be a bad NIC.
7. I still no joy, I would to an in-place repair installation of XP:
1. There is an issue with your Winsock service. The WinsockFix utility I linked above should have cleared any issues except in the instance that some of your required services are not running.
. Click Start, select Run, and type C:\WINDOWS\INF in the textbox.
. Click OK.
. Locate the Nettcpip.inf file.
. Right-click the file Nettcpip.inf and select Install from the menu.
Reboot.
2. There are some odd things that can interfere with DHCP services on a machine.
. Check that NAV is not a problem:
. Check that "hidden" firewall components are not an issue. PC-Illan, for example, will create this if you use standard default settings for the installation. Other antivirus programs can do the same thing. "Disabling" firewall products such as ZoneAlarm, Sygate and Norton is not enough to prevent issues. Either uninstall or set them up so that your local LAN is a Trusted Zone for all traffic and all traffic types.
3. I want you to carefully check that the NTFS permissions, (not the Windows Share settings), make the folders available for your LAN users. Steve Winograd has a great checklist, do not skip any steps:
4. If still no joy, re-run the WinsockFix utility.
5. If still no joy, replace the network adapter, or update the drivers for the existing one.
6. Consider again both choices from #5 above. It might be a bad NIC.
7. I still no joy, I would to an in-place repair installation of XP:
- Status
Similar threads
- Locked
- Question
