I've had the same problem and isolated it further: the problem is related in some way to kppp's ability to properly connect to DNS service. I can consistently reproduce this problem as follows:
1. Start or restart the computer running Red Hat Linux 8, 2.4.18-27.8.0.
2. Use kppp to connect to Earthlink via dial-up. Linux dials out and the connection is established.
3. Open a kterm window and run "/sbin/route -n". Linux displays the route. Note however, that if the "-n" (numeric) is omitted, the route command hangs.
4. In the kterm window, run "vi //etc/resolv.conf". Two DNS servers are listed: 207.069.188.185/186. These DNS servers are Earthlink's default servers.
At this point, I've repeatedly verified that "ping" can reach network resources by IP address but not by symbolic URL. DNS service isn't properly connected.
5. Disconnect the kppp-based connection.
Now let's use Gnome to connect.
1. In the kde Start Application menu, choose System Tools | Network Device Control. Ghome displays the Network Device Control dialog box.
2. If one is not already defined, use Configure | Add to add a "neat" dial-up connection of the same number as that used in step 2 at the beginning of this post, then Activate the connection. Linux dials out and the connection is established.
Note that at this point proper DNS functioning is achieved.
3. Verify that the general information about DNS is the same as that received by kpp. Use "vi /etc/resolv.conf" to view the list of known DNSs which should be the same as those seen in step 4, above.
4. Use /sbin/route and ping to verify that symbolic connections are available: DNS service has somehow been made to work by "neat" where it didn't with kppp.
5. Use the connection to view the Internet or retrieve e-mail.
Here's where it gets interesting.
1. Disconnect the "neat" connection. In the kde Start Application menu, choose System Tools | Network Device Control, then Deactivate the device activated in step 2, immediately above.
2. Repeat the kppp connection sequence. At this point kppp receives proper DNS service. This remains true until the next time the computer is restarted at which point kppp can only be "fixed" by yet again using "neat" to connect via dial-up.
If anyone has any additional verification steps that I can perform, please post them here. I'm relatively new to Linux but otherwise understand computer usage in general and can follow instructions. I'd be interested in figuring out:
- Why kppp doesn't want to use DNS even though they're "captured" in the /etc/resolv.conf file at the time of connection
- Why "neat" clears this problem for the remainder of the logged on session
Cheers & hope this helps,.
R. Bruce