• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Home Network Painfully Slow (On 1 Computer Only)

This is it in a nutshell...

After some major hardware upgrades and swapping, I have a 4 computer home network. All computers run WIN98. One computer (mine) is painfully slow in accessing the network. Once the file is finally located, and the coping is ready to start, the file transfer takes place quickly. The time it takes to open "Network Neighborhood" and to finally be ready to copy a file is as much as 2 minutes!

Things I have tried: Deleting and reloading all network adapters, services, and protocols; switching out the router to an old hub I had; messing with IRQ's in the BIOS; deleting, and finally reinstalling Sygate (sharing a 56K modem on one of the other computers).

The computer that is slow is an Athlon 1700+XP, 40G HD, ASUS A7V133A, burner, CD-ROM, GeForce II video, scanner, web cam, SB Live Value.

Has anybody had this problem and found the fix?

TIA
 
Sounds like a name resolution protocol. Go into the Network Control Panel on all the machines and make sure you've got all the same protocols installed. Also, go into each protocol, go to the "advanced" tab and make sure that they all have a checkbox on the "set this as the default protocol" box checked on the SAME protocol. IE, is one using NetBEUI and one TCP/IP as their default?

In general, I'd use NetBEUI as the default protocol everywhere. Should take care of your problem.

- G
 
Well, I tried what you suggested, and a whole bunch of other things, and this is what I found.

1. Setting the default protocol didn't do much of anything. Only when I used NETBUI alone (with TCP/IP removed) did the speed improve, but only a tiny bit.

2. I began getting all sorts of shutdown delays and errors while I was screwing around with this. One thing that got me particularly curious was a program called "AcebotMainThread" that wouldn't shut down normally. Funny thing was that I couldn't find this program anywhere when doing a search for it on the HD. Google search didn't come up with anything either. Hmmmm....

3. I was finally able to get speed by mapping the drives on the 4 computer network (using the Sygate resource). Now it runs great.

I am coming to the realization that something is major screwed up with this computer. I recently changed drivers on the Promise controller (ATA100) due to the "Volume Mounting Bug". Could this be causing the problem?

Why "Network Neighborhood" runs so slow is still a total mystery.
 


<< One thing that got me particularly curious was a program called "AcebotMainThread" that wouldn't shut down normally. >>

Ask Jeeves turned up a few things for "Acebot"

* AceBot MetaTag Generator from TUCOWS
* Quake 2 ACEbot by Steve Yeager
* One reference to an IRC channel

If either of the 1st two ring a bell, then you can check those out.
If not, I'd make sure that machine doesn't have an IRC zombie 'bot on it somehow.

WICKED stuff, BTW...
 
Back
Top