dnsmasq trouble

Heloo guys...

Could you help me please?

I'm running a linux box with DNSMASQ (let's call it SERVER1 on
192.168.13.1)
inside there's /etc/hosts with :
linux1 192.168.13.5
linux2 192.168.13.6
winxp 192.168.13.10

the /etc/resolv.conf
nameserver 194.xx.xx.xx (direct internet)


Everything is ok, all the machine in LAN have gateaway and DNS set on
SERVER1, but...

linux boxes "ping" perfectly everything (lan+wan)

WinXP can access to internet but cannot ping linux1 and linux 2 ?????
why ?

By the way on WinXP, if I try C:\>nslookup linux1 (for example)
everything is ok, I get :
Server : SERVER1
Address: 192.168.13.1

Name : linux1
Address: 192.168.13.5


What's the problem win XP ??


than for your help

> WinXP can access to internet but cannot ping linux1 and linux 2 ?????
> why ?
>
> By the way on WinXP, if I try C:\>nslookup linux1 (for example)
> everything is ok, I get :
> Server : SERVER1
> Address: 192.168.13.1
>
> Name : linux1
> Address: 192.168.13.5
>
> What's the problem win XP ??

Well you don't have a DNS problem, since WinXP resolves linux1 to its
correct address.

You may have a firewall problem. Are your linux boxes configured to
drop echo requests from WinXP? Is your WinXP box firewalled to drop
echo replies from the LAN?

You may have a routing problem, in which case WinXP knows linux1's
address but doesn't know how to find it. What does 'route PRINT' show
on WinXP?

--
To reply by email, replace "deadspam.com" by "alumni.utexas.net"

Thanx for your answer...

Well, in fact any Windows on the LAN cannot ping !?

The iptables on SERVER1 is down.

All the route are the same for each boxes
All Unix are ok (I have also a Solaris 10 x86 which "works"/ping perfectly)


I don't understand at all

damn...


"Andrew Schulman" <(E-Mail Removed)> wrote in message
news:175w09gx3p6sc$.(E-Mail Removed).. .
>
> > WinXP can access to internet but cannot ping linux1 and linux 2 ?????
> > why ?
> >
> > By the way on WinXP, if I try C:\>nslookup linux1 (for example)
> > everything is ok, I get :
> > Server : SERVER1
> > Address: 192.168.13.1
> >
> > Name : linux1
> > Address: 192.168.13.5
> >
> > What's the problem win XP ??
>
> Well you don't have a DNS problem, since WinXP resolves linux1 to its
> correct address.
>
> You may have a firewall problem. Are your linux boxes configured to
> drop echo requests from WinXP? Is your WinXP box firewalled to drop
> echo replies from the LAN?
>
> You may have a routing problem, in which case WinXP knows linux1's
> address but doesn't know how to find it. What does 'route PRINT' show
> on WinXP?
>
> --
> To reply by email, replace "deadspam.com" by "alumni.utexas.net"

stef wrote:

please, don't top post -- it makes responding in context difficult
[re-arranged]

> "Andrew Schulman" <(E-Mail Removed)> wrote in message
> news:175w09gx3p6sc$.(E-Mail Removed).. .
> >
> > > WinXP can access to internet but cannot ping linux1 and linux 2
?????
> > > why ?
> > >
> > > By the way on WinXP, if I try C:\>nslookup linux1 (for example)
> > > everything is ok, I get :
> > > Server : SERVER1
> > > Address: 192.168.13.1
> > >
> > > Name : linux1
> > > Address: 192.168.13.5
> > >
> > > What's the problem win XP ??
> >
> > Well you don't have a DNS problem, since WinXP resolves linux1 to
its
> > correct address.
> >
> > You may have a firewall problem. Are your linux boxes configured
to
> > drop echo requests from WinXP? Is your WinXP box firewalled to
drop
> > echo replies from the LAN?
> >
> > You may have a routing problem, in which case WinXP knows linux1's
> > address but doesn't know how to find it. What does 'route PRINT'
show
> > on WinXP?
>
> Thanx for your answer...
>
> Well, in fact any Windows on the LAN cannot ping !?

Use copy-n-paste to give us your XP command and output exactly. Eg.,
how does pinging by IP work? Errors? Pinging by name? Errors?
Responses? What do you get when pinging the ladder -- ie., work from
localhost, to default gw, to name server, to other hosts? By IP? By
name?

> The iptables on SERVER1 is down.

