Reply
Sun 30 Oct, 2005 06:21 pm
I should begin by saying I've only been having problem for the past 24 hours or so; I've done nothing drastic to my configuration before or since that should be causing these problems.
We are talking dial-up. I suspect I may have a faulty modem. But like I said, everything was fine until very recently, so I'm not convinced that's the answer.
The most pressing issue is simply with load times. While it's showing nice connection speeds (currently 34.6 Kbps), the performace is more like what you get with 9.6 Kbps. (A download I made this morning even had a rate of 1.24! A three or four minute DL took 20!)
Even worse, just flipping from page to page here on a message board, for example, is taking 30-45 seconds. I'd love to just look for help here on the net, but with that kind of load time, it's just downright painful.
The machine is a refurbished Dell Latitude 610C notebook with a Pentium III-m. Windows 2000 Pro OS. The modem is a PCTEL 2340WT V.9x MDC.
I just got it! So literally, the only programs on the machine are the OS and my ISP software (Netscape Internet Service), with a couple of other small programs that came included.
It just doesn't make any sense why I'd be having problems like this with such a clean machine. 30GB hardrive, 512 RAM. I just don't get it.
I've spent roughly five hours or so troubleshooting with the Windows Troublshooter, so I have already tried much (or all) the obvious adjustments.
Other than that, I don't know what else to tell you.
Here's a copy of my modem log taken just a moment ago; hopefully that will tell someone something:
Quote:10-30-2005 18:28:41.387 - File: C:\WINNT\system32\unimdm.tsp, Version 5.0.2195 - Retail
10-30-2005 18:28:41.387 - File: C:\WINNT\system32\unimdmat.dll, Version 5.0.2195 - Retail
10-30-2005 18:28:41.387 - File: C:\WINNT\system32\uniplat.dll, Version 5.0.2195 - Retail
10-30-2005 18:28:41.467 - File: C:\WINNT\system32\drivers\modem.sys, Version 5.0.2195 - Retail
10-30-2005 18:28:41.488 - File: C:\WINNT\system32\modemui.dll, Version 5.0.2195 - Retail
10-30-2005 18:28:41.488 - Modem type: PCTEL 2304WT V.9x MDC Modem
10-30-2005 18:28:41.488 - Modem inf path: oem14.inf
10-30-2005 18:28:41.488 - Modem inf section: Modem1
10-30-2005 18:28:41.908 - 115200,8,N,1, ctsfl=1, rtsctl=2
10-30-2005 18:28:41.908 - Initializing modem.
10-30-2005 18:28:41.908 - DSR is low while initializing the modem. Verify modem is turned on.
10-30-2005 18:28:41.908 - CTS is low while initializing modem.
10-30-2005 18:28:41.918 - Send: AT<cr>
10-30-2005 18:28:42.098 - Recv: AT<cr>
10-30-2005 18:28:42.098 - Command Echo
10-30-2005 18:28:42.098 - Recv: <cr><lf>OK<cr><lf>
10-30-2005 18:28:42.098 - Interpreted response: OK
10-30-2005 18:28:42.108 - Send: AT&FE0&C1&D2&K3V1W3S0=0<cr>
10-30-2005 18:28:42.108 - Recv: AT&FE0&C1&D2&K3V1W3S0=0<cr>
10-30-2005 18:28:42.108 - Command Echo
10-30-2005 18:28:42.108 - Recv: <cr><lf>OK<cr><lf>
10-30-2005 18:28:42.108 - Interpreted response: OK
10-30-2005 18:28:42.118 - Send: ATS7=60S30=0M1\N3%C3&K3B2N1X4<cr>
10-30-2005 18:28:42.118 - Recv: <cr><lf>OK<cr><lf>
10-30-2005 18:28:42.118 - Interpreted response: OK
10-30-2005 18:28:42.128 - Send: ATM1<cr>
10-30-2005 18:28:42.128 - Recv: <cr><lf>OK<cr><lf>
10-30-2005 18:28:42.128 - Interpreted response: OK
10-30-2005 18:28:42.128 - Waiting for a call.
10-30-2005 18:28:42.138 - Send: ATS0=0<cr>
10-30-2005 18:28:42.138 - Recv: <cr><lf>OK<cr><lf>
10-30-2005 18:28:42.138 - Interpreted response: OK
10-30-2005 18:28:42.138 - 115200,8,N,1, ctsfl=1, rtsctl=2
10-30-2005 18:28:42.138 - Initializing modem.
10-30-2005 18:28:42.148 - Send: AT<cr>
10-30-2005 18:28:42.148 - Recv: <cr><lf>OK<cr><lf>
10-30-2005 18:28:42.148 - Interpreted response: OK
10-30-2005 18:28:42.158 - Send: AT&FE0&C1&D2&K3V1W3S0=0<cr>
10-30-2005 18:28:42.158 - Recv: <cr><lf>OK<cr><lf>
10-30-2005 18:28:42.158 - Interpreted response: OK
10-30-2005 18:28:42.169 - Send: ATS7=60S30=0M1\N3%C3&K3B2N1X4<cr>
10-30-2005 18:28:42.169 - Recv: <cr><lf>OK<cr><lf>
10-30-2005 18:28:42.169 - Interpreted response: OK
10-30-2005 18:28:42.179 - Send: ATM1<cr>
10-30-2005 18:28:42.179 - Recv: <cr><lf>OK<cr><lf>
10-30-2005 18:28:42.179 - Interpreted response: OK
10-30-2005 18:28:42.179 - Dialing.
10-30-2005 18:28:42.189 - Send: ATDT#######<cr>
10-30-2005 18:29:05.262 - Recv: <cr><lf>CONNECT 34666/PROTOCOL: LAPM/COMPRESSION: V.44<cr>
10-30-2005 18:29:05.262 - Interpreted response: Connect
10-30-2005 18:29:05.262 - Receive Connect but CD was low, Waiting for signal to go high
10-30-2005 18:29:05.282 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.302 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.322 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.342 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.362 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.382 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.402 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.422 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.442 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.462 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.482 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.502 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.522 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.542 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.562 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.582 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.602 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.622 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.642 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.662 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.682 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.702 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.722 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.742 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.762 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.782 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.802 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.823 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.843 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.863 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.883 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.903 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.923 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.943 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.963 - After waiting 20ms CD is still low.
10-30-2005 18:29:05.983 - After waiting 20ms CD is still low.
10-30-2005 18:29:06.003 - After waiting 20ms CD is still low.
10-30-2005 18:29:06.023 - CD has been raised
10-30-2005 18:29:06.023 - Connection established at 34666bps.
10-30-2005 18:29:06.023 - Error-control on.
10-30-2005 18:29:06.023 - Data compression on.
10-30-2005 18:29:36.026 - Read: Total: 3675, Per/Sec: 120, Written: Total: 6496, Per/Sec: 214
10-30-2005 18:31:36.029 - Read: Total: 31330, Per/Sec: 230, Written: Total: 46908, Per/Sec: 336
10-30-2005 18:33:36.031 - Read: Total: 90846, Per/Sec: 495, Written: Total: 68650, Per/Sec: 181
10-30-2005 18:35:36.034 - Read: Total: 120971, Per/Sec: 251, Written: Total: 87489, Per/Sec: 156
10-30-2005 18:37:36.036 - Read: Total: 130900, Per/Sec: 82, Written: Total: 89226, Per/Sec: 14
10-30-2005 18:39:36.039 - Read: Total: 158395, Per/Sec: 229, Written: Total: 97150, Per/Sec: 66
10-30-2005 18:41:36.041 - Read: Total: 195420, Per/Sec: 308, Written: Total: 116940, Per/Sec: 164
10-30-2005 18:43:36.044 - Read: Total: 216773, Per/Sec: 177, Written: Total: 129340, Per/Sec: 103
10-30-2005 18:45:36.046 - Read: Total: 271740, Per/Sec: 458, Written: Total: 155785, Per/Sec: 220
10-30-2005 18:47:36.049 - Read: Total: 345369, Per/Sec: 613, Written: Total: 184889, Per/Sec: 242
10-30-2005 18:49:36.051 - Read: Total: 375774, Per/Sec: 253, Written: Total: 197638, Per/Sec: 106
10-30-2005 18:51:36.054 - Read: Total: 387310, Per/Sec: 96, Written: Total: 205978, Per/Sec: 69
10-30-2005 18:53:36.057 - Read: Total: 420882, Per/Sec: 279, Written: Total: 231710, Per/Sec: 214
10-30-2005 18:55:36.059 - Read: Total: 428816, Per/Sec: 66, Written: Total: 239156, Per/Sec: 62
10-30-2005 18:57:36.062 - Read: Total: 463325, Per/Sec: 287, Written: Total: 256931, Per/Sec: 148
10-30-2005 18:59:36.064 - Read: Total: 519657, Per/Sec: 469, Written: Total: 284056, Per/Sec: 226
10-30-2005 19:01:36.067 - Read: Total: 591698, Per/Sec: 600, Written: Total: 323185, Per/Sec: 326
10-30-2005 19:03:36.069 - Read: Total: 595027, Per/Sec: 27, Written: Total: 326821, Per/Sec: 30
10-30-2005 19:05:36.072 - Read: Total: 595111, Per/Sec: 0, Written: Total: 327110, Per/Sec: 2
10-30-2005 19:07:36.074 - Read: Total: 595195, Per/Sec: 0, Written: Total: 328566, Per/Sec: 12
10-30-2005 19:09:36.077 - Read: Total: 595279, Per/Sec: 0, Written: Total: 328618, Per/Sec: 0
HELP!
Looks to me like a noisy phoneline might be at the root of your problem. Could be a faulty modem, but that's not real high on the list, the way that log reads. I really suspect a phoneline issue. If so, it could be transient, clearing up by itself in day or so. If the problem doesn't clear up on its own, hre are a few things you might wanna try, just to narrow the focus of suspicion
1) With no other equipment connected to your phonline, use a known-good phoneline of not more than 6' in length to connect your modem directly to the telco wall jack - no splitters or filters or extensions or swivels between your machine and the wall jack, just a short cord, and no other telephones or other devices connected to that phoneline anywhere in the home. Try a connection and see what happens. If you get a decent connection, your modem is OK, but something else is causing interference on your phone line.
2) If possible, locate the telco linedrop interface - the box outside your dwelling to which the external telephone line is connected. If you live in an apartment or other multiple dwelling unit, that may be a bit of a trick; the line drop interface will prolly be in a big switchbox sort of affair, not readilly accessed by folks not connected with the telco or the building.
If you can find the linedrop interface, assuming here you don't live in a multiple dwelling unit, there should be a door or panel which you can open. Behind it, there should be a jumper, a short, standard telephone cord with standard plugs at either end. One end of that cord will connect to a jack which is wired to the telco linedrop, the main phoneline to your dwelling. The other will connect to a jack wired to the actual interface between your internal phone lines and the telco line drop. Unplug the end of that short jumper which seems to connect to the line drop. Using any standard telephone, connect to the jack from which you removed the plug, and see if the phone has a dial tone. If it does, that's the line you want. If not, try the other one.
Once you've figured out which jack you want, connect your modem to that jack, using as short a known-good phone line to make the connection as you can manage. When the modem is hooked up to the live phone line, try to connect to your ISP account. If you connect OK from the outside interface, but not from inside, your modem is OK but you have a problem with your inside phone lines. Sort of a bummer, if so - that usually means you pay for any repairs.
3) If possible, have a freind who has a laptop or modem-equipped handheld bring it over to your place, and have the freind try to connect using your normal indoor phone connection. If your freind has an ISP other than yours, that's great; have your freind try to connect to that account, then try to connect to your own account using the freind's device. If your freind's machine connects OK to both accounts, but your machine won't, suspicion turns to your modem. If your freind has a different ISP than do you, and connects to that account OK but not to yours, suspicion points to your ISP. If your freind has the same difficulty you have, connecting to either account, suspicion points to the phone line.
4) Take your machine to another location - a freind's home or place of business, preferably one which has a valid dialup internet account. Try to find someone who's phone # has a different prefix than yours, and its even better if your freind's internet account is with an ISP other than yours.
Connect your machine to your freind's phoneline, try connecting to your own ISP account, and see what happens. Then try connecting via your freind's account. If your machine connects to your account OK from your freind's location, your problem likely is your home phone line. If your machine will connect OK to your freind's account - particularly if your freind has a differnet ISP - but not to your account, the problem is with your ISP.
There are some command strings you could try, in advanced modem settings, to force your modem to think its a different type of modem, but there's not much point going there unless and until you've either confirmed or eliminated your phone line and your ISP.
Oh, and I suspect your machine is a Dell Latitude C610, not a 610C, and that your modem is a PCTEL 2304WT V.9x MDC, not a 2340WT V.9x MDC. Those I've seen.
Great suggestions. Thanks a lot! And just so you know, I think you're absolutely on the right track. We've - oh, what a coinsidence - had a roofing company here roughly since I've been having problems. Again, thanks.
Thanks again, timberlandko. Just thought I'd let you know when I connect to another phone line, I get superfast connections and exceptional browsing. Guess it's time to contact the phone company and complain.
Final post for any onlookers: turns out it was the cord coming from a splitter to my comp. Replaced the cord, better performance than ever.
Stumble It!
Tweet This
Bookmark on Delicious
Share on Facebook
Share on MySpace