//flex table opened by JP

Click to See Complete Forum and Search --> : any1 have any ideas on why my friends lucent winmodem stopped working


bigslammer
01-04-2000, 04:07 PM
I've tried everything for him. new drivers, new phone cord, removed and installed dial up adapter and tcp/ip dial up. it dials then says error 678. what is error 678? device manager says everything is a OK. did his modem just die? and yes I know winmodem aren't great but I too have a lucent winmodem and I download and connect at 53,333. so it's not really all bad. thx http://www.sysopt.com/forum/smile.gif

theCorvetteDoctor
01-04-2000, 06:04 PM
Sounds like you got about all bases covered,, I think,, did ya remove it in device mgr and see if it showed up on re-boot? Or, in control panel> modem>diagnostics, hit "more info" this runs a full test. lotsa luck

Susan
01-04-2000, 06:30 PM
Yes, DO run the diagnostics under more info. It will show if there are any small errors.

bigslammer
01-04-2000, 10:38 PM
yes ran the diagnostics and removed it. windows detects and installs then the diagnostic say everything is a ok. everything looks fine in device manager. only thing is that his family members might have installed some third party software that he doesn't know about. everything that starts up in "msconfig" seeems normal and ran "sfc" and no files were corrupted. only thing I can think of is that either his modem went "bad" (but I hear it dialing" or the phone company was working on the lines and something terrible went wrong(but we do get a dial tone). http://www.sysopt.com/forum/smile.gif

Target
01-04-2000, 10:55 PM
If you look, when the 678 error message appears, there should be a description of the error in the window underneath it.

You might try to update the drivers/firmware for the modem as well. Current Lucent LT Winmodem drivers are version 5.66

The firmware update will de-install your modem and re-install it with the updated driver/firmware. You simply run the *.exe file to perform the whole deal.

I'd give that a shot, then try it again. Keep in mind, depending on how old your current driver is, that when the new one is installed, it might change the name of your modem. You will have to account for that configuration change in your dial-up properties if the update changes the modem name.

Onslaught
01-04-2000, 10:56 PM
Call me I may know and it may be so simple.

bigslammer
01-05-2000, 01:19 AM
ok I'll take you up on it onslaught. yep almost lost my tennis match tonight with the village idiot(you know who). luckily the lights went out whew. http://www.sysopt.com/forum/smile.gif you should play him tomm night.

bigslammer
01-05-2000, 01:24 AM
target yeah I've tried 566, and 554. no go on either one. actually through trial and error I believe 554 works better and it also works better in NT. thx though. I think something is either wrong with the line or the modem. belated y2k prob? :0

bigslammer
01-05-2000, 02:46 AM
oh yeah I also remember that I heard the modem dial in but it never got to the "verifying username and password" dialog.

Red Rage
01-06-2000, 11:55 PM
Error 678 is "There is no answer"

If you hear the modem tone skip to farther down.

check the dial properties

got to modems in control panel then dial properties on bottom. make sure they are all right and double check the phone number.

Here are some init string to try if you get the modem tones.

LT 56k Flex - AT&F&C1
LT Win 56kflex - AT&D2&C1X4V1Q0S7=70W1\N3&Q5&K3S38=0
LT Win - AT&FX
LT Win 56Kflex - AT&F
LT Win 56Kflex - AT&F1&W^M
LT Win 56Kflex - AT&FS=S10
LT Win 56Kflex Enabled - S38=1
LT Win 56Kflex Disabled - S38=0
LT Win V.90 Enabled - AT-V90=1
LT Win V.90 Disabled - AT-V90=0

I've noticed a simple AT&F or AT&FX does the trick most of the time. Some times for what ever reason (usually line conditions) disabling V.90 will allow a user to connect.

Hope this helps,

~Red

bigslammer
01-07-2000, 12:02 AM
thx http://www.sysopt.com/forum/smile.gif I'll give it a try

Axel
01-07-2000, 06:42 AM
A few other questions for you -

Most WINmodems (and I do hate them, btw) are PCI which brings me to the question - when you were in device manager, did you go down into the system drivers and check out the PCI bus drivers for any conflicts?

How are the IRQ's looking on the system? - Any conflicts there?

WINmodems use CPU resources - does he have a different CPU than you do? - is it much slower? - is it a CYRIX on a VIA I/O mobo?

As you are getting a no answer/response message - the above probably has nothing to do with the problem, but it's worth checking just in case.

Next - have you deleted and rebuilt the dial-up connection to the ISP under <my computer> <dial-up networking> - try that. - then find a second dial-up number, doesn't have to be local or 56K - just for testing - manually build another dial-up networking connection to the second number and try to connect.

In case it's line noise, drop the connection speed setting in both modem properties and the dial-up connection down to 14.4 and attempt to connect.

If the second number works - call the ISP and report the number.

If the lower speed works, call your friend's phone company and report line noise - there may be something wrong locally or in your friend's local central office they have to fix.

[This message has been edited by Axel (edited 01-07-2000).]

Squirrel
01-07-2000, 08:21 AM
My theories are on the same line as Axel.

I don't know how your phone systems work in America, but here in England you are limited to the amount of peripherals you have on a single line (called REN, residential systems are limited to something like REN4)

I have come across a problem once where someone had added another phone extension to their house and found that strange things were starting to happen, including the modem having very strange errors,no dial tone, ringing when dialing ect. (xfiles or what..)

Simple solution, but strange if you've never come across this before.

Just another possibility for you..

Comtech
01-07-2000, 08:31 AM
Error 678, the phone you are dialling in to is not answering, check the phone number and dial again. Kinda self explanatory.

bigslammer
01-07-2000, 03:02 PM
oh it turns out the phone company was jacking around with the phone lines and finally got it straight today. everything is up and running fine. geez I feel like an idiot for not checking with them the first day. oh well thx for the help.

theCorvetteDoctor
01-08-2000, 12:42 AM
In regards to the IRQ issue, I got a new BB unit and the wierdo on-board modem shares irq 10 with PCI steering and I can't change it. Under conflicts, it says "no conflicts". BTW, the modem won't work, installed a ISA modem, works fine?? thanks DrVette