• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Dialup Connection

Seekermeister

Golden Member
I realize that alot of you have forgotten alot of what you knew about this type of internet connection, but if you think back, you might be able to help. I have a problem that is not all that uncommon...alot of connectivity problems. It isn't really that the ISP is dropping the connection, I can stay connected all day. But even though my dialup connection indicates that it is active, too often, when I click a link, nothing happens, and I have to reconnect to restore operation. I'm not sure about in Windows, but in Linux, I have noticed that this seems to be connected to the DNS server not responding. I have changed from my local ISP's DNS, to Verizon. But this has not helped or changed the problem. I'm thinking that this must have something to do with my settings, or that perhaps I need to use some kind of extra modem string. I have been looking at this for a long time, so just giving me a link to some page about modems in general won't help. But, if someone can dig up a solution from the dark recesses of their memory, I would love to hear about it.
 
Can you give us some more info - when the problem occurs, if you open a CMD prompt, can you ping the web site you are trying to get to? Ping it by IP? Does it happen for all websites? If you do a tracert to a common site (say www.google.com) what happens?
 
I haven't done a tracert on it yet, but when this happens, it is all websites at the same time. I generally have to disconnect and redial to get things normal.
 
Before this happens:

Tracert to www.google.com, and write down the IP's of the hops (especially the end point)

When this happens

can you ping your own IP
Can you ping your default gateway
Can you ping any hops after your gateway
can you ping the IP for www.google.com that you got earlier
can you ping your DNS servers
 
Odd, I tried tracert and it timed out on everything that I tried. I thought that it might be the firewall, so I turned it off, but no change. This happened while I am still able to reach a website normally. As far as the gateway, I'm assuming that you are referring to a router, but I have no router, just my USR modem.
 
ipconfig shows your default gateway


default gateway is the NEXT HOP on the way out, it's what you talk to at your ISP (other end of the ppp tunnel)

do you get IP's on your Tracert, that's what matters. Ping and find which ones reply to pings prior to starting (some will, some won't)
 
I ran ipconfig, and it came back with this:Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

Windows IP Configuration

PPP adapter Dialup:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 4.253.13.26
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 4.253.13.26

I did ping a couple of urls, but they timed out also.
 
I just tried a tracert again, and it is still timing out. I'm going to buy a wireless router tomorrow, which has both NAT and SPI firewall functions, as well as MIMO. Will this router help...hurt, or remain the same?

I also tried using some static DNS numbers that my ISP gave me, and they didn't help.
 
To seekermeister,

I am no networking expert---but it looks like you have windows server edition by the build number---and I have no idea of what sort of network you are running---or if you are running a network at all---and if you are not running a network---why do you need wireless? Nor can I get any idea of how you are configured---and what--other than better speed--you are trying to do.

I have to wonder if you have the right protocols installed to be work with your modem. If your pings are timing out---you either have a bad isp or some
software conflicts inside of your computer--modem interface.

But if you are throwing money at the problem---I'd start with the modem first---but cheap me would first uninstall and then reinstall the modem drivers first.

And if you get any kind of a router---you are going to have to have a modem that works with that router.---with most modern routers assuming they will get a dsl or cable modem.

But given how vague things seem to be---you can suspect your existing router---a bad NIC---or a bad modem.--or some sort of conflict between them or in them.

But if you are just running one computer---I would just get an internal or usb dial up external modem---and chuck the rest of the un-needed junk---and get my protection from a software firewall.

But advice is cheap---but I run a two computer lan just that way---and it works just fine.
 
Originally posted by: Lemon law
To seekermeister,

I am no networking expert---but it looks like you have windows server edition by the build number---and I have no idea of what sort of network you are running---or if you are running a network at all---
I'm running x64, which is built on Windows Server 2003. At the moment, I have no network.
and if you are not running a network---why do you need wireless?
when I buy my router, it will connect the PC and laptop.
Nor can I get any idea of how you are configured---and what--other than better speed--you are trying to do.

I have to wonder if you have the right protocols installed to be work with your modem. If your pings are timing out---you either have a bad isp or some
software conflicts inside of your computer--modem interface.
Possible, but the modem's driver has been fine...at least until now. There wasn't any conflicts before, but if there is now, I have no idea what they are.
But if you are throwing money at the problem---I'd start with the modem first---but cheap me would first uninstall and then reinstall the modem drivers first.
The problem with that, is that the modem is not cheap. Price a USR 5686E external and you might understand.
And if you get any kind of a router---you are going to have to have a modem that works with that router.---with most modern routers assuming they will get a dsl or cable modem.
According to USR, the router would plug into the ethernet port and the modem would plug into one of the routers ports, then into the telephone jack. They claim that a broadband router should be used.
But given how vague things seem to be---you can suspect your existing router---a bad NIC---or a bad modem.--or some sort of conflict between them or in them.
For the moment, we can forget out the router or NIC. If the problem is with the modem, then how would I diagnose that?
But if you are just running one computer---I would just get an internal or usb dial up external modem---and chuck the rest of the un-needed junk---and get my protection from a software firewall.
Forget about an internal modem, I multiboot, and Linux doesn't like most of them. I do have a USB modem in the closet, but it doesn't perform as well as the USR.
But advice is cheap---but I run a two computer lan just that way---and it works just fine.

 
To seekermeister,---who asks---For the moment, we can forget out the router or NIC. If the problem is with the modem, then how would I diagnose that?

Short answer---if the modem is going through the router and the NIC--they become a total package----you can only properly diagnose the modem by removing it from the other two.
And see how it connects all by itself. Or move the modem to another friends computer and try it there---or try it on your lap top---or buy a cheap dial up modem to test your lines.
Or borrow a known good router--or add another presumed good NIC---As you diagnose interactions between components---troubleshooting steps go up exponentially.---and on top of that you are running a 64 bit OS---which is yet another joker in the deck.

At this point---as step one---you have to separately look at diagnosing four things---(1) Your phone line (2) Your existing router (3) Your existing NIC (4) Your existing modem.
 
No router, no NIC. So, it boils down to phone line, modem or OS...the latter being my hunch. I know that hunches don't do much for diagnosis, but I really dislike dragging out my USB modem. So I think that I'm going to let it ride until I install MCE, which is waiting on my new processor to arrive. If the problem continues with MCE, then I will drag out the USB, regardless of how I feel about it.
 
Pleasant surprise! I just bought a ZyXel X550 at CompUSA, because they have a one day sale...regular $69.98 for $29.98. The ad that I had picked up in the store a few days ago, said nothing about an additional rebate, but it had an extra $20 mail-in rebate, so it will only cost $9.98 in the end.

One thought occurred to me. Since I'm connecting a dialup modem to it, will I have to use the same dialup connection as before, or will I have to make another for the ethernet connection?
 
I went ahead and drug out my USB modem, to see if it would have the same ping and tracert problems, as well as possibly using it with my router's USB port. But, apparently the driver is not x64 compatible. So I went to the CompUSA website, since it is a CompUSA modem, to attempt to find a driver update. I couldn't find anything for any of their products. Although the link that I found was supposed to include email support, the only thing that I actually found, was a telephone number, which I bet is for some kind of premium support. Does anyone know of a driver that is x64 compatible, that would work with this modem?
 
Back
Top