>Well I used your script to deal with a ISP here ( which I know
>they show login/passwd prompt ), it does not connect; while
>if I used my script which does the manual authentication, it
That page will show how to get log data. Did you remember to set the
'user mingching.tiew' option to pppd, so that it knows who to say is
calling? Did you set up /etc/ppp/pap-secrets correctly?
Quote:>So my question now is how does Windows does it if it does
>not send login/password ?
DUN (the tool where you fill in the blanks, then press the OK button
_before_ the modem dials, and you do nothing further to get connected)
can't use scripts. Are you using some other application?
Quote:>I suspect the chating capability in Windows is far more smarter
>than the 'chat' program on Linux, ie it looks for login/password,
I would doubt that _very_ much. You don't identify which version of
windoze you are using, and each version is different with how you set
up a log, but you should look at that. Here are three suggestions
I've seen used to set up logging in windoze. These are copies of
a series of Usenet posts - so watch the quoting levels:
Go to Control Panel/Modems/Properties/Connection/Advanced. Check Record a
Quote:>system called Modemlog.txt. Can't find it. Any suggestions?
That's the file name in Windows 95. Windows 98 uses the modem's name
as the file name. For example, mine is:
C:\WINDOWS\U.S. Robotics 56K FAX Win INT.log
c:\windoze\ppplog.txt file (very large)
In your DUN folder, right click your ISP's icon and choose Properties.
Select the Server Types tab. On that window, you should ONLY have
Enable software compression checked, and TCP/IP in protocols. You
will see a box that says Record a log file for this connection. That
box, if checked, will start the ppplog.txt file. It can be used for
troubleshooting serious protocol problems, but most users will never
need that log. A word of caution, don't post that log without first
editing out your login and password information, which appears in
plain text. If you don't have a check in that log box, and you do
have a ppplog.txt file, check it's date. It can be deleted if is
Quote:>Try turning on PPP logging. I'm not sure offhand how to do this in XP;
>you might try the Win2k method:
Yes, that's it, it also works in WinXP Pro.
Quote:>if present, it assume manual authentication; otherwise it does
>pap/chap; something which the Linux chat program cannot do.
>Perhaps wvdial does it.
Searching the newsgroups comp.os.linux.networking and comp.protocols.ppp,
you will find that this often fails. As mentioned, ISPs set up for
windoze using PAP authentication, and ignore the text based login. This
is because that requires a login _shell_ on the terminal server, and
that's extra work to set up. Additionally, most windoze users wouldn't
know what to do once they sent a login/password, unless the ISP auto
starts pppd. So, given that authentication is built in to pppd, why
should the ISP worry about doing it the hard way?
As for wvdial - it defaults to looking for a login prompt and this sometimes
leads to failure, which is why wvdial includes a "stupid mode". The author
of that application is living in the 1980s, and hasn't recognized that
windoze killed the login prompt method. See the man page.