Red Hat Bugzilla – Bug 57313
PPP Dialer NOT Dialing
Last modified: 2007-04-18 12:38:38 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)
Description of problem:
I recently upgraded from RH 7.0 to 7.1. Now the PPP Dialer applet does
not attempt dial my ISP. After selecting my ISP, it just spins its wheels
for several seconds, fails, and then presents the usual tiny status window
with the big connect button. However, if I go into the Dialup
Configuration applet and click on the Debug button after selecting my ISP,
it dials up my ISP and connects perfectly. (In fact, that's my workaround
until I can get this PPP Dialer issue resolved.)
I did notice that two ppp-watch processes are kicked off when I attempt to
use the PPP Dialer program to connect to my ISP. I've seen some
references to similar ppp-watch issues, but I haven't seen anyone
specifically address the PPP Dialer applet.
Thanks for your help.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Invoke the PPP Dialer applet from Start|Programs|Internet
2. Select your usual ISP
3. Click the button to connect
4. When prompted for verification, click OK
5. Progress bar will flitter back and forth, but nothing will happen for
6. Dialer will time out, displaying a message box indicating failure.
7. Click OK.
8. The standard tiny progress window with the big connect button (green
dot) will pop up, acting like nothing has happened and waiting for you to
try to connect.
9. Clicking the connect button at this point will continue to result in
Actual Results: PPP Dialer will never dial the ISP.
Expected Results: It should have dialed and connected, just as it did in
Invoke the Dialup Configuration applet and select the connection line for
your ISP. Click on the Debug button, and the applet will dial up the ISP
and connect without a hitch ... which is exactly what it should do. For
some reason, the connection works here, but not through the PPP Dialer,
which looks at exactly the same connection data.
Please verify this with a newer version of Red Hat Enterprise Linux or Fedora
Core and reopen it against the new version if it still occurs.
Closing as "not a bug" for now.