Slow LAN/Internet

[medicnick83]

I have a Windows 2000 PC here giving me a interesting problem.

The computer itself is very fast, but when you try browse the internet, or the LAN, then it's horribly slow, slow as in, if you goto any web site, it'll never come up however, it does find it, says it's loading, but nothing happens.

When you browse the LAN, things happen, but huge gaps of long waiting sessions happen - I tried to copy a 120MB file and it said it was going to take 70 minutes!

The problem seems to centre around any 'traffic' on either the LAN or INTERNET.

I've scanned for viruses and removed the 3 that were on.
I've updated 2000 to Service Pack 4.
I've tried a different network card.
I've uninstalled alot of programs that didn't need to be on.
I've reset Firefox and IE to defaults.
I've tried SMITFraud fix thingy.

I've even tried Googling, but can't seem to find a scenario that matches mine for a solution.

Any other ideas?

Oh, if we ping say, something local, it comes back with <10ms replies and if I ping say 196.25.1.1 then it comes back with ± <20ms replies.

 

[Aghori]

Maybe an os repair from the windows disc?

 

[Cadavre777]

This may sound stupid, but have you thought about changing the ethernet cable (and keystone jack if applicable)? Is the cable sheilded or unshielded, running parallel (of more than a couple meters) to power cables, any kinks or twists in the cable?

Any or possibly all of these can be the cause of your problem.

 

[medicnick83]

I eventually fixed the problem, and it's not the cable etc.

For some reason (according to sources) this problem happened alot in Windows 2000.

What I did was take the network card's speed off "AUTO" and force the mode onto whatever, in this case, I put it on 100/HALF and it worked. 10/HALF also worked.

I would like to know why this happened, so as to better understand the problem.

But ya, the forcing the speed fixed the problem.

 

[Happy Camper]

Windows is what happened

 

[syntax]

I eventually fixed the problem, and it's not the cable etc.

For some reason (according to sources) this problem happened alot in Windows 2000.

What I did was take the network card's speed off "AUTO" and force the mode onto whatever, in this case, I put it on 100/HALF and it worked. 10/HALF also worked.

I would like to know why this happened, so as to better understand the problem.

But ya, the forcing the speed fixed the problem.

Firstly, dont put it on 100/half.....in fact, in todays world you should never really need half duplex...make it full...

As to why this happened, probably the autonegotiation software sucks...its a common thing, even some rather large name brand switching and routing manufacturing companies cant get autonegotiate to work between two of their own products so rather just set it yourself....

 

[Asha'man X]

I've heard of this happening with some switches who didn't auto negotiate speed properly with the NIC. Setting things to half duplex works but can cause slowness in the future.

 

[medicnick83]

Well, funny enough, I went back to the client this morning, changed from HALF to Auto and it worked again... they connect direct to a very new Telkom ADSL modem.

Strange indeed!

 

[wetkit]

"Telkom ADSL modem" says it all