Log file error

[Igaduma]

Hi all,

When using an NT box to simply do a cut & paste this error is logged in the smbd.log file.

2002/06/11 10:48:43, 1, pid=28859, effective(0, 0), real(0, 0)] smbd/service.c:close_cnum(650)
it0392 (172.31.11.168) closed connection to service asset
[2002/06/11 10:48:55, 1, pid=28863, effective(100, 20), real(0, 0)] smbd/service.c:make_connectio
n(610)
it0392 (172.31.11.168) connect to service asset as user asset (uid=100, gid=20) (pid 28863)
[2002/06/11 10:49:32, 1, pid=28862, effective(0, 0), real(0, 0)] smbd/service.c:close_cnum(650)
it1949 (172.31.22.136) closed connection to service asset
[2002/06/11 10:49:58, 0, pid=28863, effective(0, 0), real(0, 0)] smbd/oplock.cplock_break(786)
oplock_break: receive_smb timed out after 30 seconds.
oplock_break failed for file jdr-1_0_1-win.exe (dev = 1540008, inode = 125538).
[2002/06/11 10:49:58, 0, pid=28863, effective(0, 0), real(0, 0)] smbd/oplock.cplock_break(859)
oplock_break: client failure in oplock break in file jdr-1_0_1-win.exe
[2002/06/11 10:50:58, 1, pid=28863, effective(0, 0), real(0, 0)] smbd/service.c:close_cnum(650)
it0392 (172.31.11.168) closed connection to service asset
root@vertigo>

Anyone any idea's ?

Thanks.

 

[Igaduma]

Hi all,

Problem "went away" when running NT4locking.reg regscript included with samba.
I ran this on each machine...but somehow forgot to run it on the problem machine...


Iga

 

[masopustc]

Hi all,

are the registry-settings described in "NT4locking.reg" still valid for Win2k? Or are there similar settings for 2k?

TIA,
christian

 

[Igaduma]

Hi there,

From other sources then this fairly silent forum I think I understood that W2k/XP needs the latest samba source to work 100%.
2k/XP features some nice new commands which do not play ball with older samba releases.
anyhow, I find microsofts implementation of it all pretty un-compliant to anything.

Right now my company is kicking off a project to roll-out XPclients & 2k servers, fully automated, over a timeframe of 1 weekend. We've got 1000 employees and about 2000 desktops, and +- 400 laptops.
About 30-40% of our software isn't signed for XP,even some mission-critical software isn't XP signed.
But, according to our WinTeam micro$oft will stop support for NT in summer 2003!
Like they need NT support every day.

um..then again..maybe they do! heheh

Somehow, I still feel safe with my NT-only compliant sambaserver for the moment...

IgA