I can't seem to get ping to work on my home computer. I actually have two separate installations of Ubuntu 9.10. One is at home, sharing space with Windows Vista (dual-boot) on a Dell Inspiron 1525. The other is at workusing Sun VirtualBox on a Windows XP host. ping works quite well at work, through VirtualBox. For example, Code:ping linuxcommand.org always gets 0% packet loss. However, when I do the same thing at home, I always get 100% packet loss.
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 have this annoying problem since day one.I am testing out Red Hat RHEL5, everything is fine except DNS look up.If I ping www.google.com, it doesn't work, ping ip address it all works;if I bring up browser, put www.google.com it doesn't work, can't find the name, however, simply put ip address there it works.My DNS seeting seems ok, and the DNS works from Windows box.
how to go about getting Ubuntu to receive an ad-hoc wireless ICS enabled connection. The internet connection is shared through a virtual machine running XP (with the USB wireless dongle under XP's control), on my desktop PC, in order to escape my ISP's no NAT policy. Ubuntu is on both the desktop PC (the sender), and the laptop (the receiver). The desktop and laptop also run windows 7. I managed to get my laptop Ubuntu to connect to my virtual machine XP, by setting the IP, subnet and gateway of all wireless devices, as was suggested in [URL] - I did use the Network Manager GUI, but pinging the desktop doesn't work.
Even with the IP configuration, Windows 7 on the laptop receives the internet fine. The next step is getting Ubuntu to receive. I can do any kind of configuration in a virtual machine, such as install Ubuntu. In virtual machine XP I used 192.168.0.1 with subnet 255.255.255.0 and gateway 1.1.1.1. On the laptop Ubuntu 192.168.0.2 same everything else. I understand nothing about networks. I know there is stuff I can do in the console, but how will Network Manager cope with me doing that?
I use my computer as a gateway to the internet for the rest of the house which is split into two LANs. I also have VPN's linking the office side of the LAN to a remote site. All of the PC's other than mine that should have access to the VPN works, but my PC doesnt and I firmly believe this is because I need to add a static route. ping 192.168.10.1 doesnt work but ping -I eth2 192.168.10.1 does. 192.168.10.1 is the remote router on the other side of the VPN. I've tried this route:
Code: route add -net 192.168.10.0 netmask 255.255.255.0 gw 192.168.1.1 dev eth2 192.168.1.1 is my computer... the gateway for the rest of the house/office. My computer has a quad NIC, only 3 ports are used. WAN, LAN1 and LAN2. Aside from this routing issue, I have everything working perfectly.
I run an centos server. From the console I can ping google.com and get a reply. But when I ping another address say xyz.com, the IP address is resolved (11.22.33.44) but there is no reply. In the same network in our office from my desktop I ping [URL] and there is a reply.I turned of the firewall but still the same problem.
I set up a virtual bridge for a virtual machine (qemu-kvm) using a qemutap interface:
Code: # brctl show bridge2 8000.0022648a3dcc no eth5 qemutap2 I can ping and ssh to the server ... Then I try to copy (scp) a file (2.8 M) to the server and, near the end, the copy stops and the server stops responding to ping and is not able to ping nothing except itself.
"ifconfig down ; ifconfig up" and the server is on line again.
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 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 ?
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?
I can connect to the internet and browse. I'm wired and using DHCP on a Windows network. Updating Ubuntu or downloading programs takes hours for 52MB of updates. Why? I read some articles that mention Network Manager needs to be enabled at the .conf file. Can I edit this using GUI or command line only?
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 am trying to get a Linux (Slackware 13.37) working in a Windows networking environment. The IT support for this organisation does not extend to Linux support, so I'm limited in what help I can get for this.
I'm trying to get to the point where I can get to the internet to download what I need on this Linux machine.
The situation is this (*fictitious addresses used) -My Linux machine uses a fixed IP address (10.100.150.21) My Windows machine uses a DHCP assigned IP address (10.100.150.213)Both Linux and Windows machine are configured to access the gateway server (10.100.150.1)So, I can ping the Linux machine from the Windows machine and vice-versa.I can ping the gateway machine from the Windows machine.I can browse Windows Shares on the network via SMB from the Linux machine.I CANNOT ping the gateway machine from the Linux machine with the Destination Host Unreachable message being the error message.
For actual internet access I need to access a proxy server but since the Linux machine can't even ping the gateway server, it fails to ping the proxy.Now, I have been told the gateway is a HW based router and for Windows machine they use some software for authentication to connect to the network. This software isn't available for Linux, so that's why I've been told to use a fixed IP address.My experience of networking is pretty basic and most of the Linux setup is done via running Slackware's setup program.
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 installed nss-mdns in Fedora Core 10 and can see all the Bonjour published hosts on the lan. However, I am always forced to append the .local domain when referring to a host:
I have Huawei B970b (see specs). It a router with wireless and GSM capability. It works ok in XP. I can connect and ping its IP 192.168.1.1. In Ubuntu I can see the wireless SSID and could connect to the router but I can not surf the net nor I can ping 192.168.1.1.
recently I got new wireless card, att usb Quicksilver(based/produce by Option?), for att.Regular gnome network manager freezes the computer when I am plugging it it therefore I installed the one from wicd.net.Also, I am using HSOConnect (to connect by to G3 network), and sometimes I connect to regular wireless g connection through router.
Under both cases I can ping the website by IP and can access the website by ip (ex. google) but can not ping or browse by name.As a side note... I can use and access Skype fine under g3 network and normal wireless.I tried browsing and finding other solutions in past few days but ended up breaking everything and reinstalling to get back to the point I am at now.I am working on the road, so not being to broswse is rather crippling to me.... also I can access internet normally only from home from different computer now.
I cannot ping any hostnames on our LAN /etc/resolv.conf has both name servers configured correctly. I can ping the IP, but can't ping the hostname. I know it's something really simple, just can't put my finger on it.
I can ping my IP, and other PC in the same LAN, but I CANNOT ping the gateway on my 10.04LTS ubuntu. Other PC in the same LAN(Ubuntu 10.04LTS) could ping the gateway and my IP. I thought that (1)network cable is OK because I could ping the other PC in the same LAN.(2)Gateway is OK because other PC could ping it. (3)setting of operating system might be somehow wrong.
I have tried to restart the network several times and still not works. I followed the HOW-To debug tips and following is the results. Any suggestions?
I'm having a problem with my computer connecting to a speficic wifi. The problem seems to be between my computer and this wifi, because I can connect to other networks and other computers can connect to this wifi. I do manage to get a connection, but I can't ping any website, I always get an unknown host error.I have managed to connect to this network only once: it wasn't pinging and then it eventually started working, but I don't recall doing anything that made it work.
