I can’t upload, need help

[TLAM Strike]

I just switched ISPs from AOL to the local phone company and all of a sudden I can’t upload files with my new ISP. Its a dial up connection. Is it something to do with my new connection? Is my ISP just cheap? Is there anything I can do?

I tryed lots of diffrent image upload and file upload sites they just stop loading even with very small files. AOL still uploads fine.

:damn: :damn: :damn: :damn:

[sonar732]

A few questions TLAM,

1. Can you download just fine?
2. Are you having any sort of connection/disconnect issues?
3. Do a tracert of the ip address you are sending to so that you can make sure that you have a "clean shot" to the ip address.
4. If you do have connection/disconnect problems, have a line test done. The littlest bit of noise on the telephone line will cause problems.

[TLAM Strike]

1) I can download just fine. It slows down near the end of large DLs though
2) Nope.
3) Ummm how?

[sonar732]

Start-Run-command/cmd (depends on OS).

type 'tracert www.insertaddress.com'

If you have XP, you can perform 'pathping www.insertaddress.com'

[TLAM Strike]

OK I traced a route to http://www.imageshack.us/ and this is what I found:

Generated by www.DNSstuff.com at 02:11:27 GMT on 26 Feb 2006.
Hop T1 T2 T3 Best Graph IP Hostname Dist TTL Ctry Time
1 0 0 0 0.5 ms
66.36.240.2 AS14361
HOPONE-DCA c-vl102-d1.acc.dca2.hopone.net. 255 US Unknown: 83c3f817
2 0 3 0 0.8 ms [+0ms]
66.36.224.249 AS0
IANA-RSVD-0 gec3.core2.dca2.hopone.net. 0 miles [+0] 254 US Unix: 1:10:05.468
3 1 7 5 1.5 ms [+0ms]
66.36.224.185 AS0
IANA-RSVD-0 iar2-ge-2-0-0.washington.savvis.net. 0 miles [+0] 252 US Unix: 2:11:33.396
4 61 1 2 1.9 ms [+0ms]
206.24.226.97 AS3561
SAVVIS bcs1-loopback.washington.savvis.net. 0 miles [+0] 252 US Unix: 2:11:33.473
5 2 2 2 2.6 ms [+0ms]
206.24.227.122 AS3561
SAVVIS dhr4-pos-1-0.weehawkennj2.savvis.net. 0 miles [+0] 251 US Unix: 2:11:33.420
6 1124 109 93 4.2 ms [+1ms]
208.173.10.182 AS3561
SAVVIS [Missing reverse DNS entry] 0 miles [+0] 250 US [Router did not respond]
7 8 4 4 4.2 ms [+0ms]
154.54.2.201 AS174
COGENT p11-0.core01.dca01.atlas.cogentco.com. -1 miles [+0] 0 miles [+0] 249 US [Router did not respond]
8 46 43 45 43 ms [+39ms]
66.28.4.90 AS174
COGENT p3-0.core01.iah01.atlas.cogentco.com. -1 miles [+0] 0 miles [+0] 244 US [Router did not respond]
9 74 73 73 73 ms [+30ms]
66.28.4.6 AS174
COGENT p14-0.core01.san01.atlas.cogentco.com. -1 miles [+0] 0 miles [+0] 243 US [Router did not respond]
10 77 75 74 74 ms [+1ms]
66.28.4.230 AS174
COGENT p4-0.core02.lax02.atlas.cogentco.com. -1 miles [+0] 0 miles [+0] 245 US [Router did not respond]
11 78 112 114 76 ms [+1ms]
38.112.36.250 AS174
COGENT g5-2.hc01.lax02.atlas.cogentco.com. -1 miles [+0] 0 miles [+0] 243 US Unix: 2:11:34.994
12 206 78 76 76 ms [+0ms]
38.101.111.36 AS174
COGENT
[Reached Destination]www.imageshack.us [No PTR] 52 US Unix: 2:11:34.996
13
14
15

Analysis:
Number of hops: 12
Last hop responding to ICMP: 12, UDP: 12, TCP: 12.
I did not detect any firewalls that are blocking ICMP, unwanted UDP, or unwanted TCP packets.

Legend:
T1/T2/T3 are the round-trip times in milliseconds (1/1000ths of a second).
T1 uses a proper ICMP-based tracert (Microsoft style). T2 uses a UDP-based traceroute (Unix-style). T3 uses a TCP-based traceroute (port 80).
Since many ISPs now block ICMP and/or packets to unknown ports, T3 (not used by many traceroute programs) typically shows the best results.
Best times may be theoretical (if it takes 80ms to hop 10, and 50ms to hop 11, we say the best time for hop 10 is 50ms).
If no reverse DNS entry is given for an IP, we display 'unknown.example.com' if the domain name is known.

