slow pc after networking

  • Thread starter Thread starter Ashley Laybutt
  • Start date Start date
A

Ashley Laybutt

Hi
I have a new Athlon PC running XP pro. The machine was
running like a dream until I tried setting up a wireless
network to an old P3/450 running W98SE. Now my computer
is running as slow as a commodore 64. I have disabled the
network and performed a system restore to a date before
the networking was commenced, but it still takes forever
to do ANYTHING. I have 38 processes running in the
windows task manager window. PLEASE HELP
 
Hi
I have a new Athlon PC running XP pro. The machine was
running like a dream until I tried setting up a wireless
network to an old P3/450 running W98SE. Now my computer
is running as slow as a commodore 64. I have disabled the
network and performed a system restore to a date before
the networking was commenced, but it still takes forever
to do ANYTHING. I have 38 processes running in the
windows task manager window. PLEASE HELP
Click to expand...

Ashley,

Do you know what those 38 processes are?

How well did you protect your wireless LAN? Recommended precautions:

Enable WEP / WPA. Use non-trivial values for each. (No "My dog has fleas").
Enable MAC filtering.
Disable DHCP, and assign an address to each computer manually.
Don't disable SSID broadcast. But change the SSID itself - to something that
doesn't identify you, or the equipment.
Enable the router activity log. Examine it regularly. Know what each
connection listed represents - you? a neighbor?.
Install a software firewall on every computer connected to a wireless LAN. Put
manually assigned ip addresses in the Local (highly trusted) Zone. Open the
following ports for file sharing only in the Local Zone: TCP 139, 445; UDP 137,
138, 445.
Use non-trivial userids and passwords on every computer connected to a wireless
LAN. Disable or delete Administrator and Guest userids.
Stay educated - know what the threats are. Newsgroups alt.internet.wireless and
microsoft.public.windows.networking,wireless are good places to start.

This very well be a spyware problem.

Start by downloading LSP-Fix from <http://www.cexx.org/lspfix.htm>, and
CWShredder from <http://www.majorgeeks.com/download4086.html>.

First, run CWShredder.

Now check for, and remove, spyware. Get HijackThis
<http://www.majorgeeks.com/download.php?det=3155> and Spybot S&D
<http://security.kolla.de/index.php?lang=en&page=download>.
1) Install and run Spybot. First update it ("Search for updates"), then run a
scan ("Check for problems"). Trust Spybot, and make all recommended deletions.
2) Install and run HijackThis. Do NOT make any changes immediately. Save the
Log.
3) Have your HJT log interpreted by experts at one or more of the following
forums (and post it here):
<http://forums.tomcoyote.org/>
<http://63.247.79.145/~coyote/forums/>
<http://www.wilderssecurity.com/>
<http://forums.net-integration.net/>
<http://www.spywareinfo.com/forums/>

If removal of any spyware affects your ability to access the internet (some
spyware builds itself into the network software, and its removal may damage your
network), run LSP-Fix.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
Hi Chuck
the following are the processes that are running
iexplore.exe, taskmgr.exe, ocrawr32.exe, svchost.exe
(appears a few times), nopdb.exe, ticicon.exe,
hgcctl95.exe, nvsvc32.exe, nprotect.exe, navapsvc.exe,
incdsrv.exe, alg.exe, ccevtmgr.exe, spoolsv.exe,
explorer.exe, iconmgr.exe, wcescomm.exe, rundll32.exe,
msmsgs.exe, isass.exe, services.exe, winlogon.exe,
csrss.exe, netgearag.exe, smss.exe, soundman.exe,
incd.exe, ccapp.exe, wowexec.exe, winoldap.mod,
ocraware.exe, ntvdm.exe, system, system idle process. I
really appreciate your help

Ash

-----Original Message-----


Ashley,

Do you know what those 38 processes are?

How well did you protect your wireless LAN? Recommended precautions:

Enable WEP / WPA. Use non-trivial values for each. (No "My dog has fleas").
Enable MAC filtering.
Disable DHCP, and assign an address to each computer manually.
Don't disable SSID broadcast. But change the SSID itself - to something that
doesn't identify you, or the equipment.
Enable the router activity log. Examine it regularly. Know what each
connection listed represents - you? a neighbor?.
Install a software firewall on every computer connected to a wireless LAN. Put
manually assigned ip addresses in the Local (highly trusted) Zone. Open the
following ports for file sharing only in the Local Zone: TCP 139, 445; UDP 137,
138, 445.
Use non-trivial userids and passwords on every computer connected to a wireless
LAN. Disable or delete Administrator and Guest userids.
Stay educated - know what the threats are. Newsgroups alt.internet.wireless and
microsoft.public.windows.networking,wireless are good places to start.

This very well be a spyware problem.

Start by downloading LSP-Fix from
Click to expand...
 
Hi Chuck
the following are the processes that are running
iexplore.exe, taskmgr.exe, ocrawr32.exe, svchost.exe
(appears a few times), nopdb.exe, ticicon.exe,
hgcctl95.exe, nvsvc32.exe, nprotect.exe, navapsvc.exe,
incdsrv.exe, alg.exe, ccevtmgr.exe, spoolsv.exe,
explorer.exe, iconmgr.exe, wcescomm.exe, rundll32.exe,
msmsgs.exe, isass.exe, services.exe, winlogon.exe,
csrss.exe, netgearag.exe, smss.exe, soundman.exe,
incd.exe, ccapp.exe, wowexec.exe, winoldap.mod,
ocraware.exe, ntvdm.exe, system, system idle process. I
really appreciate your help

Ash
Click to expand...

Ash,

Instead of listing each process like that, how about you try a HijackThis log
(see instructions below) which is easier to work with.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
Back
Top