timeout_processing(868)

[Chance C. Geurin]

We've been successfully running Samba 2.0.5a for a while now on Linux and 
Solaris servers with Win98 and NT clients.  We're using non-encrypted 
passwords.  Recently, two NT clients have been exhibiting the following error 
message on reconnecting a share a bootup:

\\Pike is not accessible.  A remote procedure call (RPC) protocol error 
occurrred.

If you continue to boot, Pike can then be accessed.  Pike is a Linux server 
(running 2.2.10).  The NT clients in question have no problem accessing a 
Solaris server.  The corresponding log entries on Pike are as follows:

[1999/10/28 12:24:49, 1] smbd/service.c:make_connection(521)
  oxford (192.168.1.85) connect to service public as user twandell 
(uid=10283, gid=10) (pid 31229)
[1999/10/28 12:31:23, 0] lib/util_sock.c:read_socket_data(507)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[1999/10/28 12:31:23, 1] smbd/service.c:close_cnum(557)
  oxford (0.0.0.0) closed connection to service public
[1999/10/28 12:39:01, 0] smbd/process.c:timeout_processing(868)
  Reloading services after SIGHUP
[1999/10/28 12:39:06, 1] smbd/service.c:make_connection(521)
  oxford (192.168.1.85) connect to service public as user twandell 
(uid=10283, gid=10) (pid 31597)

The receive failure made me think we had a physical problem, but moving the 
machine to a known good hub/cable combination makes no difference.

Any ideas would be _greatly_ appreciated.  Thanks!


Chance C. Geurin (chance at rtlogic.com)
RT Logic! (http://www.rtlogic.com)
Colorado Springs, Colorado

Any intelligent fool can make things bigger, more complex, and more violent.
It takes a touch of genius - and a lot of courage - to move in the opposite direction.
Albert Einstein