dialup slow beyond words

when i first connect, things are relatively normal, but on later connects thru the day, things slow to like 15-20 mins (!) a page. i had faster speeds back in the days of acoustic couplers.

AV/AM all come up empty; HDD usage fairly low (20G used out of 80G); frag = 0%; "CPU usage" varies from 5% to 20%; 512M RAM as follows:

free physical - 50%
free pagefile - 80%
free virtual - 95%

[all per ASC]

i have no feel for "typical" RAM figures, but those sure don't look "pinned" to me!

in addition, speedfan gives me temps like:

HD0: 49c
Temp1: 72c
CPU: 67c

which seem high to me, but i've read in other threads here that anything under 80c is fine.

so what ELSE to look for? or how to systematically debug what's wrong with my dialup?

at this point i'm just GROPING. and 15-20 mins/page of groping AIN'T NO FUN....

*****
[EDIT]

turns out it's my NETZERO dialup only. juno works just fine. i mean, it's still dialup, but i can surf w/o 20 min GAPS before every page..

is anyone else using NZ? is it simply some problem on their end this week?

even the connect is slow. like 7-8 mins between "you are connected" to some homepage showing up!

NZ homepage/email etc working just fine if i'm already online, btw. i.e., if i use wifi or juno to connect, i can still get to NZ email via the web. which would lead me to think that the problem is *not* on their end.

but how can NZ dialup and juno dialup be so different right now?

of course, i've uninstalled and reinstalled my NZ dialer a gazillion times now. to no avail.

 

Control panel, then system, then hardware, then device manager, then click on ports, right click communication port hit properties and check the port settings. You should set it to its highest limit, you will need to reboot for it to take effect. If it is already set high not sure where to go from there!

 

You could pick a destination that's slow and TRACERT to it (assuming the destination is accepting ICMP traffic). Then compare that to the hops and responses to the same destination through Juno. That might tell you where your lag is.

 

wasn't there another reply here which listed two APPS to try? something to check port usage or something. why was that of all things deleted????

for the record, i don't have ports in my device manager. at least, not that i can find. is there an intermediary step/folder I should be looking thru?

nor do i see anything reading "COM2", "COM3" etc. FWIW.

not to say that my PC doesn't have these things, it's just that i'm unaware where/how they're represented.

oh, and...no clue how to "do a TRACERT"!! prithee tell!

 

again, where is the post with those 2 APPs to try? could the person who posted it the first time pls. do so again?

one was sumpin like "TCP/IP". the other i cannot recall.

TIA!

 

I don't recall seeing another post (but I could be wrong). TCP/IP are protocols rather than applications. Are you referring to comm ports or TCP ports? NETSTAT will tell you what TCP ports are open and/or listening. Was it TCPView that you are referring to? NETSTAT and TRACERT are Windows native commands...

TRACERT - http://kb.iu.edu/data/aihy.html
NETSTAT - http://commandwindows.com/netstat.htm
TCPView - http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx

Incidentally, attached is an image of what my comm ports look like in Device Manager.