[sonar732]

Don't go by DNSstuff.com, I did both and the numbers are quite different.

My tracert from command line...


1 <1 ms <1 ms <1 ms 192.168.0.1
2 53 ms 55 ms 35 ms adsl-65-42-108-254.dsl.peoril.ameritech.net [65.
42.108.254]
3 12 ms 13 ms 14 ms dist1-vlan50.peoril.ameritech.net [66.73.155.226
]
4 25 ms 26 ms 25 ms bb1-gig2-0.peoril.sbcglobal.net [66.73.155.103]

5 18 ms 17 ms 17 ms bb1-p9-2.chcgil.sbcglobal.net [151.164.240.148]

6 18 ms 15 ms 15 ms bb2-p5-1.chcgil.ameritech.net [151.164.191.182]

7 18 ms 18 ms 19 ms ex1-p0-0.eqchil.sbcglobal.net [151.164.42.147]
8 18 ms 16 ms 15 ms ge-3-0-1.edge2.Chicago1.Level3.net [4.68.127.225
]
9 22 ms 24 ms 19 ms ae-2-54.bbr2.Chicago1.Level3.net [4.68.101.97]
10 59 ms 60 ms 59 ms as-0-0.mp2.Tampa1.Level3.net [209.247.11.198]
11 60 ms 60 ms 61 ms ae-13-53.car3.Tampa1.Level3.net [4.68.104.75]
12 61 ms 64 ms 58 ms 4.79.172.2
13 59 ms 58 ms 65 ms GigE3.ds05a.tpa.sagonet.net [65.110.32.74]
14 84 ms 65 ms 59 ms unknown.sagonet.net [207.150.190.52]

DNSstuff tracert...

1 0 0 0 0.5 ms

66.36.240.2 AS14361
HOPONE-DCA c-vl102-d1.acc.dca2.hopone.net. 255 US Unknown: 83cf1975
2 1 1 0 0.5 ms [+0ms]

66.36.224.232 AS0
IANA-RSVD-0 gec2.core1.dca2.hopone.net. 0 miles [+0] 254 US Unknown: 8098583d
3 2 1 1 1.8 ms [+1ms]

66.36.224.181 AS0
IANA-RSVD-0 ge-1-2-0--0.gw01.mcln.eli.net. 0 miles [+0] 252 US Unix: 2:23:42.789
4 1 5 1 1.8 ms [+0ms]

207.173.115.145 AS5650
ELIX ge-3-1-0--0.cr01.mcln.eli.net. 0 miles [+0] 251 US Unix: 2:23:42.818
5 4 3 2 2.7 ms [+0ms]

207.173.115.110 AS5650
ELIX so-3-0-0--0.er01.asbn.eli.net. 0 miles [+0] 250 US Unix: 2:23:42.852
6 3 4 3 3.0 ms [+0ms]

154.54.11.53 AS174
COGENT p12-2.core01.iad01.atlas.cogentco.com. 0 miles [+0] 250 US [Router did not respond]
7 4 4 4 4.1 ms [+1ms]

154.54.2.201 AS174
COGENT p11-0.core01.dca01.atlas.cogentco.com. 0 miles [+0] 249 US [Router did not respond]
8 87 59 44 44 ms [+40ms]

66.28.4.90 AS174
COGENT p3-0.core01.iah01.atlas.cogentco.com. 0 miles [+0] 244 US [Router did not respond]
9 74 122 130 74 ms [+29ms]

66.28.4.6 AS174
COGENT p14-0.core01.san01.atlas.cogentco.com. 0 miles [+0] 243 US [Router did not respond]
10 115 86 84 75 ms [+1ms]

66.28.4.230 AS174
COGENT p4-0.core02.lax02.atlas.cogentco.com. 0 miles [+0] 245 US [Router did not respond]
11 93 83 76 75 ms [+0ms]

204.6.150.242 AS174
COGENT g1-2.hc01.lax02.atlas.cogentco.com. 0 miles [+0] 244 US Unix: 2:23:43.238
12 * 75 * 75 ms [+0ms]

38.101.111.34 ASN=174[Destination Unreachable] unknown.cogentco.com 0 miles [+0] 52 Unix: 2:23:43.344
13 * * * 99999 ms [+99924ms]

