View Full Version : HELP! More 56k modem problems! :(
MoonMan
January 30th, 2003, 04:27 PM
Ok remember back when my modem wasn't connecting at it's average speeds? Well now it isn't connecting at all OR in the extreme rareness actually connects but only for like 1 minute.
It isn't making normal sounds either. It will do the normal dialing up, and then start making low to high sounds that sound nothing like the original sounds.
I have tried other numbers and even a different internet service with nothing. I have unplugged other phones and other lines and even hooked the phone line straight to the computer rather than through the surge protector. There is no call waiting (there is an automated services though), no extra services, nothing.
I think maybe my internal winmodem has finally died... Please help!
Oh and I have an AMD Athlon processor 1.3ghz, 384 SD RAM, Windows 2000 pro with all of the latest service packs, 56k v9.0 internal winmodem that came with my computer. Any more info needed will be provided as soon as I am able to read the replies.
I am at a buddies house and on his computer, so I am pretty desperate.
On a side note, he has an internal winmodem that works, but he has cable so never uses it. Would I be able to unplug it from the motherboard or whatever it is connected to and plug it into my computer if I am able to find the proper drivers for it? Would the drivers I have already work?
ANY help would be appreciated! Thanks!
MusikBeatz23
January 30th, 2003, 04:39 PM
MoonMan if i where you i would try disbeling your firewall until you connect i had that problem before disabled my firewall and i was connected but then i enabled it again and i stayed connected but i updated the firewall version and i stopped having that problem.... try it you have nada to loose.... :fire
MoonMan
January 30th, 2003, 04:41 PM
I do not have, I repeat I do not have a firewall enabled.. and I do not think it has anything to do with it. I have NO software that is disabling my modem, multiproxy is disabled even though it has nothing to do with it, and nothing else is stopping my modem from working.
Thanks anyway dude.
Dark Messenger
January 30th, 2003, 04:54 PM
this site might help you http://www.net-boy.com/
my biggest recommendation is to lose the winmodem and get a regular fax/data modem even better get one that says on the box it will work with Linux (in case you ever decide you want to go that route...switching to linux).
Read the part on the link i posted about 'software modems' and hopefully it will be obvious for you. :-)
MoonMan
January 30th, 2003, 04:59 PM
First of all, I do work with Linux so I will check out that article.. just to get that out of the way.
Now... money IS a problem for me. I have no spare money to spend, and I have noone to spend money on me.
I just want someone to point me in the right direction, tell me why it isn't working/tell me how to get someone elses win modem to work on my computer, or at least tell me there is no other way but to spend money. I appreciate your help DM, but there is no money I can throw at this problem.
Thanks anyway.
don webb
January 30th, 2003, 05:16 PM
This happened to me alot when I was on dail up ! It only happend during bad (wet) weather. Somehting to do with the older lines out her in the back woods....
How has the weather been in your area ?
Just a suggestion. Good luck
jonny5
January 30th, 2003, 06:37 PM
Usually if i pick up my phone and hit a number, there will be no dial tone so you can check to see if there is static in the line. That's the best way i know of how to check for that.
Ya winmodem's aren't that good.. i would recommend a US Robotics 56k fax pci modem. They're pretty good.
Hopefully you get it all sorted moony
CCSDUDE
January 31st, 2003, 12:46 AM
Well, I've had to deal with Lucent Winmodems often....here are afew reasons for the disconnects that I've found.
1) Line noise...like if you have a digital answering machine or one of the phones hooked up to that line has a bad connection or the receiver button is corroded. So slight movements make it crackle on the line thus the disconnects.
2) Outdated firmware....the original 'firmware' for the Lucent was always trying to connect at 56k and had a low tolerance for noise so it booted 'em off a lot. Or you could try setting it to connect at 36kb or setting the max connect rate in the string crap for dialing up.
3) Someones trying to call all the time...lol
4) Broken Winmodem drivers, try updating 'em or removing the modem via system in the control panel then reinstalling the modem via the 2k disc or whatever drivers you need off whatever.
That's all I can think of off the top of my head, I'll dig around a bit and post back if this doesn't solve it.
Peace, dude.
MoonMan
January 31st, 2003, 02:04 PM
First of all... thank you all for responding.. but I may have overreacted toward the situation.
Although it has nothing to do with my services (I tried many), I think the wireing or something in my house does not like bad weather and cannot handle a connection during it (although it can handle phone calls).. the snow seems to have melted and when I tried to sign on it connected almost without a hitch.
I am going to invest in cable when I get the chance and have some spare money but for now, I guess I will just have to deal with this unreliable piece of crap.
Anyways, thanks everyone, and peace.
Krell
January 31st, 2003, 02:13 PM
don webb had the closest answer this round folks.
Wet weather wreaks this havoc ALL across our country. The best you can hope for, is to disable the v90 attempts, and try to connect at a lower setting, maybe change your port speeds to a lower setting also.
I am telling you for a fact that using download accellorators and 3rd party utils will not help you defy basic physics.
In all cases, and on all days, eliminate the obvious culprits, too many phone devices, too much phone line length, having your phone lines near a lot of other electrical cords (this will bleed rf interference terribly)
There may also be too many physical connections between your modem and the Central Office, and too much distance in between.