CentOS 5 Networking :: PING From 5.5 To Windows Hostname/NETBIOS Name?
Jan 28, 2011
Windows 7 machine (hostname/NETBIOS name: AwesomePC, LAN IP: 192.168.1.20)
No WINS server
From CentOS 5.5, have
# ping AwesomePC
resolve to a ping on 192.168.1.20
# ping AwesomePC
resolves to some random public IP that seems to be coming from my WAN DNS (openDNS) servers
Have edited /etc/nsswitch.conf, edited line: hosts: files wins dns Have edited /etc/resolv.conf, added line: search CAKE Have installed samba (# yum install samba) and run (# service smb start), with /etc/samba/smb.conf, workgroup = CAKE, name resolve order = wins host lmhosts bcast
Does # ping even care about samba? How can I get this to work?
I have a windows 7 desktop hardwired to my wireless router and a windows xp laptop connecting wirelessly on the same network. I am able to ping the windows 7 box by its ip address but unable to do so by its hostname. This is very inconvenient since I would like to set up a share by hostname (doesnt change) and not by ip (changes occasionally since its dhcp).
I have been beating my brains out the last few days trying to get my linux box to ping my Pc's via the netbios name. (ping pc_name) I have read post after post with no luck at all. What i do know is that my pc's can ping the linux box via netbios name with no problem. Samba works from the pc's but not the other way around. I have added wins to my host in the nsswitch.conf fileMy smb.conf file:Quote:
global] workgroup = OFFICE server string = Samba Server Version %v
I have a network of 2 WinXP machines and one linux box. I have fiddled around with the settings as you do when learning. The network is working. The network neighbourhood on the WinXP machines recognise the linux box and vice versa, (the linux Places|Network recognises the 2 WinXP). I can Ping the linux box using its hostname from a WinXp. But I cannot do the reverse. I get an 'unknown host' response. I can ping the linux to itself using its hostname.
I'm having an issue on two Fedora Core 13 machines where I can ping others by hostname, but the hostname resolution fails whenever I use ssh/scp/vnc/etc. I can still do these things by IP address, just not by hostname. RHEL5.3 machines on the same network with the same configuration do not seem to have this problem.
Here's the not-so-quick-and-dirty description of the situation:
I know that there is a virtual router at 192.168.31.1 and another at 192.168.30.1. I also know that there is another network (let's call it 126.96.36.199) and on that network lies a number of resources. By nature of this configuration, any machine on 188.8.131.52 can be accessed by any 192.168.x.x, but not the other way around. Beyond that is out of my hands and currently out of my scope of knowledge.
I have a dnsmasq server on 184.108.40.206 that operates as a secondary nameserver, another machine out of my sphere of influence is the primary nameserver (220.127.116.11).
The secondary nameserver on 18.104.22.168 holds the hostnames of our development machines. The problem is that in some cases, while I can ping by hostname all day long, services such as ssh, scp, vncviewer, etc all fail to resolve the hostname. In other cases I can do all of these things.
Every machine has an equivalent resolv.conf:
As an example, I will show the output of a handful of my development machines:
I also included columbia as a one-way test -- even though it cannot access 30.x or 31.x, they can access it:
columbia -- physical machine, Red Hat Enterprise 5.3, IP 192.168.100.200
Okay, so here are the various outputs. Remember, nibbler, discovery, and atlantis can ALL: - Ping by IP address - Ping by hostname - ssh, scp, vnc, etc by IP addess
Additionally, the SERVFAIL reply from 22.214.171.124 is expected since my dnsmasq server is on the secondary server.
Note that the only machine that can both ping and ssh/scp/etc by hostname is nibbler, which also happens to be the only one of the three running RHEL5.3 instead of FC13. Other virtual and physical machines running on the 192.168.31.0 and 192.168.30.0 networks (all running RHEL5.3) work just like nibbler does. So the problem seems to only affect machines running FC13.
Final note: selinux is disabled, iptables is disabled, ip6tables is disabled.
Other than that, discovery is a brand-spanking-new install straight off of the FC13 DVD. atlantis has been around longer, but its just a file server so I haven't done anything too crazy to it.
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 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.
Ping by hostname - there is a 5-6 second delay between each one of the responses:
Ping by IP - the responses come VERY quickly one after the other:
First off I should say that I am a total Linux and Networking Noob. I have used Windows all my life, but I am now trying to get into linux so I have set up an old PC with Fedora.
Currently I only have the Linux Box and a Windows 7 Box and they are both connected to my broadband router. I have set them up with static IP addresses in the router and they can both ping each other by IP address but not hostname. I would like to be able to use hostnames to access each box (e.g. for SSH access and File Sharing). My question is basically how can I do this, what are the options and which is recommended for a small home network?
So far I have been able to set up the linux box to be able to ping the Windows box by hostname by editing the hosts file. Is this the right thing to do? Should I just do this on the Windows box too?
I have 4 installations of Fedora 14 running on a Win 2008 R2 server in Hyper-V.
When I try to ping my desktop or the host server via the hostname from within any of the Fedora installations, the ping fails. I can ping by IP without issue. Also if I try to ping the VMs from my desktop it fails. I have an XP VM setup that I can ping without issue via hostname and IP.
All of the VMs can access the Internet without issue. I have disabled all firewalls on all systems with no luck. My desktop can ping the Hyper-V server without issue so it would appear that the problem lies with the Fedora installations.
Does anyone have anything I can try to get the name resolution working?
I have a Windows 7 machine that I have an installation of Ubuntu 10.10 via VMware and am having an issue with pinging by hostname thorugh the VM. From the Windows 7 machine I can ping by name without any issue but not with the VM. I have the VM as bridged so it is pulling all the network stuff via DHCP including the correct DNS servers. I can ping all the DNS servers and host without any issue. I have verified my /etc/resolv.conf entries are all correct.
If I run nslookup via the VM it says:
I have also verified that AVAHI is running to cache the DNS stuff and still no success.
At work, I recently installed FreeNAS 0.7.4919 on a computer and set it up to be a samba server. Using a Windows XP Pro SP3 computer on the same subnet as the FreeNAS server, I can ping the FreeNAS server's hostname and it works just fine. However, using an Ubuntu 10.04 computer on the same subnet as the FreeNAS server, I am unable to ping the FreeNAS server's hostname. When I try, it says "ping: unknown host [the FreeNAS server's hostname]". I can ping its IP address just fine, though. Why is it that Windows XP Pro can ping the FreeNAS server's hostname but Ubuntu 10.04 can't?Here's the output of the ifconfig command on the Ubuntu 10.04 computer:
Code: eth0 Link encap:Ethernet HWaddr 00:14:c2:cd:a6:39 inet addr:10.37.74.141 Bcast:10.37.75.255 Mask:255.255.252.0
I have a weird problem since yesterday that I can't solve. I can't ping / ssh my machine anymore using its hostname... says "unknown host", "network unreachable". I have no idea why - it used to work perfectly. I can still ping / ssh using the IP so it must be a problem of hostname not being resolved.
I have a dynamic IP (I'm at work...) but that doesn't seem to be the problem - network manager automatically adds a line in /etc/hosts with <mycurrentip> <hostname> (I checked, it's indeed the IP given by ifconfig and that I can use to ping/ssh).
2nd question: Another computer has a similar problem but slightly different: the hostname is resolved but points to a wrong IP (seen in ping or nslookup), different from what ifconfig returns. As a result, ping times out and ssh says "no route to host".
In my office i have a network of 172.16.31.0 and a squid proxy server running, all other systems have windows XP and one system has centos. On centos system i have three lan cards and i want to test some things on it. So i assigned another IP on it of range 192.168.7.0/24 and same range on another windows system. And all the systems connected through a same network switch.
Unable to ping between Centos and Windows system. If i ping from one centos to windows system with the series of 172.16.31.0 then it replies very well but same thing is not happening in other 192.168.7.0/24 IP series.
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?
I have a problem on my LAN, then: I have a laptop on which Windows Vista is installed, and every time I try to do ping to my server centos, my centos server does not respond to ping. The server is operating normally, because I found other PCs on my network that communicate normally with my centos server.
I can't ping by netbios name or fully qualified domain name, BUT nmblookup works just fine. I know it's a dns problem(s) I just don't know what or how to fix it. I'm very new to all of this(networking, domain administration, posting on forums etc) so I hope this is the right way to ask for help here. I've searched around the forums and the internet for a bit but I haven't found a solution to my problem yet.
here is some background on how the network is setup2 different domains sharing the same dhcp scope.
DC for DomainA is running windows 2003 std DC for DomainB is running windows 2008 sbs DC-A has ip of 192.168.1.249 DC-B has ip of 192.168.1.3 router is sonicwall (192.168.1.1) DC-A is hosting both DHCP and DNS
there are 25 computers in DomainB and 1 computer (not in domain) with ubuntu 10.04 and Free Open Ghost running on it (dhcp off) all 25 computers can ping the fog server by name (and eachother) all 25 computers pxeboot to fog just fine
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 mean I assigned the IP: 192.168.1.4 to Linux machine (Eth0). I did everything above and can't ping till now, when pinging from windows or Linux I get a message "destination host unreachable" restarted Linux many times but same result. NETWORK CABLE is working fine I tested it.
I have installed a ubuntu 9.10 server to use mostly as a fileserver. When I installed the server I set it up as DHCP and later on I have changed the /etc/network/interfaces file, the /etc/hosts file and the /etc/hostname file. I have the ip 192.168.1.100 set on the server and I can ping and SSH this address. But I can not ping my server by it's hostname enighet. I am setting up a NFS server and I would like to use my servers hostname when I do this. Why can I not ping my server by it's hostname? These are the 3 files I have changed...
Code: johan@enighet:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo
I configure a Linux Suse 10 box, added static IP, DNS (resolv), gateway (routes) but I am not able to ping other servers by name but nslookup works and the server can navigate on internet check below the problematic server is server-host20
Other server can ping that server by name just fine
All my network information by the way my server can ping DNS server by name just ok and as you see nslookup works.
So everything seams to be fine on my F10 boxes networking. I can ping computers on the network with both LAN IP addresses, and their hostnames. However, I can only access my F10 box with a LAN IP. In windows, I go to view workgroup computers... only the windows systems. If I go to the F10 system with samba via the IP address it works fine, just can't get to it with a hostname.
I'm wanting a static IP of 192.168.1.22. And on the windows workgroup "workgroup".
I'm new to doing things with linux that are remotely difficult... and well, this has proven to be. I can't work out if this is a SMB problem, general networking...
smb.conf (I've ommited the top info segment due to forum character limit, as well as the SELINUX notes)
Code: #======================= Global Settings ===================================== [global] # ----------------------- Netwrok Related Options ------------------------- #
I've completed the installation of a CentOS server.Running the setup utility as root, ive set up a static IP and installed apache. Now this works ok. I can type in the servers IP address from my browser/putty/winSCP and access the server within the intranet. The problem is that i would also like to access the server using its hostname, e.g. http://centos or whatever Currently i cannot do it. I've searched the forums, edited the /etc/sysconfig/network and /etc/hosts to no avail no matter what i do i cannot access it. i've disabled some services so im not sure if this is the fault.
I've had my FC11 x86_64 installation up and running for 6 months. Until a week ago, I was able to mount windows shares through Nautilis using their netbios names. About a week ago, this all broke with no tinkering on my part. Now, I can mount the shares using the IP address, but not using the netbios name.
When I make he attempt either from scratch or by using a previously working bookmark, I get "cannot display location "smb:\..." When I browse the network using Nautilis I can see the workgroup, but when I try to open it, I get "unable to mount location. Failed to retrieve share list from server." When I use nmblookup with the netbios name, the correct ip adress is returned.
The problem seemed to correspond to a software update that occurred on 2009-11-21 that included updates to selinux-policy and selinux-policy-targeted. SE Linux has the System Default Enforcing Mode set to disabled. The system default policy type is set to targeted with no other options available.nsswitch.conf file appears to have been changed on the same date, but reverting back to the backup version of the file failed to solve the problem. Samba is up and running. My linux shares are accessible from my windows boxes. The firewall is open to smb and smbclient.
I am currently facing one issue with my network. I have several computers and this is what happens, everything works fine when I use the ip address, but when it comes to hostname.
-Windows computers can't ping/see the computer 5 (while it is running linux), but they can see computer 3 while running ubuntu 8.10 and computer 2 while on Mac OS X.
-computers 2 and 3 can see/ping everybody while on Mac/Linux.
-computer 5 can ping everybody.
-computers 1, 2, 3 and 4 (on every OS) can see/ping computer 5 while on windows xp.
Basically, the problem is with computer 5, it can see, but it is not seen by other computers (just when running ubuntu lucid)Computer 5 is supposed to be a printer server, so it must be seen by the others regardless of OS.When I ping computers 5 the TTL is 64, when I ping other computers, TTL is 128. I don't think this means anything, but I am not sure.Initially I thought this was a printer issue, but then I realized is something related to network when I tried to use ping/explore the computer 5 by ip/hostname (it works by ip, but not by hostname).Computer 5 is sending the hostname to the router properly, it appears in the dhcp client list.