[Unknown] [Unknown - Firewall did not respond] 0 miles [+0]

[TLAM Strike]

Ok this is what I got
Tracing route to www.imageshack.us [38.101.111.55]
over a maximum of 30 hops:

1 160 ms 151 ms 160 ms 66.133.132.65
2 240 ms 150 ms 481 ms 66.133.132.2
3 170 ms 160 ms 150 ms p5-1-0.gw01.roch.eli.net [65.73.239.9]
4 140 ms 160 ms 161 ms 65.73.205.1
5 210 ms 150 ms 150 ms ge-1-1-0--0.cr01.roch.eli.net [207.173.114.205]

6 170 ms 161 ms 150 ms so-0-0-0--0.cr01.nwrk.eli.net [207.173.114.233]

7 171 ms 160 ms 150 ms so-3-0-0--0.cr02.nwrk.eli.net [207.173.114.202]

8 190 ms 150 ms 171 ms so-0-0-0--0.cr02.mcln.eli.net [207.173.114.253]

9 171 ms 170 ms 170 ms so-3-0-0--0.er01.asbn.eli.net [207.173.115.110]

10 160 ms 160 ms 160 ms p12-2.core01.iad01.atlas.cogentco.com [154.54.11
.53]
11 180 ms 171 ms 170 ms p11-0.core01.dca01.atlas.cogentco.com [154.54.2.
201]
12 211 ms 190 ms 210 ms p3-0.core01.iah01.atlas.cogentco.com [66.28.4.90
]
13 231 ms 240 ms 230 ms p14-0.core01.san01.atlas.cogentco.com [66.28.4.6
]
14 220 ms 241 ms 250 ms p4-0.core02.lax02.atlas.cogentco.com [66.28.4.23
0]
15 240 ms 250 ms 241 ms g5-2.hc01.lax02.atlas.cogentco.com [38.112.36.25
0]
16 241 ms 240 ms 230 ms 38.101.111.55

Trace complete.

I seem to be able to upload small .gifs and .html occasonly (I was able to do it once with each of those two extentions)

[TLAM Strike]

I got this little icon on my task bar that I can use to get status or disconnect my Dial Up. It has two PCs and the montors flash blue when sending or reciving (left is sending right is reciving I think). Now when I'm uploading they stop flashing blue for most of the time, they might just go blue for a few seconds then they stay dark. I think this means my computer isn't sending the data. :hmm:

[sonar732]

Do me a favor and connect with your AOL, then do the same with the tracert and post those results so that it can be compaired. It's been so long since I provided dial-up support that I can't remember what the typical time in ms was.

Yes, your computer isn't sending anything when it stays dark. Another way to tell is to double click on that icon and it will show you the send/receive data in packet form.

[Perilscope]

Have you asked your ISP if they impose a limitation?

[TLAM Strike]

This is what I got with AOL:

Tracing route to www.imageshack.us [207.150.190.40]
over a maximum of 30 hops:

1 201 ms 180 ms 180 ms ipt-dtcc02.dial.aol.com [205.188.70.66]
2 170 ms 190 ms 181 ms iptfarmc-dr2-sw0.conc.aol.com [205.188.120.94]
3 180 ms 181 ms 180 ms wc1-dtc-ae2.net.aol.com [172.18.30.43]
4 171 ms * 171 ms dar1-dtc-GE1-1-0.net.aol.com [172.18.52.65]
5 180 ms 201 ms 180 ms pop2-ash-P5-0.atdn.net [66.185.141.69]
6 181 ms 190 ms 190 ms Level3.atdn.net [66.185.140.254]
7 180 ms 180 ms 180 ms so-1-1-0.bbr2.Washington1.Level3.net [64.159.3.6
5]
8 210 ms 231 ms 220 ms as-0-0.mp2.Tampa1.Level3.net [209.247.11.198]
9 201 ms 220 ms 230 ms ae-23-56.car3.Tampa1.Level3.net [4.68.104.171]
10 210 ms 210 ms 211 ms 4.79.172.2
11 220 ms 211 ms 220 ms GigE3.ds05a.tpa.sagonet.net [65.110.32.74]
12 211 ms 210 ms 210 ms unknown.sagonet.net [207.150.190.40]

Trace complete.


Have you asked your ISP if they impose a limitation? Might be the 1st thing I do on Monday.

[sonar732]

This is the part is what concerns me with your current ISP...

2 240 ms 150 ms 481 ms 66.133.132.2

