> > http://support.microsoft.com/kb/204279
> 
> Using the procedure described in that article, I verified that
> the computer in question *is* running NetBIOS (it has both the
> "direct hosted" and "NBT" transports).

OK.

> If I run "snoop host rosalind" and "smbutil lookup rosalind",
> I get no snoop output.

That's odd.  Did you run snoop on the machine where you're
trying to use the Solaris CIFS client?  You should see something.
Here's a good snoop command line if you want just NetBIOS/SMB:
 snoop -o /tmp/output.snoop port 137 or port 138 or port 139 or port 445

Then use: wireshark /tmp/output.snoop

> If I run snoop and exclude communication with a few other hosts
> (e.g., punch-sfbay.sun.com, the desktop machine where I'm typing
> the commands into an ssh window), all I get is:
[an ARP "who is"]
> Would the fact that I'm punched-in make any difference?  I've got it
> configured for "allow local LAN".

Possibly, yes.  It may block UDP - I don't remember.

> Here's what I get on Linux...
> $ smbclient -N -R bcast -L nissan
[finds samba]
> You can see the four machines on my network.
> 
> Then I tried:
> $ smbclient -N -R bcast -L rosalind
[finds Windows 2000]
> I get similar information for "dell4600".  "rosalind is in the
> local /etc/hosts file, "dell4600" isn't.
> 
> This seems to indicate that the WINS name server on nissan is working.
> 
> What else should I do to figure out why smbutil isn't working?


The snoop capture is the best way to figure this out.
You should see NetBIOS name requests from your CIFS client,
either broadcast, or to the configured WINS, or both.

Trying without punchin running would be a good idea.

Gordon


_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss

Reply via email to