Debian Configuration :: Can Ping Public Ip But Cannot Ping Domain Name
Apr 6, 2011
I have a debian server installed with a static ip. Now i am able to ping my ip, but when i try to configure a domain name with the nameserver as my ip, i am not able to ping the domain name
I am using an virtual machine. where I need to ping from one machine to another. earlier I was able to ping. But after going to google.com once, I cannot ping back to this machine.
But if I gave ping -I eth1 <IP> then I can ping.
I cannot install any package, so tell me solution which includes not installing any package.
i am running debian testing and the last few days i was trying to ssh to another pc on my network and i was getting an error like there was no machine with that ip! then i tried pinging to it with no luck! ARP was the only tool that returned the MAC address of the machine and that is strange i think. i realised then that i could only ping the gateway and localhost (127.0.0.1 not my ip). after editing my /etc/hosts, i could ping my ip as well. what is so wrong? here are some useful things:
my new /etc/hosts: jack@debian:~$ cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 debian.local debian
I recently did a clean install of Debian 5, and a backup program called BackupPC. Both machines are on a small local network served by a router. Both machines have statically mapped IP addresses, done by the router via matching MAC addresses in a table of corresponding IP addresses (192.168.0.2 (HP-PC-XP), 192.168.0.3 (Debian). I configured Backup PC correctly (I think)...Upon running Backuppc, the first thing it tries to do when its time to run a backup is to ping the machine to be backed up. The name of the PC is stored in a backup pc config file. (I believe BackupPC does a DHCP request with the machine name to get the ip address, but not sure). Running the backup results in BackupPC tells me that it can't ping my xp machine. If I open up a terminal window in debian, i can successfully ping my xp machine when i use the ip address. 92.160.0.2 If I ping using the host name of the xp machine (e.g. HP-PC_XP), the ping command displays some ip address i've never seen...something like 63.123.155.104....how is it getting that and how can it be corrected?
I recall that nslookup looks at the local hosts file first to resolve the name....i look in my hosts file and found no such address (only contained localhost)....now what?
I've been using Debian for about 6-7 months now. I've had a bit of a major networking problem for the past 4 months or so that I've been trying to fix - specifically, it started when I upgraded to Jessie. I can connect to wifi just fine, and sometimes I can even use the internet for brief periods of time (exceedingly rarely). Then... nothing. No network access, period. I can't ping any outside servers, I can't ping other computers on my network, and I can't even ping my router. Pages I try to load just stay "connecting" for all eternity, network printing fails, and so on.
So after four months of searching online (I've read through way more wireless documentation than I care to say), I finally gave up and admitted that maybe I screwed something up during upgrade to Jessie (as a matter of fact, I did, I had to do the upgrade in two increments [somehow] because my root partition was too tiny by mistake) and I did a clean install. Since I had /home on a separate partition, I was able to keep all my user files, but all settings regarding networking were wiped. So after installing firmware-iwlwifi so I can use my wireless card, I tried connecting to wireless! Success! Then I tried connecting to the internet... success! Briefly. The next morning I tried using the internet again, and it failed in exactly the same pattern as before.
I don't know much about what's going on here, but here's what I do have available:
I do have to use firmware-iwlwifi, which I installed by doing apt-get install firmware-iwlwifi. I don't think it's an issue with the wireless card itself (hardware-wise), the laptop dual-boots Windows 7 (that I never use anymore), and Windows 7 is able to connect to the internet just fine. Connecting directly to my router by ethernet cable works fine, I have perfect internet/network access then.
I can confirm that my laptop is receiving an IP address and that it is using ARP correctly to get the MAC address of my router (I confirmed this by doing the arp command, it has the MAC address correct, I checked from another computer with my router's config page) All other computers on my network work perfectly with my router. To confirm the router/its configuration isn't at fault, I did a full factory reset of the router, but to no avail.
Out of curiosity I tried installing Wireshark (using an ethernet cable to download it) to monitor what happens when I try to access a webpage. I'm no expert on networking, but I noticed something out place when I compare a capture from the affected computer to a capture from one operating normally - there are a lot of STP packets showing up. I did some checking around, it looks like STP is involved in bridging and more complex networking setups (involving switches, for example)... but it shouldn't be found on a home network, especially where there's no bridging whatsoever. These STP packets don't show up on packet captures done from any other computer. I've attached a packet capture from the affected computer here, since the forums won't let me attach a .pcapng file.
Here's the output from a few commands I ran during past troubleshooting sessions:
Code: Select allsudo ifconfig eth0   Link encap:Ethernet HWaddr e0:db:55:b5:fe:06      UP BROADCAST MULTICAST MTU:1500 Metric:1      RX packets:12455 errors:0 dropped:0 overruns:0 frame:0      TX packets:7781 errors:0 dropped:0 overruns:0 carrier:0      collisions:0 txqueuelen:1000
I would like to ask something. Today my network Internet access suddenly slowed down, after inspecting the problem the hard way we disconnected one of our servers(ip=190, debian squeeze) from network and the network was alright again. When we plugged it back in, following symptoms were observed: computer 190 pinged gateway app. each 6th time. gateway(debian lenny) pinged computer 190 app each 6th time whole network Internet access was slowed down, local network functioned just fine
While pinging themselves, i ran iptraf on icmp packets on gateway and I saw what i thought was ping attack, lots of echo request coming from external address to computer 190. Blocking that address in iptables didn't help but restarting the gateway did, network Internet conenction is at full speed and gateway and computer 190 ping just fine.
My question is, what steps should I undertake in similar case (it's second time in 2 months) - to debug similar problems. Is it even possible for ping DOS to this kind of damage?
I try to use the "ping -a" command for getting an audible ping. But there is just silence The command "beep" works fine, so everything should be ok with the speaker (in the konsole).
I have a very strange problem.ometimes, yes sometimes not all the time, I get a Destination Host Unreachable when I ping a computer on my network. If I switch to root using su I can ping that same computer. Here is a screen shot:
joseph@laptop:~$ ping 192.168.1.14 PING 192.168.1.14 (192.168.1.14) 56(84) bytes of data. From 192.168.1.9 icmp_seq=2 Destination Host Unreachable
Just installed squeeze and noticing slow responses to ping. Ping with -n is fine, and as expected. Ping without -n is very slow to appear on the screen.
ben@WOPR:~$ ping google.com PING google.com (74.125.230.114) 56(84) bytes of data. 64 bytes from 74.125.230.114: icmp_req=1 ttl=54 time=26.2 ms 64 bytes from 74.125.230.114: icmp_req=2 ttl=54 time=25.9 ms 64 bytes from 74.125.230.114: icmp_req=3 ttl=54 time=29.3 ms 64 bytes from 74.125.230.114: icmp_req=4 ttl=54 time=25.5 ms ^C64 bytes from 74.125.230.114: icmp_req=5 ttl=54 time=25.8 ms
--- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 20199ms rtt min/avg/max/mdev = 25.514/26.569/29.308/1.399 ms ben@WOPR:~$ ping -n google.com PING google.com (74.125.230.115) 56(84) bytes of data. 64 bytes from 74.125.230.115: icmp_req=1 ttl=54 time=25.6 ms 64 bytes from 74.125.230.115: icmp_req=2 ttl=54 time=26.0 ms 64 bytes from 74.125.230.115: icmp_req=3 ttl=54 time=26.8 ms 64 bytes from 74.125.230.115: icmp_req=4 ttl=53 time=21.5 ms ^C --- google.com ping statistics --- 5 packets transmitted, 4 received, 20% packet loss, time 4006ms rtt min/avg/max/mdev = 21.540/25.042/26.859/2.064 ms
I've tried disabling ip6, disabling avahi and adding options single-request to my /etc/resolv.conf - problem remains. If it helps when installing Squeeze was prompted to install firmware-realtek, which I didn't have. So downloaded onto usb from another machine installed once setup was complete.
This applies to my 2 opensuse PC's, my Windows PC is fine.I can ping a hostname, say "PC1" but I can not ping PC1.domain.local (even the host PC can not ping it's own FQDN). When I ping just the hostname the ping stats even list the FQDN.Onto the next issue, since all my PC's, have the domain prefix domain.local, my Synology can not. I can ping it's IP and that is it. I can resolve it's name with nmblookup just fine tho and that is what is killing me. How is this not resolving.Even weirder, I can browse to "Synology" in Network Servers under places on the slab.
I have two machines on this network, one running Ubuntu and the other running Fedora.
When I'm using the Wireless network on the Ubuntu machine, I cannot ping the Fedora machine. Everything else works. I can browse the net fine.
If I switch over to the Wired Network then I can ping the other machine.
I don't understand why ping doesn't work only over the Wireless. I can ping the router so I'm guessing it's getting blocked by the router but I didn't block ICMP traffic.
I tried asking on IRC and they ran out of ideas too to find out where the problem is.
I just installed my first EVER bind DNS server. I am running bind9 on Ubuntu 10.04. Everything seems to be working great except one thing: If I ping a host that I have set up in bind by its HOSTNAME the pings take 5-6 seconds to reply/print to the screen between each echo response. If I ping by the host's IP address, they echo back very quickly.
I have read that IPv6 can cause this, but I have disabled it in /etc/sysctl.conf and the problem still exists.
I know everyone says this can't be a DNS issue, but this never was an issue with dnsmasq (which i was using prior), and it doesn't make sense that the ping are ONLY slow when pinging by hostname and not IP.
Configs below:
Ping by hostname - there is a 5-6 second delay between each one of the responses:
Code:
Ping by IP - the responses come VERY quickly one after the other:
So, I have an Virtual Machine running CentOS 5.4. It sits behind a hardware firewall which also does NAT'ing. I've set up plenty of these, so I know for sure the firewall and NAT rules are set up correctly. From the host, I can ping anything in my subnet and the gateway. But I can't ping anything else beyond the gateway. I can perform DNS queries and when I try to ping, it finds the appropriate IP address.But from the outside, I can ping the PUBLIC address (It's a 1 public to 1 private address NAT, not 1 public to multiple private). I've tried it with IPTABLES on and off, with no change.
I have Mandriva One 2009.0 (192.168.1.100) on one box and Mandriva Free 2010.0 (192.168.1.118) on the other. I can ping router (192.168.1.1) from both of these boxes but I can't ping one box to the other and the other way around. What's going on?.
Do I have to change some settings in router?. Or is it firewall issue on those two machines?. Both of these boxes are connected by cable. Symbol of the router: TL-WR340G.
I was using my ISP's DNS server. When I would ping something that doesn't exist, e.g. blahtest.com, it would reply anyway. When I tried to go to the site in a browser, it was some page like "I hope we can help you find what you're looking for". I thought that was ridiculous, so I changed to OpenDNS's DNS server.
ever since upgrading from karmic to lucid, i cannot ping fqdn hosts in .local tlds. nslookup & dig work, but most other utilities fail (ping, traceroute, etc...). i know .local is an invalid tld, but apple seems to have made it a defacto standard on private networks, so i'd imagine somebody else has seen this issue before... is there a simple fix that doesn't require managing hosts file entries on a bunch of systems?
Since two days i m not able to browse websites using the domain names but able to ping/browse using IP addressed. I have done the following:
1. Using wireless i m able to get IP address of DNS (8.8.8., Gateway, localhost & router ip address 2. Disabled wireless and connected ETH0 but still the same problem 3. not able to edit resolv.conf
sudo gedit resolv.conf ** (gedit:4179): WARNING **: Hit unhandled case 0 (Error opening file: Input/output error) in parse_error.
For clairification, I can ping. I have tried several IP addresses and 100% success rate. When I noticed the problem I was trying to run sudo apt-get update && apt-get upgrade After some time I noticed these error messages to start with
[Code]
I tried to ping the adddress security.ubuntu.com from my Windows machine to verify that I could connect and was surprised when I could. I then pinged the address 91.189.92.167 which is what my windows machine resolved the name as and it went though.
My thoughts on this are that when my Ubuntu Router came up, for some reason it did not incorporate the ISP's DHCP servers into the ip address it obtained. Sadly I know to view ALL IP infomation in windows via ipconfig /all command but I do not know what this is in the *nix world. need commands that I can use to check and troubleshoot this apparently DHCP issue so I Can start to update my server and expand on its services?
I have been logging into a server remotely and trying to set up a mailing list on it. The server is the newest version of ubuntu server: uname -a: Linux Themis 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:48:10 UTC 2009 i686 GNU/Linux.I noticed I could not download packages with apt-get or ping domain names, and I can't even ping 127.0.0.1.And do you think there is something wrong with the network card?
As the title suggest, I have downlaoded the latest copy of Ubuntu Server from the ubuntu website.Everything installed fine. DHCP configured ok as far as I can tell. I can ping other machines on my network (which are running Windows) and they can ping the Ubuntu machine and conenct to Apache which is running on it.If I try to ping google.com or any other domain, it gives the correct IP address but gives no response to any pings, dont telnet on port 80 (or any toher potr for that matter) on any machine on the internet. I checked the settings using ifconfig to see what DHCP had assigned, and they matched the windows machines configuration (other than the IP address obvisouly). I tried assigning a static IP, even reserving a particular IP for my NIC.
Whatever I do, i cant connect to any machine outside the network via IP or domain.I have searched everywhere and tried everything i can find on the net but still to no avail.The Windows machines are part of a domain called alcom-uk.local and run off of a Windows Small Business 2003 Server. Not sure if i need to manually setup Ubuntu to connect using a domain or anything.
I have connected xp and fedora through crossover cable . xp has ip address 192.168.0.1/24 (manually assigned) fedora has 192.168.0.2/24 with default route equal to 192.168.0.1
I can ping fedora from xp computer but i can't able to ping xp from fedora computer.
I have manully edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file with correct subnet mask and ip address because when i tried to give ip address manully in network manager the subnetmask is replaced with gateway address don't know why.
Now i want to share internet through crossover cable . xp is connected to internet through wireless usb adapeter.
I try to ping with php : exec("ping -n 1 $ip",$output[],$retval); it works fine in window. but in linux i got this error : ping: icmp open socket: Operation not permitted are there any ways to solve this ?
On the ROUTER I have set the ip_forward=1 and eth0.proxy_arp=1 and eth1.proxy_arp=1 then I run the following command : route add -net 192.168.2.0/24 gw 192.168.2.1 dev eth0 route add -net 192.168.4.0/24 gw 192.168.4.1 dev eth1
On PC1 I executed the following : route add -net 192.168.4.0/24 gw 192.168.2.1 dev eth0 and for PC2 I run the following route add -net 192.168.2.0/24 gw 192.168.4.1 dev eth0
After doing those things, I can't ping between PC1 and PC2... but both can ping the router...
I have a desktop computer (Ubuntu) connected to one of the LAN ports of the Cradlepoint MBR1000 router via an Ethernet cable. I also have a Verizon mobile broadband USB modem (USB760) plugged into the USB port of the Cradlepoint router.I also have a laptop (Ubuntu) with a wireless wi-fi adapter (802.11g). The laptop also has an Ethernet card but I'm not using it. The desktop computer does not have a wi-fi adapter, only the laptop does.
With the above setup, I have Internet access to both the desktop computer as well as the laptop computer, which I am well pleased with.Is there a way I can have file sharing between the desktop and the laptop, or at least ping between them, the way I have it set up? I can't use the ad-hoc method because for that to work each computer needs a wi-fi adapter. The router is using DHCP but can also be configured manually.
How can I forward all traffic from a public IP to another public IP. Let's say I have a first debian box named box1 with eth0 = 1.1.1.1 and eth0:1 = 1.1.1.2 and I want to forward all traffic from 1.1.1.2 to "box2" located somewhere else over the internet and having for eth0 2.2.2.2 Both 1.1.1.0/24 and 3.3.3.0/24 are public IP ranges.