Re: hopefully simple ppp dns or routing problem on Slack 9.1
From: John Gabriele (john3gz_at_bestwebz.net)
Date: 04/25/04
- Next message: Stephen Zilliox: "Re: Slow browsing with cable modem"
- Previous message: volkman: "Re: who can fix a proftpd.conf problem"
- In reply to: John Gabriele: "Re: hopefully simple ppp dns or routing problem on Slack 9.1"
- Next in thread: Clifford Kite: "Re: hopefully simple ppp dns or routing problem on Slack 9.1"
- Reply: Clifford Kite: "Re: hopefully simple ppp dns or routing problem on Slack 9.1"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 25 Apr 2004 13:33:12 -0400
John Gabriele wrote:
> Clifford Kite wrote:
>
>
>>
>> The only thing I can think to do now is use minicom to dial in and see
>> what, if anything, the ISP displays. A desperation measure. :(
>>
>
> Thanks for all the help Cliff (and Bill, if you're still reading :).
> I'm going to try a few more things, google around a bit more, and maybe
> contact a few folks. If I ever get this thing working, you and Bill will
> be the first folks I tell about it! :)
>
> ---J
> --- remove zees if contacting via email ---
>
EPILOGUE
I spoke with my ISP's tech support again. The fellow said that you can
use a login chat script method of logging in when you dial up, or else
you can use PAP. You dial the same telephone number for both. I asked
him how the other end knows whether I'm using a login script or PAP,
but he didn't know the answer (and wasn't interested in finding out).
Well, unfortunately, that was it. I really needed to just get back to
work. Since the Slackware install was very recent, I pulled out my
Redhat 9 ("Shrike") CD set and wiped the whole thing, installing RH9.
RH9 comes with some redhat-config-* internet setup wizard that helps
you get set up right away with a simple point-and-drool interface :) .
Turns out that it was confused a bit (maybe the Fedora folks have fixed
it by now) and was insisting on using its own seemingly random dns
addresses in a 2nd (2nd to /etc/resolv.conf) resolv.conf located in
/etc/ppp. After changing those first in the GUI network wizard and then
manually, DNS was working and everything was fine.
Moral? Dunno. Maybe my Slack install had some corrupted file. Maybe
I was making some obvious mistake that never got uncovered in this
discussion thread. Maybe Slack's ppp integration needed more testing.
Anyway, I'm back online with a GNU/Linux setup and getting my work
done again. I also plan on having a look at the next Fedora release.
Thanks.
---J
- Next message: Stephen Zilliox: "Re: Slow browsing with cable modem"
- Previous message: volkman: "Re: who can fix a proftpd.conf problem"
- In reply to: John Gabriele: "Re: hopefully simple ppp dns or routing problem on Slack 9.1"
- Next in thread: Clifford Kite: "Re: hopefully simple ppp dns or routing problem on Slack 9.1"
- Reply: Clifford Kite: "Re: hopefully simple ppp dns or routing problem on Slack 9.1"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|