What about XP's firewall? Can you ping yahoo.com and get a response on
screen?

> All the route are the same for each boxes
> All Unix are ok (I have also a Solaris 10 x86 which "works"/ping
perfectly)
>
>
> I don't understand at all
>
> damn...

Yep, know the feeling

There's some detail you/we are overlooking but you have the data and
must share it _exactly_ as it appears on the console.

Offhand, I can't think why XP is not doing proper (name?) lookups when
pinging. Did you try tracert? Tcpdump? Ethereal? We may need to
know just what packets are being sent, received, and replied and (not?)
received.

XP arp can sometimes be funky, so seeing the arp packets (as well as
the ping packets) may be good to look at. Is XP reading arps?

regards,
prg
email above disabled

> Well, in fact any Windows on the LAN cannot ping !?

Can you telnet from Windows to some open port on one of the Linux boxes?

--
To reply by email, replace "deadspam.com" by "alumni.utexas.net"

Ok , I found... more exactly I've read the doc

Sorry it's my fault :

It seems Windows is not very "compliant" with DNS, read this :

dnsmasq oc :
....Resolver code sometime does strange things when given names without
any dots in. Win2k and WinXP may not use the DNS at all and just
try and look up the name using WINS. On unix look at "options ndots:"
in "man resolv.conf" for details on this topic. Testing lookups
using "nslookup" or "dig" will work, but then attempting to run
"ping" will get a lookup failure, appending a dot to the end of the
hostname will fix things. (ie "ping myhost" fails, but "ping
myhost." works. The solution is to make sure that all your hosts
have a domain set ("domain" in resolv.conf, the network applet in
windows, or set a domain in your DHCP server). Any domain will do,
but "localnet" is traditional. Now when you resolve "myhost" the
resolver will attempt to look up "myhost.localnet" so you need to
have dnsmasq reply to that name. The way to do that is to include
the domain in each name on /etc/hosts and/or to use the
--expand-hosts and --domain-suffix options.


Ho my... not so... easy to find !!

Sometimes Windows is very... disturbing



anyway thanx for your answers guys !

> It seems Windows is not very "compliant" with DNS, read this :
>
> dnsmasq oc :
> ...Resolver code sometime does strange things when given names without
> any dots in. Win2k and WinXP may not use the DNS at all and just
> try and look up the name using WINS. On unix look at "options ndots:"
> in "man resolv.conf" for details on this topic. Testing lookups
> using "nslookup" or "dig" will work, but then attempting to run
> "ping" will get a lookup failure, appending a dot to the end of the
> hostname will fix things. (ie "ping myhost" fails, but "ping
> myhost." works. The solution is to make sure that all your hosts
> have a domain set ("domain" in resolv.conf, the network applet in
> windows, or set a domain in your DHCP server). Any domain will do,
> but "localnet" is traditional. Now when you resolve "myhost" the
> resolver will attempt to look up "myhost.localnet" so you need to
> have dnsmasq reply to that name. The way to do that is to include
> the domain in each name on /etc/hosts and/or to use the
> --expand-hosts and --domain-suffix options.

Yikes. What a pile of crap! Anyway, glad you solved your problem.

--
To reply by email, change "deadspam.com" to "alumni.utexas.net"

stouf wrote:
> Heloo guys...
>
> Could you help me please?
>
> I'm running a linux box with DNSMASQ (let's call it SERVER1 on
> 192.168.13.1)
> inside there's /etc/hosts with :
> linux1 192.168.13.5
> linux2 192.168.13.6
> winxp 192.168.13.10
>
> the /etc/resolv.conf
> nameserver 194.xx.xx.xx (direct internet)
>
>
> Everything is ok, all the machine in LAN have gateaway and DNS set on
> SERVER1, but...
>
> linux boxes "ping" perfectly everything (lan+wan)
>
> WinXP can access to internet but cannot ping linux1 and linux 2 ?????
> why ?
>
> By the way on WinXP, if I try C:\>nslookup linux1 (for example)
> everything is ok, I get :
> Server : SERVER1
> Address: 192.168.13.1
>
> Name : linux1
> Address: 192.168.13.5
>
>
> What's the problem win XP ??
>

Windows cannot ask for a single-part host name in the local network.
It will append .localdomain to the single-part names.

Add aliases like this:

192.168.13.5 linux1 linux1.localdomain

to the /etc/hosts file in the dnsmasq host.

The same seems to apply for MAC OSX clients.

--

Tauno Voipio
tauno voipio (at) iki fi