Connection Problems

I am using a dial-up connection, and for some reason, somehow messages are being missed somehow between my modem and WindowsXP. Or that is the way I am thinking, but I'm hoping someone has answers.

When I connect to my ISP, there are two little modems blinking in my task bar that let me know I am connected. It used to be that while they were blinking, I always knew I was still connected. When they disappeared, the connection was lost. That is no longer happening now.

I will connect to my ISP, and then proceed to download my e-mail or whatever. Then, while in the middle of something (sending an e-mail, or trying to access a web site) everything stops responding (message that mail server ended connection, im's go off-line, "cannot find page" if opening browser) but those two little monitors are still blinking away, implying that I am still connected.

On some rare occasions, I will not be able to get e-mail, or open a web page, but the IM still appears to be connected also, but that is very rare.

So it seems to me I've lost my connection, but my computer is not getting the message for some reason. I have to manually disconnect, and then re-connect.

And along with this problem is the fact that for some reason of late, where I used to be connected all day long, now I have a terrible time keeping the connection. Often I will lose the connection (althought I don't know it right away) almost immediately after being connected, or withing a very short period of time. But then at other times, I will be able to stay connected for an hour or so before actually losing it (but the monitors are still blinking). It is only occasiionally that the connection will be lost and my computer will actually realize it and then try to re-connect.

I sure hope someone knows/understands what I am trying to explain because it has become very frustrating when trying to complete certain transactions over the Internet, and then losing my connection in the middle of it, but not knowing it because the PC doesn't know it either! :mad

Sandie
Windows XP SP2
Compaq Prosario 6420NX
AMD Athlon XP 2200+
480 MB of RAM

 

It is very possible that the blinking icons do indicate that you have a connection but that you aren't able to send or receive data. The trick here is going to be figuring out exactly where the break is occuring.

Is there any way you can try with a different modem and see if that cures it? Also try with a different cable from wall to modem and modem to PC if the modem is external. If it's internal but on a card rather than built into the motherboard, also try powering down, removing the modem, cleaning the contacts with a pencil eraser, and putting it back in.

If no spare modem is available or if you try one and the problem remains, then we need some data. When you first get connected, open a cmd prompt (start->run->cmd). Once you have the cmd window open, key in

Code:

ipconfig /all >> c:\ipconfig.txt

to send a copy of your settings to a text file. When the connection drops but the lights keep blinking, do the exact same thing. Using >> to send the data will force it to append to the bottom of the text file rather than overwriting.

Also, print a copy of the first set of data and after the second ipconfig, from a cmd window (and use the IP addresses rather than DHCP, DNS, etc.)

Code:

ping DNS >> c:\ipconfig.txt
ping DHCP >> ipconfig.txt

Then copy the contents of that file and paste the whole thing into a reply here.

Note that if you just do the commands you will see results in the cmd window but if you redirect the output to a text file you won't see any onscreen results. Feel free to play with those commands while things are working so you can see the sort of data you'll be collecting.

I'd also suggest telling your phone company that you have periodic noise on your phone line and ask them to check it for you. Don't mention it being a modem/internet issue since they really don't have to provide data quality service and might not be willing to check as they would if you reported noise with voice conversations.

 

But that does bring up another point, do you have call waiting / call waiting ID? If yes, have you checked your dial up string to turn these features off during your internet connection? If they are active and correct, may want to cycle them off/on to rattle out any gremlins.

 

Hello Newt,

Thank you so much, but I don't know how far I will get trying your suggestions.

First, I have an internal modem, but I don't know enough about the inner workings of the computer to know where it is or how to remove, replace, or anything else with it. About the most I've accomplished inside my PC is to add a memory card, and I was a nervous wreck until I saw I had done it correctly! LOL

The second instruction you gave I will attempt, but I will be honest and admit that I won't know what I'm doing, so there is no guarrantee I will be doing it correctly. As for the second box of Code: you give, I don't really understand what you are asking me to do. I have 2 IP addresses (I think) that my ISP gave as the ones to add to my connection properties to connect properly. Are they the IP addresses of which you are referring? As to playing with any commands while things are working, I don't think that is going to fly either because I am so in a fog over this I wouldn't have a clue as to what other commands to send as to "play" with, and I rarely am connected long enough to get anything at all done, let alone time to "play" with anything. LOL

And last, I have contacted my phone company before bothering you folks here, and now I guess that was a mistake. I told them it was the separate line just for the PC, and requested a line check. They called back and told me the line test was perfectly clear. Of course, my ISP also denies any responsibility here, and claims there is absolutely no problem with their server either. That is always their reply, even when they know their server is out! They claim that any problems a customer has is always caused by either a virus or spam. And that is after I have already ran my anti-virus program, gone to both PC Pitstop and Housecall, and check with them as well, and then run the 3 spyware protection programs (Spyguard, Adaware, and Spybot Search & Destroy) that I have installed. And everything is cleared and good to go.

If it was easy to try another ISP, I would jump at the chance. But I live in a very rural area (alas, that is why there is no cable) and this one ISP almost has the market exclusively. They are a small local telephone company in another county, and they maintain a server at the local library in my Township. So when I called and asked them to check their server, it seems that they don't even have the ability (or so they claim) to check my connection with their server. They told me I was served by another telephone company, and so they would have to check my line.

For Dennis L,

I don't have call waiting or caller ID or any of those things.

Sandie
Windows XP SP2
Compaq Prosario 6420NX
AMD Athlon XP 2200+
480 MB of RAM

 

LOL - I understand being nervous about these things. If I hadn't had the luxury of being able to 'work on' PCs owned by my company, I doubt I'd ever have taken the case off of mine.

However, the bit about removing, cleaning, replacing the modem card is easier than you might think.
- shut down
- unplug the power cord
- remove the cover. Should just be a matter of removing a few screws.
- remove the single ***** holding the modem in place. You can identify it by looking at where the phone cord plugs in to the back.
- Lift one end of the card until you start seeing the connectors then just rock it a little and it should come right out.
- clean the gold connectors with a pencil eraser. Make sure not to touch them with your fingers since skin oil isn't real good for them.
- slide the card back into the slot and seat it firmly. They aren't fragile.
- replace the *****.
- replace the case.
- deed done.

The other part with the stuff in the code boxes (and put there so the spaces would be obvious) can't hurt anything - they just give you information. Just type in exactly what you see above and it should work fine. To make things a little easier for you, I'll type them below and you can copy/paste the lines into a notepad document then with a cmd window open, copy a line from the document, paste it into the cmd window, press ENTER, and move on to the next one.

Use this first one while things are working and then either close or minimize the cmd window, open c:\ipconfig.txt, and write down the IP address of your DNS and DHCP servers. When you have a loss of connection, run it again along with the next two where you will substitute the IP addresses for DNS and DHCP.

ipconfig /all >> c:\ipconfig.txt
ping DHCP >> ipconfig.txt
ping DNS >> c:\ipconfig.txt


For instance, if the ipconfig /all command showed you a DNS server address of 25.127.31.99 then you would use that rather than the word DNS.

To give you an example, here is what that text file would look like if run from my work PC. Note that you may have only one DNS address or possibly more. Use each one you have.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Windows IP Configuration

Host Name . . . . . . . . . . . . : WXPLH0NMP
Primary Dns Suffix . . . . . . . : us.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : us.com
cab.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : cab.com
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection #2
Physical Address. . . . . . . . . : 00-02-8A-2D-3F-49
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 172.29.11.57
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . : 172.29.8.127
172.29.8.126
DHCP Server . . . . . . . . . . . : 172.29.8.142
DNS Servers . . . . . . . . . . . : 172.29.9.4
172.29.9.6
148.128.90.64
Primary WINS Server . . . . . . . : 172.29.9.8
Secondary WINS Server . . . . . . : 143.168.8.8
Lease Obtained. . . . . . . . . . : Tuesday, August 30, 2005 23:54:42
Lease Expires . . . . . . . . . . : Tuesday, September 06, 2005 23:54:42

Pinging 172.29.8.142 with 32 bytes of data:

Reply from 172.29.8.142: bytes=32 time=9ms TTL=128
Reply from 172.29.8.142: bytes=32 time<1ms TTL=128
Reply from 172.29.8.142: bytes=32 time<1ms TTL=128
Reply from 172.29.8.142: bytes=32 time<1ms TTL=128

Ping statistics for 172.29.8.142:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 9ms, Average = 2ms

Pinging 172.29.9.4 with 32 bytes of data:

Reply from 172.29.9.4: bytes=32 time=15ms TTL=128
Reply from 172.29.9.4: bytes=32 time<1ms TTL=128
Reply from 172.29.9.4: bytes=32 time<1ms TTL=128
Reply from 172.29.9.4: bytes=32 time<1ms TTL=128

Ping statistics for 172.29.9.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 15ms, Average = 3ms

Pinging 172.29.9.6 with 32 bytes of data:

Reply from 172.29.9.6: bytes=32 time<1ms TTL=128
Reply from 172.29.9.6: bytes=32 time<1ms TTL=128
Reply from 172.29.9.6: bytes=32 time<1ms TTL=128
Reply from 172.29.9.6: bytes=32 time<1ms TTL=128

Ping statistics for 172.29.9.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 148.128.90.64 with 32 bytes of data:

Reply from 148.128.90.64: bytes=32 time=52ms TTL=122
Reply from 148.128.90.64: bytes=32 time=52ms TTL=122
Reply from 148.128.90.64: bytes=32 time=52ms TTL=122
Reply from 148.128.90.64: bytes=32 time=52ms TTL=122

Ping statistics for 148.128.90.64:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 52ms, Average = 52ms

 

Hello Newt,

First, I have recently discovered that my A drive is non-functioning, and a repairman will be coming soon to replace the old one with a new one. When he is doing that, I will have him check the modem and make sure the connections are clean. I am just too nervous about playing around down there, for one thing. And another, once I get down I am going to have one heck of a time getting back up. Physical limitations due to arthritis.

Now, I tried that command promt thing, and I don't know how you copy/paste, but I couldn't do that with it at all, so after I typed in what I thought was what you wanted me to type in (and I have a strong feeling I got it wrong) I had to type every response given to my notepad. But I will copy/paste what I received on here. It goes like this.

C:\Documents and Settings\Owner>ipconfig /all >> c:\ipconfig.txt

C:\Documents and Settings\Owner>Code:ipconfig /all >> c:\ipconfig.txt
The filename, directory name, or volume label syntax is incorrect.

C:\Documents and Settings\Owner>Codeing DNS >> c:\ipconfig.txt
The filename, directory name, or volume label syntax is incorrect.

C:\Documents and Settings\Owner>Codeing DHCP >> ipconfig.txt
The filename, directory name, or volume label syntax is incorrect

I know I did this wrong, but I really don't know what the DNS or DHCP is, or where to find them.

Also, I have a program called The Ultimate Troubleshooter, so I decided to run that this morning to see if it could find anything. What it did say in bold red flashing lights was
Microsoft Windows Scripting Host not found!!!!! And therefore, some of the information could not be gathered. Now I don't know where that is or how to find it, so........

Still, there was some information about IP addresses, so I will copy/paste that here and maybe it will tell you something.

Operating system : Windows XP Home Edition 2.0 2600
TUT version : 2.61
Registered To : Sandra L. Knapp
PC network name : SANDIESPC
Country Locale : United States 1-Sep-2005 12:16:48
--------------------------------------------------------------------------------

Windows IP Configuration of this PC
Host Name : SandiesPC
DNS Server : 65.167.41.2
DNS Server : 65.167.41.3
Node Type : Hybrid
IP Routing Enabled : No
WINS Proxy Enabled : No
DNS Enabled : No

Network cards, Modems, and other connections on this PC:

Description : WAN (PPP/SLIP) Interface
Adapter Type : PPP
Physical Address : 00-53-45-00-00-00
Dhcp Enabled : No
IP Address : 65.167.45.201
Subnet Mask : 255.255.255.255
Default Gateway : 65.167.45.201


And always, I want to thank you so much for your help.

Sandie
Windows XP SP2
Compaq Prosario 6420NX
AMD Athlon XP 2200+
480 MB of RAM

 

Hi Newt,

Keep your fingers crossed. I just MAY have solved my problem!!!

I set up a new connection to my ISP, and that was sometime after 3 pm. It is now after 7 pm, and I have kept my connection the entire time. This is a first. I will be more confident after signing on tomorrow and staying on the day long. Then I will know for sure.

I have set up an new connection twice before, but I did it a little different this time. I have to IP numbers that were given to me to put in as where I was to connect to. (it is mentioned as the Default Gateway in my previous post)

This time I deleted the old connection, and when I set up the new one, I did not put in that DNS information, I just told the computer to find the connection automatically. Is it possible that such a simple change can be what was needed to solve this problem?

Like I said, it's been working just fine now for about 4 hours. That alone is amazing compared to the past few weeks. But if this works again tomorrow, I will then feel mure at eaze, and be very happy indeed!

I will come back tomorrow and let you know how things are working.

Until then, thank you so much for all of your help and suggestions. Even when I am confused, I still appreciate the help that is always offered so graciously.

Thanks,
Sandie

 

Hi Newt

Ok, I don't care what they say, I am fairly certain now that the problem is with my ISP, and NOT my computer.

After setting up a new connection for the 3rd or 4th time late yesterday afternoon, I was able to connect, and remain connected for 5 hours without disruption. Hooray, right? Well this morning, it didn't last 10 minutes, and the connection was not working right, and yet I was still sending signal, just not receiving any.

Wouldn't that imply to you that the problem must be with the ISP and not my computer? When I called them AGAIN yesterday afternoon, they told me the problem HAD to be my computer, and they were sorry, but there was nothing they could do to help me. I told them I was sending signal, but not receiving it, and they just didn't want to hear it. They are like this all the time. It is always the customers computer that is messed up, never their server.

Ok, just wanted to let you know what was going on.

Sandie

 

Try checking success of neighbors / friends connection quality with this ISP.
Try to find some that use the same phone provider you use.
Also those that use phone service the ISP provides.
Out of curiosity, have you checked for local dialup access for national ISP providers? ... AOL, Netscape, Walmart would be just a few.

 

Hi Dennis L

Neighbors here are not right next door. I only know of two that are within a mile of my home that use the same providor. Other than that, there are some senior citizens that do not use computers. Those two neighbors only use their computers for short periods of time because they work while I am retired.

As to the national ISP services, none of them have an access number that I can use. I would have to call long distance to use any of their numbers. That is another major problem here. While most other exchanges cover large areas, and are also open to other exchanges without getting long distance charges, where I live that is not the case. Our exhcange is for a relatively small area, and if we want access to a very few other exchanges, we have to pay a monthly fee to access them. A few of the people that have Internet do that, but I can't afford to do that, or I would have.


As to contacting others that use phone services that my ISP provide, I would have to travel to a town 25 miles distant to find them, and I don't personally know anyone there. This small phone company provides ISP services to our area because they knew no other ISP served the area.

I have found one large phone service and ISP service that has an access number in my area..........USA Datanet.net. I have an account with them for long distance calls. I have contacted them, and I am going to try a 7 day trial of their Internet service to see if that works better. And then if I have the same problems, I will know something on my computer is causing a problem, but finding what it is will be another matter altogether. If everything works well using Datanet, then I will know for a fact that my present ISP is the problem, and I will just leave them, and stay with USA Datanet. But I have to wait a few days for their disc to be mailed out to me before starting their service.

Thank you for your response,
Sandie

 

Hi Newt,

I hope you get to see this. I think I know now what you wanted me to do, and I think I have the information you wanted. I "pinged" my ISP (65.167.41.2) and I did the ipconfig /all. Here is the information.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>ping 207.46.133.140

Pinging 207.46.133.140 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.46.133.140:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\Owner>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : SandiesPC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

PPP adapter NEP:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 65.167.45.217
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 65.167.45.217
DNS Servers . . . . . . . . . . . : 65.167.41.2
65.167.41.3
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Documents and Settings\Owner>ping 207.46.133.140

Pinging 207.46.133.140 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.46.133.140:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\Owner>ping 107.46.133.140

Pinging 107.46.133.140 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 107.46.133.140:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\Owner>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : SandiesPC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

PPP adapter NEP:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 65.167.45.228
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 65.167.45.228
DNS Servers . . . . . . . . . . . : 65.167.41.2
65.167.41.3
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Documents and Settings\Owner>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : SandiesPC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

PPP adapter NEP:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 65.167.45.230
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 65.167.45.230
DNS Servers . . . . . . . . . . . : 65.167.41.2
65.167.41.3
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Documents and Settings\Owner>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : SandiesPC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

PPP adapter NEP:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 65.167.45.230
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 65.167.45.230
DNS Servers . . . . . . . . . . . : 65.167.41.2
65.167.41.3
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Documents and Settings\Owner>ping 65.167.41.2

Pinging 65.167.41.2 with 32 bytes of data:

Reply from 65.167.41.2: bytes=32 time=126ms TTL=253
Reply from 65.167.41.2: bytes=32 time=135ms TTL=253
Reply from 65.167.41.2: bytes=32 time=112ms TTL=253
Reply from 65.167.41.2: bytes=32 time=120ms TTL=253

Ping statistics for 65.167.41.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 112ms, Maximum = 135ms, Average = 123ms

C:\Documents and Settings\Owner>ping 65.167.45.3

Pinging 65.167.45.3 with 32 bytes of data:

Request timed out.
Reply from 65.167.45.1: Destination host unreachable.
Request timed out.
Reply from 65.167.45.1: Destination host unreachable.

Ping statistics for 65.167.45.3:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Owner>ping 65.167.45.230

Pinging 65.167.45.230 with 32 bytes of data:

Reply from 65.167.45.230: bytes=32 time<1ms TTL=128
Reply from 65.167.45.230: bytes=32 time<1ms TTL=128
Reply from 65.167.45.230: bytes=32 time<1ms TTL=128
Reply from 65.167.45.230: bytes=32 time<1ms TTL=128

Ping statistics for 65.167.45.230:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Owner>




I hope this is the information you were requesting, and that you can find answers by seeing this.

As always, thank you so very much,
Sandie

 

A brief simplified explanation of how your dial up connection works.

You dial in and the modem at the ISP answers.
Your modem sends a standardized packet of data to which the ISP responds with a standardized response and your modem responds to that (This is all that screaching and squawking , it is called a handshake). All this is defined by the protocol (V90, or V92) . Through this handshake, the two modems determine the fastest speed at which data can be exchanged given that damaged packets must be resent (so if you set it to high you wind up with more damaged packets than not and do not get any data exchanged).
So what determines this limit? Pretty much the quality of the phone lines. Cracked insulation, nearby radio stations , a long rural run to the telephone company , etc can cause noise on the line and decrease connection speed, as can corrosion on your wall jack wires (moisture) things like answering machines or cordless phones (especially if they get low batteries) and even damaged phones.

What is happens if the noise increases after you have connected and negotiated a connection speed? Well that is a problem. The speed is set when you first connect , and only reconnecting will reset it. So if noise increases, then the data gets corrupted in transmission and eventually so much has to be resent that none arrives.

It could be a loose or damaged (tree branch in the lines) phone line, or it could be something in your house.

Check the wall jack for corrosion and replace if damaged.
Unplug all other equipment from the phone lines and try connecting . If it is higher speed, something in your house is a likely cause. If it stays connected , it is almost certain.

Pick up a phone and press any number. You should hear total silence. If you hear static or music etc, there is a problem with the line. A call to the phone company may help, but remember that they are only required to supply voice quality lines (9.6Kbps, not 56Kbps), but you can ask them to test your lines. Say you keep getting disconnected, without mentioning that it is your ISP or computer that gets disconnected.


At first I thought you were talking about the more email shows in your inbox than downloads, this is caused by your ISP using a spam filter. Things marked as spam get deleted when you access it and the filter runs.
So you see the inbox number of messages, the filter runs and you get the non spam delivered.

 

Hello Oshwyn5,

Thank you for your response.

The line used for my PC is a totally separate line from any of the house phones. The only thing using this line IS my PC.

I called Verizon, and they ran a line test for me, and the line is very clear, and I have listened myself by unplugging the PC and plugging in one of the house phones, and I heard nothing but silence also.

I have had the separate line for the PC for about 2 years, so it is fairly new, and I really doubt it is corroded. No need to unplug anything else, because there is nothing else.

What has me totally confused is that Thursday night I was able to keep a good solid connection for over 4 hours without a single disconnect.

My problem is not really that I am constantly being disconnected, it is that I am not receiving an answer from the ISP's server. If you look down at my Task Bar, my Yahoo and MSN messenger are lit up, implying I am still connected. The two little monitors are still there blinking, saying I am still connected. But I cannot open any web pages, I cannot send or receive e-mail. And generally after a short period of time, the two IM's will go out, saying I'm disconnected, but the little monitors are still blinking and the PC is saying I am still connected.

I have my Network Connection set up that when disconnected, it is to automatically reconnect. But it cannot and will not do that when there is just enough signal that the PC believes it is connected. And it can be like this for an hour at times. I literally have to tell the PC to disconnect, and make a new connection.

My ISP tells me the problem is with my computer. But if that is the case, then why would my computer connect and remain connected for 4 or 5 hours with no problem one day, and the very next day I can't function properly for 10 minutes without realizing that in actuality I am not connected corrected, even if the PC says I am connected.

Again, thank you for taking the time to try and help.

Cordially,
Sandie

 

Last time I saw that it turned out to be a bad modem. Not fully bad, just gone enough not to disconnect correctly and not to maintain a connection.

Oddly enough it was on a Compaq Presario (Forget the model number, 667MHz PIII though).

A new modem solved it.

 

Hello Oshwyn5,

I have been wondering about that, but I thought it couldn't be the modem if I was connecting and able to function at least any little bit.

I have a repairman coming out to fix my A drive (just discovered it doesn't work. Never tried to use it since I bought the PC until just recently, so it's probably been broken all along. My first Presario had to have it's A drive replace also). If I can, I will discuss this problem with him, and see what he says. If he agrees, he can probably put in the claim for the repair right then.

When I bought my PC (March 2003) I also bought a 4 year extended warranty for it, and boy am I glad!!

Thank you so much for your help,
Sandie

 

Follow-up via email - replaced the internal modem with an external and things are now working perfectly and a little faster than before.

 

Yes Newt,

All is well once again.

I have installed the external modem, and yesterday I was able to maintain a good strong connection for the entire day. From about 10 AM to 8 PM last night. It has been a long time coming, but thanks to great help and good ideas, I am again able to enjoy being on-line.

I waited to come and give the final results because I wanted to make sure it was not just a fluke. But since it would never have done this well before the new modem was installed, I know this is no fluke.

Thank you again, for all the help and support with this problem,
Sandie