There are two *normal* factors that significantly influence the latency of a consumer device. The latency of the connecting device. For a dial-up modem, this is normally anywhere from 100 to 220ms.

I also suggest downloading this freeware utility.

http://www.pingplotter.com/freeware.html

(The following is for PingPlotter only) If you've determined that your latency is out of the normal realm, and if you're seeing problems with some aspect of your connection (unexpected slowdowns, disconnects, or that you are often forced to "retry"), then looking at the PingPlotter data should help you understand the source of the problem. You're looking for big changes in latency and/or packet loss between two hops. Start at the end and go backwards till you find a hop that's not showing the problems that your final destination is showing. Once you've identified that, then you know where the problem is occurring. Ideally, you'd be able to contact that provider and find out how to solve the problem. Often, the result is that you would contact your ISP and they would help you solve the problem.

[TLAM Strike]

Ok I ran that program and this is what I got. Around Step 8 and Step 12 it gets higher latancy. And on step 9 I have gotten some packet loss. (Err 1 PL%10)

Target Name: www.imageshack.us
IP: 38.101.111.10
Date/Time: 2/25/2006 10:08:58 PM

1 151 ms [66.133.132.65]
2 151 ms [66.133.132.2]
3 141 ms p5-1-0.gw01.roch.eli.net [65.73.239.9]
4 151 ms [65.73.205.1]
5 150 ms ge-1-1-0--0.cr01.roch.eli.net [207.173.114.205]
6 140 ms so-0-0-0--0.cr01.nwrk.eli.net [207.173.114.233]
7 140 ms so-3-0-0--0.cr02.nwrk.eli.net [207.173.114.202]
8 220 ms so-0-0-0--0.cr02.mcln.eli.net [207.173.114.253]
9 160 ms so-3-0-0--0.er01.asbn.eli.net [207.173.115.110]
10 170 ms p12-2.core01.iad01.atlas.cogentco.com [154.54.11.53]
11 160 ms p11-0.core01.dca01.atlas.cogentco.com [154.54.2.201]
12 210 ms p3-0.core01.iah01.atlas.cogentco.com [66.28.4.90]
13 230 ms p14-0.core01.san01.atlas.cogentco.com [66.28.4.6]
14 220 ms p4-0.core02.lax02.atlas.cogentco.com [66.28.4.230]
15 241 ms g5-2.hc01.lax02.atlas.cogentco.com [38.112.36.250]
16 231 ms [38.101.111.10]

[sonar732]

Give your ISP a call with those results and see what they have to say.

[sonar732]

One last option...

For instance, open a command window and type the following command:

C:\>netstat -s -p tcp

TCP Statistics for IPv4

Active Opens = 201
Passive Opens = 12
Failed Connection Attempts = 0
Reset Connections = 16
Current Connections = 1
Segments Received = 1679
Segments Sent = 1617
Segments Retransmitted = 2

This shows that, of 1617 packets sent, only 2 had to be retransmitted, which is very good. A retransmission rate higher than a few percent would be poor. Retransmission might occur because:

* a packet that this PC sent was lost and never received at the far end; or
* the packet was received at the far end, but the ACK acknowledgement packet from the far end back to this PC was lost.


What matters is how the counters are changing now. It would be better when investigating an upload performance problem to do this:

* use netstat to record the values of the Sent and Retransmitted counts;
* perform a large upload, e.g. FTP to some remote FTP server;
* use netstat to record the new values of the Sent and Retransmitted counts;
* subtract the earlier counts from the later counts to derive the counts for the upload itself;
* if the Retransmitted count increase is more than a few percent of the Sent count increase, then there must be some packet loss problem associated with that upload.

For instance, here is an example:

Before upload:
Segments Sent = 12506
Segments Retransmitted = 485

After upload:
Segments Sent = 14214
Segments Retransmitted = 1156

So, segments sent = 14214 - 12506 = 1708
Segments retransmitted = 1156 - 485 = 671

Nearly 40% retransmitted.

[Iceman]

Been a while..........thank God... since I used dial up but you might try changing the connection speed period....the bit rate somewhere in the options of the dial up connection...or your connection is just too slow to make a good upload connection period....."under maximum BPS"....set it to lowest maybe for the upload....or try different speeds....also there should be flow control settings and a couple others have to mess with them.

[TLAM Strike]

Ok this is what I got before uploading (I did have subsim open)
Active Opens = 821
Passive Opens = 13
Failed Connection Attempts = 10
Reset Connections = 445
Current Connections = 2
Segments Received = 7558
Segments Sent = 8407
Segments Retransmitted = 536

