named error messages in log file, how to fix?

Roy Arends Roy.Arends at nominum.com
Sun Jun 24 22:46:53 UTC 2001


On Sun, 24 Jun 2001 zz at rockstone.com wrote:

> 
> > At 4:47 PM -0400 6/24/01, zz at rockstone.com wrote:
> > 
> > >  192.168.1.61 is a Win98 machine with only TCP/IP,Client for MS
> > >  network and file sharing protocal/service installed.
> > >  And I do NOT have Samba running on this RH7.1 linux, nor
> > >  have port 137 to 139 open, I don't understand why the linux
> > >  machine attempts to talk to the Win98 with Netbios protocol
> > >  as indicated using port 137.
> > >  Any suggestions what's likely the problem and how to
> > >  fix it?  thank you.
> > 
> > 	All PCs try to talk to everything on ports 137-139.  However, if 
> > the machine at the other end isn't speaking NetBIOS or NetBEUI, then 
> > they most likely won't be able to respond in a manner that PCs will 
> > understand.
> 
> thanks for your reply, I had the PC using tcp ip as default 
> protocol, and I think this is not Win98's problem, but 
> bind configuraiton problem. 

??????

Win98 sends a query from source port 137 (netbios-ns) to destination
port 53 (domain).

Named answers the query from source port 53 (domain) to destination port
137 (netbios-ns).

Named can not send the packet to destination port 137.

Named logs messages stating the above.

This is windows sending a query while denying the query-response (or due
to some firewall).

Make it accept the response, or make it not sending the query.

Your problem is not caused by BIND configuration, no matter how severe
your RH box was hacked.

Roy Arends
Nominum




More information about the bind-users mailing list