Re: And Now, From Work...

From: Vulpine <vulpine_at_mac.com>
Date: Tue, 22 Nov 2005 10:56:08 -0500

(Former ISP service tech and avid Apple user here.)

Up to a point I agree with the two other techs who responded. It's
clearly an issue either with the modem settings or the lines in your
area. However, I subscribe to the K.I.S.S. policy of tech support.

First: I agree with Tribble in checking the line quality in your
home. Pick up the phone and dial a single digit (other than zero
(0)). Listen to the receiver. If you hear any hiss or static, that's
an indicator of badly weathered or squirrel-eaten phone lines. Call
the phone company for repair, BUT don't tell them it's for an
internet connection. Tell them it's so bad that you can't hear people
talking on the other end half the time. They'll get right on it. If
you tell them it's for the Internet, they'll tell you they only
guarantee a 14,400bps connection and hang up on you.

Second: Again I agree with Tribble than a software-controlled modem
such as a Winmodem quite often gets corrupted drivers. In this case,
depending on the version of Windows you are using (will assume XP),
follow these directions.
        Right-click on 'My Computer' and select 'Properties' at the bottom
of the menu.
        Look for and click on the tab labeled 'Hardware'.
        In the section labeled "Device Manager" click on the button of the
same name.
        In this list, look for "Modems" and click the plus symbol next to it.
        Right click on the modem name (in my case the name is 'U.S. Robotics
56K Fax PCI) and again click on 'Properties'
        Click on the tab labeled 'Driver'

Now, here's where you can do one of two things. If you still have the
driver disk for your modem, then click 'Uninstall', Ok the window and
reboot your machine. When your machine 'Finds new hardware' on
bootup, cancel the wizard and run your disk to reinstall. That should
be all it takes. Windows should still have all your account
information in the Network Properties and you should be able to dial
up as usual (without the endless retries.)

On the other hand, if you don't have the disk then you will have to
try letting the machine figure it out for itself.
        First, make sure you've got a reasonably reliable connection to the
internet already dialed up.
        Click on 'Update Driver'.
        The Hardware Update Wizard will pop open and ask "Can Windows
connect to Windows Update to search for software?" Select 'Yes, this
time only' (assuming you have a legitimate copy of Windows) and click
Next.
        The next question you want to choose "Install the software
automatically" and again click Next.
        Your machine will now run for several seconds and either tell you it
was successful, whereupon you will select Finish and be done with it
OR it will tell you it cannot continue because the wizard could not
find a better match than the software already installed at which
point you have to either go Back (if you know where the drivers are
on the machine) or Finish (assuming you don't). I choose Finish.

On to the next step if the latter choice (and the one I really expect
if you don't have the installer disk.)

        Assuming you're still dialed up, you should still have the
Properties of your modem window open. This time, click "Uninstall." A
warning window will likely pop open to say you're about to uninstall
the device from your system. Click "OK."
        This will return you to the Device Manager window where 'Modems'
should now be missing.
        On the menu bar at the top of the window, click 'Action' and select
"Scan for hardware changes"
        With luck, the computer will quickly find your modem and install a
new set of drivers for it.

At this point, I recommend rebooting the computer and trying to
connect. Your modem should now be able to train a connection on the
first try, and possibly a faster connection than you've been able to
acquire for some time. With software modems, I learned that doing
this whenever you had to redial more than twice usually -- but not
always -- fixed the problem.


This is the cheapest fix.
If you can afford to pay something over $100, then look for a good
hardware-based modem. And if you're willing to buy the best, then
look for the USR Courier 56K V.92 business modem model number 3453b.
Expensive, but one of the most solidly-reliable analog modems on the
market with an outstanding warranty package. Until lightning took my
Courier out -- the second time -- this is what I used and saw far
better performance than any modem I've used since. Yes, USR actually
repaired it the first time under warranty, though I had to pay
shipping charges. Since then I've managed to go with a cable modem,
finally. (Had to pay almost $200K to get it too. Then again, that's
what a new house costs around here these days.)


Good luck with your eyes and keep us all entertained with your
excellent artwork.

David Fields
vulpine_at_mac.com
DeltaFox Technologies
www.deltafox.com







On Nov 22, 2005, at 06:23, SkunkworksAMA_at_yahoogroups.com wrote:

> Date: Mon, 21 Nov 2005 17:52:47 -0000
> From: "Take a wild, friggin guess" <a_change_of_plans_at_yahoo.com>
> Subject: And now, from work...
>
> Hey all-
> Tried getting online this morning (made about 20 tries over the
> span of 2 hours). Are there any folks in the group who can explain
> why I can't seem to get the right connection? The modem dials in,
> and it says I'm online, but under status details, it only says "184
> bytes received", and that's all I can get. No webpage comes up (I
> get a message saying "Cannot find server"). Is it coming from my
> end, or my ISP's? It's seriously beginning to piss me off. A lot.
> It's not like I get online all that often; I'd like to be able to
> friggin' connect when I get the opportunity to actually get online.
> Any ideas?
> I'm going to use the remainder (about 10 minutes) of my lunch break
> to read through some of the messages and make notes of which ones
> need replies. Since I'm on DSL now (at work), I'll be logging on
> whenever I get the chance to do so, in an effort to finish up what I
> tried to do this morning.
> So, once again, here we go...
>
> --JMH
Received on Tue Nov 22 2005 - 07:57:21 CST

This archive was generated by hypermail 2.3.1 : Sat Nov 30 2019 - 17:52:08 CST