My connection to 206.107.131.80:http and homer.berkhirt.com:http was in state TIME_WAIT

This is what I got after I attempted to upload
Active Opens = 832
Passive Opens = 13
Failed Connection Attempts = 10
Reset Connections = 447
Current Connections = 0
Segments Received = 7655
Segments Sent = 8522
Segments Retransmitted = 546

My connection to 168.75.68.10:http was in state TIME_WAIT

Whats you take on these stats? Seems kinda high but is it normal for a dial up connection?

[TLAM Strike]

Been a while..........thank God... since I used dial up but you might try changing the connection speed period....the bit rate somewhere in the options of the dial up connection...or your connection is just too slow to make a good upload connection period....."under maximum BPS"....set it to lowest maybe for the upload....or try different speeds....also there should be flow control settings and a couple others have to mess with them. Does anyone know where those settings are? I see max port speed in my modem options but thats it... :hmm:

I changed the port speed and didn't make a diffrence that I can tell. I might have been slower but the upload still failed.

[Iceman]

look at the properties of your dial up connection in your network places folder...definatly sounds like an isp problem...maybe they have some ports blocked in which case nothing you do will be able to make succed then.

[sonar732]

So, by the formula...

Segments sent...8522 - 8407=115
Segments Retransmitted ... 546 - 536=10

Percentage loss... 8.7%

This is mine....

TCP Statistics for IPv4

Active Opens = 870
Passive Opens = 8
Failed Connection Attempts = 3
Reset Connections = 79
Current Connections = 11
Segments Received = 29247
Segments Sent = 27050
Segments Retransmitted = 15

TCP Statistics for IPv4

Active Opens = 884
Passive Opens = 8
Failed Connection Attempts = 3
Reset Connections = 79
Current Connections = 11
Segments Received = 29861
Segments Sent = 27730
Segments Retransmitted = 68

Segments Sent...27730 - 27050=680
Segments Retransmitted...68 - 15=53

7.8 % loss with no problem uploading to imageshack on DSL.

[sonar732]

There are two different places you can set the port speed. In the connection properties and the modem properties.

Click settings on your connection tab with the ISP selected. Then, click on properties by the username. Next, click on configure and you should see the port speed.

[TLAM Strike]

Yea I found that a few mins ago and have been playing with it. I set it to max (which is more than my connection I think) and everything loads faster but all that does with uploads is get me to the "Cannot Find Server" screen or blank screen faster. Setting it low just gives me a low connection and I can't really get to the point of testing it.

[TLAM Strike]

Ok I called my ISP and they said that there is no limit on Uploads and it should be working. Also I should try a FTP program, unfortunately I don't know of any FTP servers that I could use for the test.

Also on a somewhat related note I uninstalled my AOL (I figured maybe that was causing the problem) but in IE it still says “Provided by AOL” and has the AOL logo on the right hand corner. How do I get rid of it?

[sonar732]

Also on a somewhat related note I uninstalled my AOL (I figured maybe that was causing the problem) but in IE it still says “Provided by AOL” and has the AOL logo on the right hand corner. How do I get rid of it?

That is hard coded into IE via the registry.

Your browser logo shows something other than the IE logo. Maybe you have installed your ISP software and you have a different logo on the top right. How do you remove it?

1. Close all browser windows
2. Start -> Run
3. Type RunDLL32.EXE IEdkcs32.dll,Clear
4. Click on OK, and start Internet Explorer. You should find the old spinning IE logo.

[TLAM Strike]

Hmmm the AOL logo is till there...

