From: "S. Massy" <theanaloguekid@tak.net.dhis.org>
To: blinux-list@redhat.com
Subject: Re: problems connecting to ameritech.net dsl: debugging trtried
Date: Thu, 6 Sep 2001 10:10:49 -0400 [thread overview]
Message-ID: <20010906101049.A8216@tak.net.dhis.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0109060602200.27009-100000@ns.shellworld.net>
On Thu, 06 Sep 2001, Cheryl Homiak <chomiak@shellworld.net> wrote:
> Ok, first I tried going into the ppp/options file and setting a debug
> level but that didn't put any more information into syslog. When I tried
That must be because messages with the debug priority aren't configured to be written to /var/log/syslog. Look whether you have something like /var/log/debug or /var/log/ppp where those messages might already have been redirected.
If all else should fail add this line to your syslog.conf:
daemon.debug -/var/log/ppp.log
(note: the pppd manpage says debug logs to daemon.debug but for some reason it logs to local2.debug on my system, so it might also be the case for you.)
> typing pppd debug I was told "the remote system is required to
> authenticate itself but I couldn't find a suitable secret password for it
> to do so. None of the available passwords would let it use an ip
> address." If this is talking about my password with ameritech.net, I
> checked what I have in pap-secrets and it's the one ameritech claims is my
> password, though it's not the one I tried to put it in the system so it
> must be a default one. Any more ideas? I do try to research things and
> read info and man pages, but if you tell me to do something it might be
> wise to tell me how to do it. Thanks.
> One thought: is the dsl system completely separate from the ppp/dialup
> system? If not, I was wondering if I could try accessing it through the
> access number by ppp to see if my user id and password really work. The
That would be a very good thing to do, since so far the connection itself seems to work fine, it seems the authentication process might be where things go amiss.
> interesting thing is that when I try sending email to my supposed new
> email address, I get it back as undeliverable. Maybe they don't activate
> your email until you actually log in for the first time? I don't know.
Maybe... But still, that sounds suspicious, usually your e-mail address should be deliverable as soon as your account is set up.
>
> Cheryl
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Cheryl Homiak
` S. Massy [this message]
` Janina Sajka
` Cheryl Homiak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010906101049.A8216@tak.net.dhis.org \
--to=theanaloguekid@tak.net.dhis.org \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).