[jcifs] no name with type 0x00 with no scope for host

Allen, Michael B (RSCH) Michael_B_Allen at ml.com
Wed Feb 20 11:53:55 EST 2002

> -----Original Message-----
> From:	Christopher R. Hertel [SMTP:crh at ubiqx.org]
> Sent:	Tuesday, February 19, 2002 7:43 PM
> To:	Allen, Michael B (RSCH)
> Cc:	jcifs at lists.samba.org
> Subject:	Re: [jcifs] no name with type 0x00 with no scope for host
> "Allen, Michael B (RSCH)" wrote:
> > 
> > > -----Original Message-----
> > > From: Christopher R.Hertel [SMTP:crh at ubiqx.org]
> :
> > > For some reason, Microsoft decided not to have XP register this name
> > > unless the XP system was running the client services.
> > >
> >         Register? So you're saying XP doesn't respond to node status?
> Of course they do, but you need to send the wildcard name, not the <00>
> name.  You can't count on the <00> name being registered.
> >         I don't know if all hosts respond to anything else. At least
> >         there's a comment in my code that reads:
> > 
> >             // type has to be 0x00 for node status
> Use "*\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0" for NODE STATUS REQUESTS.
	Same thing. The 16th byte is <00>.

>   It's a
> wierd name, I know, but it's actually in the RFCs.  It's an asterisk
> followed by 15 nul bytes, then encoded as usual.  It's the wildcard name.
> It is illegal to register it, but all NBT nodes are supposed to respond to
> it (within the proper scope ID, of course).  It is also the precursor to the
> "*SMBSERVER" name.
	What is, node status? Actually at this point sending the node status *after*
	SMBSERVER is a little better I think. The node status is a last resort.


More information about the jcifs mailing list