Thanks to all those who offered suggestions.  Unfortunately, I 
still haven't been able to get things to work correctly.

At 08:05 PM 3/29/99 -0600, Allen Carpenter wrote:

>Check your /etc/resolv.conf file.  You should see something to
>the effect of
>
>domain <isp domainname>
>nameserver <ip address of dns server>
>
>That will be followed by any additional nameservers you have. 
>Most ISPs supply two.
>If you don't see that there you can fill it in yourself.
>
>This file is generally filled in by kppp but I am betting
>wasn't in your case.  Probably
>due to an issue with permissions.  KPPP likes to run setuid
>and cannot write to the 
>/etc/resolv.conf without permission to do so.

   I checked /etc/resolv.conf and it did indeed have the right 
entries.  I also found that kppp was indeed able to write to it.

>Sounds as if you have already discovered the next thing I'll
>mention but just in case:
>Edit the file /etc/ppp/options to remove the line containing "Lock".
>KPPP does its own locking and having the lock there will cause
>the connection to die on you.

   I had indeed already commented out "Lock".

   Someone suggested to me that I try pinging numerical IP addresses, 
and I did so.  Unfortunately the results were the same, but it was a 
good idea.

   To add a bit to my original problem report, I opened kppp's detail 
screen and after watching it while I tried a few pings and telnets I 
saw that apparently there were no packets going either out or in through 
the modem.

   I installed and attempted to use wvdial, but encountered basically 
the same problem.  The modem connected and was able to get me logged in, 
but after that nothing.

   And on a side node, minicom seems to work perfectly well.


Mike

   

--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html

Reply via email to