libsmbclient and smb_opendir: problem with workgroup

[Christopher R. Hertel]

Okay, that's weird.

nmbd is obviously running and I assume that you can get to shares on the 
server, so smbd must be running...

Try one more thing for me:  'nslookup DUCKMAN'

I think I see the problem.  I've just done some testing and I think I get 
three points for this one (if I'm right).

Does the DNS entry match the NetBIOS lookup?  Same IPs?

I was able to produce a similar problem at my end.  Turns out that the DNS 
entry doesn't match.  When I use nmblookup for the name "FOO" I get one 
IP, but when I do a DNS lookup I get a different IP.

Try this as well:  'smbclient -R "bcast wins" -N -L DUCKMAN"'

Let me know if that works.  :)

Chris -)-----

On Mon, Jun 14, 2004 at 12:13:32PM -0300, Andreas wrote:
> On Sat, Jun 12, 2004 at 05:57:54PM -0500, Christopher R. Hertel wrote:
> > Are you sure that filesharing is enabled on that system?  Do an 
> >   'nmblookup -S duckman'
> > If the duckman<20> name is not registered, the there is no sharing active.
> 
> [andreas at pandora andreas]$ nmblookup -S duckman
> querying duckman on 10.0.7.255
> 10.0.4.149 duckman<00>
> Looking up status of 10.0.4.149
>         DUCKMAN         <00> -         B <ACTIVE>
>         DUCKMAN         <03> -         B <ACTIVE>
>         DUCKMAN         <20> -         B <ACTIVE>
>         ..__MSBROWSE__. <01> - <GROUP> B <ACTIVE>
>         MYGROUP         <00> - <GROUP> B <ACTIVE>
>         MYGROUP         <1d> -         B <ACTIVE>
>         MYGROUP         <1e> - <GROUP> B <ACTIVE>
> 
>         MAC Address = 00-00-00-00-00-00
> 
> > Why would it do that?  Are you certain that this particular node is the 
> > Local Master Browser?  Try doing:
> >   'nmblookup -B 255.255.255.255 MYGROUP#1D'
> 
> [andreas at pandora andreas]$ nmblookup -B 255.255.255.255 "MYGROUP#1D"
> querying MYGROUP on 255.255.255.255
> 10.0.4.149 MYGROUP<1d>
> 
> > and then send a
> >   'nmblookup -A <IP>'
> 
> [andreas at pandora andreas]$ nmblookup -A 10.0.4.149
> Looking up status of 10.0.4.149
>         DUCKMAN         <00> -         B <ACTIVE>
>         DUCKMAN         <03> -         B <ACTIVE>
>         DUCKMAN         <20> -         B <ACTIVE>
>         ..__MSBROWSE__. <01> - <GROUP> B <ACTIVE>
>         MYGROUP         <00> - <GROUP> B <ACTIVE>
>         MYGROUP         <1d> -         B <ACTIVE>
>         MYGROUP         <1e> - <GROUP> B <ACTIVE>
> 
>         MAC Address = 00-00-00-00-00-00
> 
> 
> [andreas at pandora andreas]$ smbclient -L DUCKMAN -N
> session request to DUCKMAN failed (Call timed out: server did not respond after 20000 milliseconds)
> session request to *SMBSERVER failed (Call timed out: server did not respond after 20000 milliseconds)
> 
> But let's not forget, I don't have a problem with this particular error with
> the DUCKMAN machine. It's just that it is causing other things to break.
> 
> > I'm speculating.  I haven't looked at the code and I don't know how the
> > query is sent out.  I have a long list in my head of things that could go 
> > wrong.  I'd need a better idea of how the network is layed out, the full 
> > config, and packet traces to really know what's up.
> 
> I'm working on that. The network is a simple switched LAN but with several
> smb servers.
> 

-- 
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/     -)-----   crh at ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org