Logon Problems ...

[MCCALL,DON (HP-USA,ex1)]

Hi Lee,
the oplock break stuff is telling you that user melaniel (on smbd pid 4718)
has made a request to 
access a file that Samba believes there is an oplock on.  Samba then sends
an oplock break request
to the pid of the smbd process that he believes HOLDS that oplock.  The 'no
response received to..."
indicates that either that smbd process is hung or gone for some reason.
You may want to turn up log level,  and use smbstatus to determine what
machine was being serviced on
the pid that is referenced in the "no response received" message.  Then you
can take a look at the log file
for that machine and determine what the last thing it was doing, which
should help in determining why it's hung
up, or disappeared...
If smbstatus doesn't show that pid as active for any machine, then you are
reduced to doing a grep on your 
log.<machine> files for "(pid xxxx)" to determine which is the appropriate
log file to examine.
 
Good luck,
Don

-----Original Message-----
From: C.Lee Taylor [mailto:lee.taylor at aeroton.scania.co.za]
Sent: Friday, April 20, 2001 4:24 AM
To: samba at samba.org
Subject: Logon Problems ...


Greetings go to all Samba users and developers ... 
 
I seem to have pick up a very strange problem with Samba 2.0.7 on a RedHat
7.0 installation ...
All was working fine for quite a few months seeing that I upgraded to RH 7.0
pf late ( The last three months, I think ) 
The last few days, I have found that users are having problems logon to the
network.  
 
I have been wondering if I should upgrade to Samba 2.2, but I am a little
worried that this will not help ... thinking this is an oplock problem ...
pobbile that there are not enough oplocks or something like that ...
 
Could somebody help me with this ... Thanks ...
 
Getting errors like this in the machine log ...
[2001/04/20 09:05:34, 1] smbd/service.c:make_connection(550)
  melanie-lewis (10.1.1.62) connect to service software as user melaniel
(uid=51
3, gid=100) (pid 4718)
[2001/04/20 09:05:52, 0] smbd/oplock.c:request_oplock_break(1204)
  request_oplock_break: no response received to oplock break request to pid
3957
 on port 1100 for dev = 301, inode = 3664695
  for dev = 301, inode = 3664695, tv_sec = 3adfd51f, tv_usec = 7f11f
[2001/04/20 09:05:52, 1] smbd/service.c:close_cnum(583)
  melanie-lewis (10.1.1.62) closed connection to service netlogon

And messages like this in the log.nmb ...
[2001/04/20 08:19:06, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70)
  process_logon_packet: Logon from 10.1.1.251: code = 0x7
[2001/04/20 08:19:50, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70)
  process_logon_packet: Logon from 10.1.1.66: code = 0x0
[2001/04/20 08:19:57, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70)
  process_logon_packet: Logon from 10.1.1.66: code = 0x0
[2001/04/20 08:20:16, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70)
  process_logon_packet: Logon from 10.1.1.66: code = 0x7
[2001/04/20 08:21:31, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70)
  process_logon_packet: Logon from 10.1.1.252: code = 0x7
[2001/04/20 08:24:07, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70)
  process_logon_packet: Logon from 10.1.1.66: code = 0x0
[2001/04/20 08:24:49, 1] nmbd/nmbd_processlogon.c:process_logon_packet(70)
  process_logon_packet: Logon from 10.1.1.96: code = 0x0