You are not logged in.

Kinternet Configuration Problem with SuSE 8.2

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

tomlin

Beginner

  • "tomlin" started this thread

Posts: 1

  • Send private message

1

Wednesday, May 7th 2003, 11:37pm

Kinternet Configuration Problem with SuSE 8.2

I've just installed SuSE 8.2 Professional, and I can't get onto the Internet using a dial-up modem. I initially tried Kppp, then switched to Kinternet - per SuSE's recommendation.

(Beyond this advice, SuSE will not offer any specific installation help for their bundled applications, despite YaST's integrated installation/configuration control over the applications).

However, my modem seems to be configured correctly and functioning, but the Web browsers I've used (Konqueor and Mozillia) fail to connect with the server. For example, the modem dials and negotiates a connection with the IP server, as evidenced by the Kinternet Log file: "Using interface ppp0 [and] pppd: Connect ppp0 <-> /dev/ttyS1".

But I've noticed from the YaST Modem dialog window that the modem is listed as follows: "/dev/modem" The differences between these parameters, from YaST and the Kinternet Log, look to me like a possible conflict, specifically with regards to "/dev/modem" parameter (YaST Configuration) and "/dev/ttyS1" parameter (Kinternet Log). If this is so, I have no idea how to resolve the conflict, either by using YaST or the Kinternet configuration resources, or in particular, by using shell commands.

If anyone can shed some helpful insight on this problem, I would appreciate it.

Thanks.

Rinse

Professional

Posts: 797

  • Send private message

2

Sunday, May 11th 2003, 11:07am

/dev/modem is always a link to the actual port, in your case /dev/ttyS1
If the connection works properly, but yor browser can't resolve hostnames, then there is probably something wrong with your dns settings.
You can figure that out by sending a ping to an ip address.

Rinse
Help mee om KDE 3.5.5 in het Nederlands te vertalen