Problem with [homes]: NT maintains connection

Problem with [homes]: NT maintains connection

Post by Bob Lyon » Tue, 03 Mar 1998 04:00:00



Hi,

I've read in various Samba documents that NT sometimes maintains an open
connection to a share between logins. But with the following smb.conf I
can get the NT box to maintain an open share to some one else's home
directory (with fuill read write permission). If I log in as user1, I
get a share called "homes" that mounts user1's home directory just fine.
Then I log out and log back in as user2; the "homes" share is there, but
its user1's home directory! And I can write all over it. (By the way,
why is it that the name of the share is not the name of the user?)

What is up with that? Thanks for any help you can offer.

[global]

logon home              = \\%h\%U\NT
logon path              = \\%h\%U\NT\profile
max log size            = 50
lpq command             = /usr/bin/lpq %p
lprm command            = /usr/bin/lprm -P%p %j
password server         = CNRNTS01
security                = server
server string           = Samba %v on %h
wins server             = myserver
workgroup               = CNR-DOM2
encrypt passwords       = yes
smb passwd file         = /etc/smbpasswd
load printers           = no

[homes]

comment                        = %U's Unix Home Directory on %h
volume                 = %U's Home on %h
path                   = %H/NT
browseable             = no
writable               = yes

 
 
 

1. connection maintain problem

I am having a problem with maintaining connections on my SAMBA servers.  And
end user may be right in the middle of an operation and the application
suddenly tells them that the workspace is not in use (ie. it is not
connected or not available for connection).  I have a feeling that it may be
oplock problems.  I see this recurring in my log file:

[2001/04/05 14:55:53, 0] smbd/oplock.c:oplock_break(905)
  oplock_break resend
[2001/04/05 14:56:03, 0] smbd/oplock.c:oplock_break(905)
  oplock_break resend
[2001/04/05 14:56:13, 0] smbd/oplock.c:oplock_break(905)
  oplock_break resend
[2001/04/05 14:56:15, 0] smbd/oplock.c:request_oplock_break(1136)
  request_oplock_break: no response received to oplock break request to pid
5592 on port 4387 for dev = 21002e,
inode = 1643871
  for dev = 21002e, inode = 1643871, tv_sec = 3accbf9e, tv_usec = a9f9c
[2001/04/05 14:56:23, 0] smbd/oplock.c:oplock_break(922)
  oplock_break: receive_smb timed out after 30 seconds.
  oplock_break failed for file tlc/masthead/data/patient.dat (dev = 21002e,
inode = 1643871).
[2001/04/05 14:56:23, 0] smbd/oplock.c:oplock_break(992)
  oplock_break: client failure in break - shutting down this smbd.

This may or may not be the cause of the problems.  If anyone has any
suggestions, it would be appreciated!

Thanks

Bruce M. Campbell

2. IRC Meetings on Sundays

3. Laptop connection to home network problem

4. CreateProcess & WinOldAp

5. How can I maintain RWX file permission btween NT&UX ?

6. Inquiry: Free/commercial tcp/ip protocol drivers sought.

7. Maintain NT security, ACL's etc using ADSI

8. Search a Profibus IP module with monitoring capabilities

9. Problem accessing Home Directories from Win NT

10. problem connecting Unix-home with NT login

11. Problems with win95/NT/Samba net use s: /home

12. Domain controller connection problems in NT Logon server manager etc.

13. NT CLIENT CONNECTION PROBLEM