Yeah. some of you might remember I had problems with this before. It still isn't working. I've tried a lot of things. Ping and traceroute don't work. I have internet access on Redhat. I've checked my firewall settings and even turned them off for a minute and tried. Nothing seems to be working. I've heard some stuff about iptables and the such, and I don't know what to do. all help is great guys.
"When I die I want to pass peacefully in my sleep like my grandfather did, not screaming and yelling like the passengers in his car."
I recently had a problem on one of my machines whereby ping would give me an error, (10050). I fiddled around with my router/firewall for ages but couldn't find it.
I knew it couldn't be ZoneAlarm because I'd turned that off in the startup folder. However, after a week of mucking about, I ran the de-install on ZoneAlarm and presto - it all started working.
I can only assume the driver that ZoneAlarm installs was getting installed anyway and had somehow interferred with my network.
Ping was not the only thing that had stopped working Seti@Home could not get new workunits, AV auto update stopped working etc.
Wave upon wave of demented avengers march cheerfully out of obscurity unto the dream.
I do not have any firewalls running and I uninstalled the stadard firewall that came with it. I don't understand why I can have internet access and all, but my computer wont let me ping outside the "network" which is my ethernet cable connection. I'm lost.
"When I die I want to pass peacefully in my sleep like my grandfather did, not screaming and yelling like the passengers in his car."
you have access to the internet and can do everything else that you need to do on the net? (sorry if I'm not getting everything here, I don't know the previous history of your problem).
Might I ask why it is so important to run ping and traceroute? I mean, other than checking to see if a certain server is up or whatever, why do you need to do this?
And if I understand your post correctly, you can ping to any device on your intranet?? If that's the case, then you have a problem at the point where your connection comes in, it's not a problem with your computer's setup.
>>> I do not have any firewalls running
Nor did I... or so I thought.
If you can ping your local host 127.0.0.1, then your ping program is working. If you can ping other IP's on your lan, then your hub/switch is working. So your router or beyond must be filtering your enquiries.
Wave upon wave of demented avengers march cheerfully out of obscurity unto the dream.
Well traceroute is supposed to be good if you cant get into a site, and I hear ping is supposed to be helpful with advanced tasks you can do. I want to have a broad knowledge of how to work a linux machine and thats just something in my way that I want to figure out.
"When I die I want to pass peacefully in my sleep like my grandfather did, not screaming and yelling like the passengers in his car."
ping and tracert have a few very limited uses, probably the quickest way to get a dns translation. Many servers/routers/gateways now offer the ability to switch off replying to pings etc., thus a failing ping to a site actually means a lot less then it used to.
Wave upon wave of demented avengers march cheerfully out of obscurity unto the dream.
