Just installed Suse 9.0 professional and made my serial modem work without any problem. But whenever I'm trying to connect to my ISP using kinternet or kppp it fails in the middle of the process. It seems from what I've found out of the logs that kinternet fails in the password prompt part. It sends my username and password thrice but seems that the server denies and prompts for them again. After the third attempt, it said in the kinternet log something like: "Don't know what to do, starting pppd and hoping for best."

Then it says serial connection established and something like ppp0<-->dev/modem but still I'm not connected, and the kinternet icon remains the same as its trying to connect.

I'm newbie and totally confused, so any help would be appreciated.

I had the exact same problem with SuSE 8.2, and I had to use a program called wvdial. It's located in /usr/bin. Before you can use it, you have to log in as root in the console and use pico or some other file editor to edit the wvdial.conf file to put your ISP information in. The wvdial.conf file should be located in the /etc directory. Make sure that after you've edited the wvdial.conf file, you change the wvdial.conf file's permissions so that you don't have to log in as root in the console just to connect using wvdial. You can accomplish this by typing "chmod o+r wvdial.conf" right after saving the file when you put your ISP information in it (make sure that you're still in the /etc directory before doing this, otherwise you'll have to include the /etc directory in the chmod command). That way you can dial into your ISP using wvdial while in the console without having to log in as root unless you need to change the wvdial.conf file. Keep the console window open (you can minimize it if you want) while you're online and then close it when you're done.

Great! Thank you very much, Dhimani. Now I'm connecting from linux and can set myself free from another aspect of MS.Shitloads.

But I just wonder why I couldn't connect with other programs (KPPP and Kinternet)? What was the problem with them? And is there any way to configure them to work properly? I'd be more grateful if someone tell me these.

I believe that it has to do mostly with your/my ISP. As it was explained to me, a lot of ISP's use a Win NT based system and sometimes has problems with dialers like Kinternet. Kinternet sometimes cannot pick up the prompts for username and password like wvdial can. I admit that having to use the console to connect to the internet can be a pain, but it also gets a more reliable connection and is just one of the idiosyncracies that one has to deal with using Linux to interface with a winblows system. Anyway, I'm glad that I could be of assistance. Happy computing!!

You're right, consoling is better and much more reliable, excetp for the fact that there's no data rate diagram/icon/window/etc.*darn*

Ah, and I couldn't connect with wvdial with any user other than root, wether editing the user permissions for wvdial.conf (and almost every other aspect) or not. It dialled the number, but then gave an error in the middle of the process and disconnected.

Hmmmm, that's odd. Well, I'm gonna check that one out here; I swear that's what I did. In the meantime, it won't hurt to log in as root to use wvdial, just be really careful what you're doing of course.

This is what I get when trying to connect with another user:


--> Modem initialized.
--> Idle Seconds = 300, disabling automatic reconnect.
--> Sending: ATDT8271771
--> Waiting for carrier.
ATDT8271771
CONNECT 57600
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Fri Nov 21 16:54:34 2003
--> pid of pppd: 2230
--> Disconnecting at Fri Nov 21 16:54:34 2003
--> The PPP daemon has died: No root priv error (exit code = 3)
--> man pppd explains pppd error codes in more detail.
--> I guess that's it for now, exiting
--> The PPP daemon has died. (exit code = 3)