[svlug] mount, smbfs, ssh, and local console weirdness

[Richard Sharpe]

On Tue, 6 Aug 2002, David Christensen wrote:

> svlug at lists.svlug.org:
> 
> "Richard Sharpe" <rsharpe at ns.aus.com> wrote:
> > ...
> > The problem, AFAICS, related to smbfs and the fact that all access are
> > being mapped to a particular user on the Win2K machine.
> >
> > It might be useful to see a trace of what happens when the error
> > occurs.
> 
> Thank you for your help. :-)
 
I was hoping for a wire trace, but since the problem seems to have gone 
away, no need :-)
 
> I looked around the filesystem and found the following:
> 
>     root at r7320g:/var/log/samba# l
>     ./   smbmount.log    smbmount.log.2  smbmount.log.4
>     ../  smbmount.log.1  smbmount.log.3
 
Yes, a lot of log files will be found here ...

> I then tried to reproduce the error (to create a new log entry), but now
> it works (the error is gone)!  I built and installed kernel 2.4.19 and
> its modules today, maybe that's it?  Or, maybe I needed to tell some
> service to re-read a configuration file after I made the initial
> changes, and rebooting did that for me?  I dunno...  Oh well, its
> working now.
> 
> 
> But, I looked through the logs above anyway and found the following in
> smbmount.log.1.  This might be the clue we were looking for:
> 
>     [2002/08/01 14:18:55, 0] tdb/tdbutil.c:tdb_log(475)
>       tdb((null)): tdb_open_ex: could not open file /var/cache/samba/un
> expected.tdb: No such file or directory

Hmmm, nmbd, I think, should create this file on the fly. Some Windows code 
is borken, and sends UDP responses back on port 137 rather than to the 
source port the request came from. Samba deals with them by putting them 
in the unexpected TDB where the sender can search for them. 

> Digging some more:
> 
>     root at r7320g:/var/cache/samba# l
>     ./  ../
> 
> 
> So, indeed /var/cache/samba/unexpected.tdb does not exist.
> 
> 
> Does it make any sense to you?

Yes, but I would not expect it to have anything to do with your problem 
because your Linux machine would have a TCP connection to the server and 
would not receive any unexpected packets in relation to what you were 
attempting.

Regards
-----
Richard Sharpe, rsharpe at ns.aus.com, rsharpe at samba.org, 
sharpe at ethereal.com