titan wrote:Actually, Windows and Linux handle DNS the same way. They both use a hosts file.
The first thought that came to me is that Windows doesn't access network shares the same way. Do you have Samba running on your server?
Lonewolf08 wrote:The only thing I can think of is that Linux handles its DNS client settings differently than Windows.
Lonewolf08 wrote:Lonewolf08 wrote:The only thing I can think of is that Linux handles its DNS client settings differently than Windows.
I should have posed this as a question, thanks all for clearing that up for me though.
JBI, concerning the router; I'm not quite sure it's a true DNS Server. I just know it's acting as my DHCP assigned DNS. I have Tomato's DNS caching setting turned on so it's caching DNS entries from my ISP's DNS. The clients are all set to use the router as their DNS source. My Ubuntu server shows up in the routers Device list along with it's leased IP address. I can successfully nslookup the server by name, I just can't ping it by name from Windows (but I CAN from Linux based systems).
Lonewolf08 wrote:No I do not have Samba installed, not yet anyway. I started with a default server with no extra packages to try to get the hand of the bash terminal and Linux in general.
If I install Samba and that resolves the problem, will that most likely prove is to be a NetBIOS issue? I just think it's strange that I can successfully resolve the server hostname but can't ping it. I'll try to flush the cache tonight and test again before I install Samba.
Also, if it matters, the Ubuntu server is running in VirtualBox, to rule out any shared network card oddities I did my ping testing from another system.
Thanks for the replies guys!
# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 220.127.116.11 rhino.acme.com # source server
# 18.104.22.168 x.acme.com # x client host
Lonewolf08 wrote:Thanks for the tip. I'll look into the IPv6 theory. What really doesn't make sense to me though is that I can successfully nslookup from the Windows client, but not ping. Doesn't that mean that the ping command should be able to resolve the hostname, or am I misunderstanding how things work?
C:\> nslookup linux-server
Address: 192.168.1.1 (This is my Router)
Address: 192.168.1.44 (This is the correct address of the Linux-Server)
Ping request could not find host linux-server. Please check the name and try again.
Lonewolf08 wrote:I installed Samba to test the theory about NetBIOS and that solved it. I can now ping by hostname successfully. Thanks for the help guys. About the original question though, is there something to networking I'm missing here? If a client can resolve the hostname to an ip address, shouldn't it be able to ping it?
notfred wrote:Yes, but what DNS domain (NOT Windows networking domain) is it in and what DNS domains does it search with a non-FQDN? There's a lot more to DNS than just "who is my DNS server" and that's what I am suspecting here.
just brew it! wrote:Lonewolf08 wrote:I installed Samba to test the theory about NetBIOS and that solved it. I can now ping by hostname successfully. Thanks for the help guys. About the original question though, is there something to networking I'm missing here? If a client can resolve the hostname to an ip address, shouldn't it be able to ping it?
Yes, it should. This part has me a bit puzzled as well. Either the host name is resolvable, or it isn't.
Users browsing this forum: No registered users and 3 guests