OK, I took my slackware box to work to run updates on it (faster connection). So installed a 3com network card. Found the card ran 'netconfig' and configured my nic to reflect the network, got on the net works perfect. Take it home (i ONLY have dial up). I can't get connected, kppp just looks on dialing and if I do the 'cli' ppp-go it dials and I get connected I can't get anywhere. Any suggestions on how to fix this? I also re-ran 'pppsetup' to make sure that was re established.

Any input would be greatly appreciated!

If you setup a static IP using netconfig, it placed the commands in the /etc/rc.d/rc.inet1 file. I would suggest:

chmod 000 /etc/rc.d/rc.inet1

After rebooting that would disable the networking interface. But I would assume that it should also fail anyway, once you removed the NIC card because the driver would not be loaded. If you removed the card. To renable for the office use 655 for the permissons and reboot.

Another item that netconfig changes are the settings in /etc/resolv.conf for the network DNS servers. If they are private IP addresses for your network then they would not work from home, even if you were connected properly. Your ISP should assign DNS servers when you login and pppd should update the file as they are assigned. However, the permissions may have been changed on the file preventing pppd from setting it. So you might want to edit the file and enter your ISP DNS server assignments. Removing the move, or renaming it if you want to keep it, might also allow pppd to create the file.

Take a look at those two items and see if they resolve the issue.

Another thing to consider is if your default route is setup correctly. You can check by typing route -n.

Once connected, you'll have a gateway for your ISP network. Look for your 0.0.0.0 network. It's gateway should be set the same as your ISP gateway. Your individual local networks should have gateways of their own, if you have any at all.

After that, start with pinging IP addresses of destinations you know you can ping out on the internet. Then try hostnames. That effectively tests first for connectivity, then for resolving DNS. After you ensure both of those are good, you can browse the web or whatever else it is you want to do.

Wow! Thanks guys. I'll give this a shot this weekend. I'm sure this will get fixed up from what you all suggested. I'll report back!

Thanks!