KPPP is a front-end to run the PPP daemon, but uses its own config file (
~/.kde/share/config/kppprc) to pass some (but not all) parameters to the PPP daemon. KPPP is not associated with the ppp-go script. In other words, you have to configure both tools individually.
The routing table comes into play only after you have connected. That is, if the routing table was hosed you would be able to connect but not access the net. The ping command will tell you if the routing table is suspect, but first you need a good connection. If your box is stand-alone and not on a network, the PPP daemon should be able to automatically configure the routing table after connecting to your ISP.
Similarly with the firewall. The iptables firewall will not prevent connecting to the ISP but could prevent traffic to that IP address.
Similarly, manually configuring
/etc/resolv.conf with your ISP DNS servers comes into play only after you connect.
But you are not getting that far in the process.
I'll take a first guess that you have KPPP and PPP configured to authenticate the ISP server. The ISP server will attempt to authenticate you, but normally you do not want to authenticate the ISP server.
Try adding the
noauth parameter to
/etc/ppp/options. FWIW, here is my options file:
asyncmap 0
noauth
crtscts
lock
modem
noipdefault
passive
debug
usepeerdns
defaultroute
/dev/modem
115200
name "username" <-- replace username with your own ISP account name
For KPPP, use PAP/CHAP.
You seem to have configured your ISA PNP modem okay, but for future visitors of this thread, the following might be of interest:
Configuring a Plug-and-Play ISA Modem
I hope this helps.