odd nmbd thing

[Christopher R. Hertel]

Take a look at the error messages in your log.  The phrase "from IP %s"
will give you the IP of the client station that is trying to register a
name via unicast.  Check the configuration of that client station and make
sure that they have not listed your server as a primary or secondary WINS
server. 

If the clients use DHCP then you'll have to fix the entries in the DHCP
server. 

Hope that helps.

Chris -)-----

> Found this code in nmbd/nmbd_incomingrequests.c today; it's been getting
> triggered a lot recently.
> 
>   if(!bcast)
>   {
>     /* We should only get broadcast name registration packets here.
>        Anyone trying to register unicast should be going to a WINS
>        server. If the code gets here, then either we are not a wins
>        server and they sent it anyway, or we are a WINS server and
>        the request was malformed. Either way, log an error here.
>        and send an error reply back.
>      */
>     DEBUG(0,("process_name_registration_request: unicast name registration
> request \
> received for name %s from IP %s on subnet %s. Error - should be sent to WINS
> server\n",
>           nmb_namestr(question), inet_ntoa(from_ip), subrec->subnet_name));
> 
> 
>     send_name_registration_response(FMT_ERR, 0, p);
>     return;
>   }
> 
> I know the server I'm seeing these errors on isn't a WINS server, so it must
> be the former case (someone's trying to register unicast with it, when it
> shouldn't).  The question is, under what circumstances will that occur (at
> least that we know about), and why?
> 


-- 
Christopher R. Hertel -)-----                   University of Minnesota
crh at nts.umn.edu              Networking and Telecommunications Services

    Ideals are like stars; you will not succeed in touching them
    with your hands...you choose them as your guides, and following
    them you will reach your destiny.  --Carl Schultz