Multiple (minor) problems

[Nicholas Tang]

I spent around an hour yesterday hunting through the archives looking for
answers to these problems - if they were there and I just didn't find
them, I'm apologizing in advance.

Anyway... I recently upgraded our Irix 6.4 (Origin 200) server from
1.9.18p8 to 2.0.3.  Since then we've noticed several strange problems and
I can't figure out how to fix them.

First off, here's our setup as reported by Swat:

# Global parameters
          workgroup = xxx
          server string = CG Server
          security = SERVER
          encrypt passwords = Yes
          password server = xxx
          log file = /usr/local/samba/var/log.%m
          max log size = 500
          socket options = TCP_NODELAY
          load printers = No
          dns proxy = No
          remote announce = xxx.xxx.xxx.255
          hosts allow = xxx.xxx.xxx.0/255.255.255.0,
xxx.xxx.xxx.0/255.255.255.0, 127.0.0.1

  [xxx]
          path = /xxx
          force group = prod
          read only = No
          create mask = 0664
          directory mask = 0775

  [xxx]
          path = /xxx
          force group = prod
          read only = No
          create mask = 0664
          directory mask = 0775

  [xxx]
          path = /xxx
          read only = No
          create mask = 0664
          directory mask = 0775

  [xxx]
          path = /xxx
          read only = No
          create mask = 0664
          directory mask = 0775

  [xxx]
          path = /xxx
          create mask = 0664
          directory mask = 0775

(where you see "xxx" just means I blanked it out)

1.) Connecting via network neighborhood - when you open up the server in
Network Neighborhood it takes a good 5-10 seconds before it actually
displays the active shares on that server, and until then the server
window is frozen (the rest works fine).  This occurs when using Win NT
workstation 4.0 SP4 - we don't use Win 9x.  This isn't a major problem but
is definitely an inconvenience!  This didn't happen with 1.9.18.  Also, I
tried setting "dead time = 0" (I know it defaults but I wanted to make
sure) and it made no difference.

2.) Connection failures - periodically when trying to connect, especially
after a decent amount of idle time, it will fail to authenticate and will
say the connection is denied.  In the log files this is what shows up:

[1999/04/14 14:54:50, 1] smbd/password.c:(1127)
  password server xxx rejected the password
[1999/04/14 14:54:50, 1] smbd/password.c:(500)
  Couldn't find user 'ntang' in smb_passwd file.
[1999/04/14 14:54:50, 1] smbd/password.c:(500)
  Couldn't find user 'ntang' in smb_passwd file.
[1999/04/14 14:55:10, 0] smbd/password.c:(164)
  Unable to initgroups. Error was Invalid argument
[1999/04/14 14:55:10, 0] smbd/password.c:(169)
  This is probably a problem with the account nobody
[1999/04/14 14:55:10, 1] smbd/service.c:(488)
  xxx (xxx.xxx.xxx.xxx) connect to service xxx as user ntang
(uid=xxxx, gid=xxxx) (pid 16477)

It's possible those are two separate problems coming up - there was a 20
second delay from the first set of errors to the 2nd.  The password server
is our PDC, running on a WIN NT 4.0sp4 server, running WINS.

3.) Speed - just in general, I had expected a decent speed increase - it's
possible my configuration is just stupid, but it doesn't seem any faster
than before.  In fact it feels a little slower, even - we haven't had a
chance to do any real benchmarking but it seems a little more sluggish, at
least for file browsing.  It's possible the actual file transfers are
faster.

4.) Samba and Shiva - we have a Shiva remote access modem server-thingy.
(That's the technical term. (I didn't sleep (at all) last night.))  When
people are dialed into it and on the network, they can browse the NT file
servers as if they were on the local network (in essence, they are).
However, when they try to browse the Samba servers (all Irix 6.4 and 6.2
boxes) they can open the server in the Net'hood, and open each of the
shares, but then they can't get to the subdirectories.  Ie, if we had
server "foo" with share "bar" with subdirectory "baz", they could open up
"foo" (\\foo), open the "bar" share (\\foo\bar), but then can't get into
"baz" (\\foo\bar\baz).  This happens both with 1.9.18 and 2.0.3.

Nicholas

======================================================================
Nicholas Tang     Senior System Administrator     R/GA Digital Studios
ntang at rga.com       (212) 946-4224 (voice)        (212) 946-4010 (fax)
======================================================================