I have been trying to get my grilfriends computer to work with Mandrake. She has an ltmodem and Suse now. It works with Suse, but Suse sucks(Uhm, No offense to Suse users .) So I installed Mandrake 10.0 Official,(My favorite.) I played around with My computer for awhile before I was able to get my winmodem to work. I know what I am doing, well, mostly I guess or I wouldn't have this problem, lol. I installed the modem like I did in the post I made explaining how I did it. http://www.linuxquestions.org/questi...hreadid=228177

The problem is this. It recognizes the modem, dials, starts to log onto the network and then the modem hangs up. I am lost yet again. I am guessing there is something simple I have to do, but I don't know what. Any help would be appreciated, thanks.



Webwolf

This is just a wild guess, but if you can get it to successfully dial out and it attempts to connect to the network, then it sounds like you are passing in the wrong ID and/or PW. Just a guess, but if she's on a different ISP, perhaps you've set things up using your login ID and password rather than hers. In short, I'd just recheck the values in the ID/PW fields, also make sure you don't have any trailing spaces and that Caps Lock isn't on, etc. Good luck with it -- J.W.

We both use the same ISP. But just for the hell of it I went over there and made sure I did it all correctly. I tried her account then mine. Neither worked. It dials, logs on to network and hangs up. The log says terminate on code 15, or something similiar to that. Part of me was hoping that I did screw up and it worked, the other part of me is relieved. I would have had to kick my own ass for making such a mistake, lol.


Webwolf

hey webwolf70,
you did ask for a simple suggestion! If you are using KPPP there is a configurable setting for the modem time-out period. I believe it is in the device tab( i am on an XP box at the moment, instead of MDK10). The time-out needs to be longer than the time it takes for the modem to get fully authenticated with the ISP.
w4rth0g

Since we both use the same ISP and live nearby eachother, you would think it would be the same, but.... lol. I found the setting you where talking about. It looks like it goes from 0-60 seconds and 30 seconds is the default. I will give it a try later when I go over there and see if that helps. Maybe her phone lines are messed up and it takes longer for the ISP to get it together. I had a similiar problem in my old apartment. I would dial out on one of the phone outlets and it would be real slow and it would disconnect a lot. I switched to another and it worked fine. Found out the one that was slow had the wiring all screwed up. Let me give this a try and see. Thanks. I really do hope it is something simple, but at the same time it didn't take XP or Suse this long to connect. I will post the results when I try it.


Webwolf

That's a great suggestion w4rth0g, and hopefully it will work. Likewise, if you've got a lot of extra noise on the line, that could interfere with the PC's ability to connect. Perhaps using a different wall jack, or replacing the "modem to wall jack" cable would be worth a try. Good luck with it -- J.W.

Nope. Didn't work either. But it did give me a chance to write down some more info and investigate it further. I think I know why it is doing it now, but I want to check before I post anything.



Webwolf

Ok. This is the message I got;

"The PPPD Daemon died unexpectedly! Exit Status: 10"

The remote system does not seem to answer to configuration request."


So I went to the KDE ppp faq section. I found this. They said to try a couple of things:

"1 - /etc/ppp/options contains the auth option. Simply put a # comment character in front and try again"

2 - Your system already has a default route. Have you set up a local network? In this case recent versions of pppd will be as if the auth had been specified. To override this you may add noauth to the pppd arguments in kppp setup dialog. Alternativley you could take down the local network prior to dialing in."

There is no other network. I tried both and it didn't work. I also disabled the ethernet card in the bios. I then went to the /etc/ppp/options in Suse to see what the differences where. I copied a few more commands and added them to Mandrake. Still isn't working right, this time it is a different error. So I am going back to the origianl /etc/ppp/options in mandrake and add different commands one at a time. It will take awhile to do, but I am close, I can feel it. I am also going to see what my /etc/ppp/options look like and compare the two.

Edit: Here is the link to the KDE KPPP FAQ: http://devel-home.kde.org/~kppp/faq.html


Webwolf

hey webwolf70,
well on the upside, the "simple thing" list is getting shorter! Okay MDK10 has the built-in Firewall, and if I remember correctly it can be configured differently for each network connection. Might be worth a check to see if it is set too high. When I get back to my MDK box I will verify this.
w4rth0g

I am going to un-install KPPP and re-install it. I am also going to un-install the modem source and then re-install that. I am going to write down some ppp commands I can add to the /etc/ppp/options files and try again. If this fails I am going to take the modem out of her older HP and try that one. I hope it is a lucent modem that works with Linux. If I do that I will probably install the modem I take out of hers into my older computer. I really want to get that modem working but I need to get Mandrake set up quickly on her computer. Suse is acting really buggy and now it won't let three out of five users connect to their account. Now I am pressed for time, lol.


Webwolf

hey webwolf70,
keep us informed, as many people will follow any threads pertaining to winmodems. One more little tid-bit, I was able to solve my winmodem issue with information that was gathered from wvdial.
w4rth0g