AOL is like the Borg, it adapts to everything you try against it and once they are aboard your ship all you can do is use the self-destruct… :(

[sonar732]

Try this...

# Navigate to HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main
# Create a new string value called "Window Title" and give it the value of what ever title you want IE to have
# Restart IE and take a gander at your new title.

and

HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Toolbar

and delete the BrandBitmap and SmBrandBitmap [values] there will restore the spinning globe.

[Iceman]

Yea that aol logo is nothing..it is called "Branding" by ISP companies and is nothing but advertising by means of changing the logo....nothing to worry about...but cool fix I think Sonar posted if it returns it to normal.

[TLAM Strike]

Ok the 2nd fix kinda worked. When something is loading its the default IE logo when its loaded its the AOL logo. I guess I can live with that.

THat window title value works like a cham, I'm trying to think of something cool sounding to stick in to my IE title bar... :hmm:

Any other ideas as to my upload problem.

[sonar732]

Can you get a different access number? Lastly, update your modem software/firmware. :damn: :damn:

Another website that you can look at for help...

http://www.extremetech.com/article2/0,1697,1153604,00.asp

[TLAM Strike]

I updated my modem software to no effect. I contact my ISP and they gave me another access number, which doesn’t work for some reason (I swear my modem received a busy signal...)

No other ideas?

Anyone know a good tech forum that might have someone who knows the answer.
:damn:

[Iceman]

THE OBVIOUS STUFF

We hate to ask, but you did check the obvious things, right?



Make sure that you and your Internet service provider use the same 56K protocols. 56K requires that both ends have 56K modems, and they both have to use the same kind of 56K technology (x2, K56flex, or V.90). Despite what you may have heard, V.90 is not the same as x2 or K56flex. It is a third and distinct 56K protocol. Your ISP will be able to tell you which protocol they use.
Some Internet service providers have separate phone numbers for 56K. Make sure you're calling the right number.


THE EASY ANSWERS

Things that are easy to try even if you don't know much about computers. Don't skip this section, because these fixes often work.



If there is a telephone, answering machine, etc., plugged into the back of the modem, unplug it from the back of the modem. The modem is supposed to ignore devices plugged into it when it is online, but that is not always the case.
Try disconnecting additional telephony devices (fax, phones, answering machines, alarm systems, etc.) from the phone line, even if they're in a different room. I've heard from readers whose connect speed jumped 10K when they unplugged a fax machine or cordless phone in another room.
Also try running the phone line directly from the back of the modem to the wall, without passing through surge suppressors, splitters, phone line extenders, etc. This is a basic and useful step in modem troubleshooting.


MODERATELY DIFFICULT ANSWERS

These require slightly more computer skill. If you don't know how to use a terminal program, click on the links for help.



DO NOT SKIP THIS NEXT STEP. It's always a good idea to check the firmware page to see if there is a more recent firmware version available. Many people's problems have disappeared once they installed a new version of the firmware.
Visit the inits and drivers page to see if there is an init string or better yet a driver for your modem. If there is, download and install it. The inits and drivers page includes installation instructions.
If your modem supports more than one 56K protocol, you may want to tell it which protocol (V.90, x2, or K56flex) it should use. The commands are listed on the interoperability page.
It's possible there is an incompatibility between your modem and your ISP's modems. You might try dialing into some other local ISPs. You don't have to join or do anything after you connect: just see how fast you can connect to their modems.
If this is a Rockwell-based K56flex modem, issue an ATI3 command in a terminal program. If the version number includes the letters "DSP", click here. If the version is 0.5 something, and your Internet service provider uses K56flex Livingston Portmasters, click here. If the version is 1.0 something, you should try adding S202=32 to your init string.
If this is a Lucent-based K56flex modem, issue an ATI3 command in a terminal program. The firmware version should be at least 4.06, and higher versions are better. Click here for more information.



OR MAYBE IT'S YOUR PHONE LINE

I was hoping it wouldn't come to this, but it may not be your modem or inside phone lines at all.

It may be that the phone lines in your immediate neighborhood don't support 56K

As explained in the Basics section of the 56K Primer, multiple digital/analog conversions will prevent the use of 56K technology and limit your modem to V.34 speeds (a maximum of 33.6K).

"It's not my phone lines. I know they support 56K"

OK, how do you know your phone lines support 56K? 3Com's line test is not guaranteed. It can tell you that your phone line supports 56K when in fact it doesn't, and vice versa. Don't put all of your faith in it. If you must use the test line, 3Com recommends calling it multiple times (ten times, say). On some calls it may say your line supports 56K and on other calls it may say the opposite.

The fact that your modem can connect at 56K speeds to a long distance number is no guarantee that the same is true of local numbers, and vice versa. Long distance calls may be routed through telephone circuits which are significantly better or significantly worse than the local circuits used to connect to your ISP.

http://www.modemsite.com/56k/trouble.asp
http://www.modemsite.com/56k/disconnects.asp


ALL these tips are good....this last link is for Broadband but I know they have alot of great stuff like patches and stuff that may help ya out.

http://www.speedguide.net/

in this speedguide site has a tcp/ip analyzer...really look at this site good too.

[TLAM Strike]

Ok I figured it might have been a problem with IE so I tried Firefox and I have the same problem but I get the following error for what its worth:

The connection was reset

The connection to the server was reset while the page was loading.

* The site could be temporarily unavailable or too busy. Try again in a few
moments.

* If you are unable to load any pages, check your computer's network
connection.

* If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.