two computers connected directly to each other.HOST A: 192.168.1.1/24HOST B: 92.168.1.2/24Host A can ping and receive answer from host B.BUT, when host B tries to ping host A, host A does not send an answer to host B.tcpdump from host A:
Code:
13:44:57.788200 arp who-has 192.168.1.187 tell 192.168.1.1
13:44:57.968215 arp who-has 192.168.1.101 tell 192.168.1.1
[code]...
Ive got a problem on my server ....installed Debian 5 , Webmin and than syscp settung up syscp ready ....
I try to ping "localhost" ansver ping: unknown host
I try to ping "localhost." there is a host with IP 127.0.0.1
I need it to change it in "localhost"
Is that the bind9 maybe?
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
eg:
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 just connected an old Microsoft Wireless Desktop Elite Keyboard (keyboard + mouse set) to my Ubuntu and I was wondering if it is possible to configure all the additional keys and in particular the wheel on the keyboard.I found that keytouch was the software to do this, but on Ubuntu 10.04 seems to have some troubles: even after the configuration, all the additional keys are just... dead. The events connected with any of the keys never start.Does someone know how to configure this software?
View 1 Replies View RelatedI need to check the output of a name resolution, but I configured the firewall of the destination to avoid answering to pings.
Is there any other way to get a name's IP without using ping? (I mean something like $resolv name.com)
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).
View 3 Replies View RelatedI have a BIND server that I'm setting up with different views. There is another server out on the public Internet that currently handles all inquiries for this domain. I had installed the Yum packages, chroot, etc. and edited the config files by hand. When that didn't work, I erased the server and started over using Webmin to build everything for me. Same result. I want to setup and verify everything is working on this new server before I take it into production.This is in /var/log/messagesQuote:
Jun 13 21:33:20 dns1 named[13838]: starting BIND 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 -u named
Jun 13 21:33:20 dns1 named[13838]: adjusted limit on open files from 1024 to 1048576
[code]...
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.
View 3 Replies View RelatedEven ping google's ip address doesn't work. unknown host error using backtrack4 able to browse net with these settings.
My network settings:
What's the problem with these settings...
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.
When i ping www.google.es, i get something like:Quote:
ping www.google.es
(wait 20 seconds)
64 bytes from 66.249.92.104: icmp_seq=2 ttl:53 time=80 ms
[code].....
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:
Code:
/etc/resolv.conf:
Code:
Code:
rev.0.168.192.in-addr.arpa:
Code:
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.
View 11 Replies View RelatedI 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.
able to ping the debian servers? I haven't been able to for aver 24 hours.
View 6 Replies View RelatedStrange things are happening today to my pc with debian squeeze 2.6.32-3-amd64 kernel.
It can connect to internet via my wirelss rt2870 driver (Ralink, Belkin usb wireless). But I cannot ping any of my other computers in the home network (served by a Belkin N+ wireless router). Other computers can ping it.
I am also connected via ethernet directly to another desktop. Last night I can access the shared file (samba windows share) in this other computer, using ethernet (disabling wireless). Today I cannot. I cannot even ping it or any computer, or itself.
I am using network manager with this interface:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
I have a NAS which I've re-installed with DEBAIN. Mostly its all working great but when I tell it to ping a NetBIOS name it takes 10 seconds per attempt rather than 1. Despite this it actually resolves the NetBIOS names very quickly (the first line from the ping including the IP address appears almost instantly) it just sits there for 10 secs every ping.
# ping -c3 qnap
PING qnap (192.168.1.100) 56(84) bytes of data.
64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=0.175 ms
64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=0.167 ms
64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=0.158 ms
--- qnap ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 20036ms
rtt min/avg/max/mdev = 0.158/0.166/0.175/0.016 ms
#
# ping -c 3 [URL]
PING www.l.google.com (173.194.36.104) 56(84) bytes of data.
64 bytes from lhr14s01-in-f104.1e100.net (173.194.36.104): icmp_seq=1 ttl=49 time=40.3 ms
64 bytes from lhr14s01-in-f104.1e100.net (173.194.36.104): icmp_seq=2 ttl=49 time=25.4 ms
64 bytes from lhr14s01-in-f104.1e100.net (173.194.36.104): icmp_seq=3 ttl=49 time=25.7 ms
--- www.l.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2022ms
rtt min/avg/max/mdev = 25.491/30.518/40.313/6.926 ms
I'm really struggling to track down what may be causing this as it is strictly when resolving NetBIOS names yet it finds the IP immediately.
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
[Code].....
I have my router (192.168.1.1) connected to the internet. I have installed Debian on a server with Bind9 (192.168.1.254). The configurations files are:
Code: $ cat /etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1 Code: $ cat /etc/bind/named.conf
include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones"; .....
How I can ping my debian computers on their hostname?
I have installed both samba and winbind and I have also changed the line in /etc/nsswitch.conf to:
Hosts: files wins dns
I have done the same thing on another linux box (ubuntu) just to see if that worked and it did - I could ping it on the hostname.
Also, I have trid to add the ip/hostname in /etc/hosts and even that didn't work.
The /etc/resolv.conf seems to be as it should.
In the /etc/hostname the hostname is updated.
I have tried to restart the samba service and the networking service and even the entire computer but none of it worked.
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 have set up a MythBox on Debian Lenny. I have a wireless connection using a Belkin USB WiFi Device. I am using ndiswrapper, wpa_supplicant, etc. I am using a static ip address. I have internet access without problems. However, if I try to ssh in or even ping my mythbox inside my network there is no connection. I have never had to do anything special to ssh into debian in my network before. I am confused that I have an internet connection but can't get a ping reply.
View 1 Replies View RelatedI'm trying to run Debian server in our network. We have SSG5 Juniper Firewall set up to route traffic from our trusted network 192.168.50.0/24 to our DMZ 93.153.125.224/28I can connect / ping all Windows servers which are in DMZ. When I try to connect my Debian server instead of one of the server's static IP I'm unable to connect or ping to it. The server itself is able to connect to internet resolve DNS if I allow connection to our trusted network I'm able to ping or connect to any computer in trusted network but still unable to ping from trusted to DMZ. The SSG5 policy is set up to allow any connection from trust to DMZ and interface is set up to route all traffic.I have tried to trace the ping It'll go through firewall right to the interface needed but then it'll time out as like the server is not connected at all.
View 1 Replies View RelatedI couldn't install everything during setup of my debian server, so I installed post setup through the Add/Remove Programs. My guess is there is so much installed that either DHCP is not setup properly or there is a firewall installed. My computer found an IP address from my router but cannot connect to the DNS service or ping my router. I type: ping 192.168.1.1 computer resp: "ping: sendmsg: Operation not permitted"
View 4 Replies View RelatedI'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
[Code] ....
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 have installed linux debian in my computer but i have aproblem , i have a ping only on my computer itself , not to gateway or other computers on my network .
Ip : 10.0.88.9
Gateway : 10.0.88.1
dns :10.0.88.7
note:when i have installed system i have no internet connection so it is not installed updates
I'm using debian lenny.When I boot with kernel 2.6.36, ping always respond with Network is Unreachable. But when I boot with kernel 2.6.26 it works. I can't even ping the dafault router of 2.6.26 kernel when I am at 2.6.36. Also, system/administration/network does not show any connections while it shows something at the other kernel.
View 1 Replies View RelatedI 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
[code]...