Discussion Locked

Connected but unable to browse ,ping?

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Mine is problem of configuring ppp in Red Hat 6.2.

I used kppp and supplied all info : dns, login, passwd.

I am able to connect to isp but unable to browse. Whenever i try any site i receive a msg "UNABLE TO FIND SERVER www..... PLEASE CHECKSERVER NAME" or "UNABLE TO FIND HOST"

also when i used ping using both url and ip i got the following response
"100 packet send 0 replied 100% packet loss"

Then i entered dns in /etc/resolv.conf and modified hosts.deny, hosts.allow

I triedagain but all in vain

One more thing the graph shown by kppp shows more packets out but very less in.

if u need any more info please mail me.

please help
thanx
manish

11 replies

by gazz

The only other thing you might want to check out is the default route. Are you getting a rout from the isp automatically?

by amagoon

type Route. You should see three routes. If there isn't one that says "Default" with Flags of "UG", you have no default route.

To set a default route, you must have first have an IP address of your default route. Then, run this command:

route add -net 0.0.0.0 gw insert-route-here dev insert-interfacename-here

For example, my default route is 10.1.10.1 on interface eth0, so I would type:

route add -net 0.0.0.0 gw 10.1.10.1 dev eth0

You may add this command to /etc/rc.d/rc.local

If you don't know your interface name, run the ifconfig command. Good luck.

by manish khanna

gateway is there and is set to my isp server add. when i used ifconfig i felt something was wrong as NOARP and MULTICAST were shown. even pinging my isp didnot help

by mtuppen

I would login as root, and start up linuxconf. Make sure your IP address, gateway, subnet mask are correct and your DNS server (if using one). You will also have to make sure you've specified your full hostname for the DNS to work properly (ie. hostname.localdomain - I had similar trouble once).
Check your eth0 settings with the ifconfig command. You should have your IP, broadcast and subnet mask specified.

Regards,
Mike.

by wls

You could have a driver problem, a routing problem, a DNS problem, etc. So you're going to have to solve a meta-problem before this of identifying which problem you have.

I'd start by making a manual entry in /etc/hosts and seeing if a ping, telnet, or web request works.

If that does, then move on to solving DNS by looking at /etc/resolv.conf and trying nslookup to see who's resolving DNS queries. If you're running your own DNS service, make sure named is up and that your /etc/named.conf is properly configured.

If the /etc/host trick doesn't work, then I'd be more inclined to check your networking options. See if you can ping 127.0.0.1; if yes, you at least have interfaces working. If not, you've got more serious problems and it's time to check the kernel.

Some systems have a netconfig command to configure everything for you. The commands you'll want to play with are ifconfig to see if your ethernet interface is up and properly configured, arp to see if it notes anyother local network traffic, and route to see where packets are going.

While this may not directly solve your primary problem, it ought to get you more useful datapoints about it.

This discussion is closed to new replies.