Discussion:
Various evfsguiv2.0b5 questions
Pete Brown
2009-11-17 17:17:50 UTC
Permalink
Hi Herwig

Does evfsgui interact OK with IBM Peer systems? - or do other systems in
my workgroup need to be running samba server?


I ask because I am not getting very encouraging results from either
evfsgui 1.3 or 2.0beta5 - both builds have problems accessing shared
directories on my peer network.

I have installed the files from evfsgui-20beta5-20091115.zip and
smbclut-3.0.37-os2-20091023.zip to l:\samba

I already had evfs.ifs and evfsctl.exe loaded as they were already in
the config.sys file so started evfsgui2.0b5 and saw the message about
the missing smb.conf file.


The Network neighbourhood panel is empty and stays that way after I
click Refresh; the animated icon suggests something happening but no
peer network is displayed when that icon disappears.


I changed the View to Dialog and selected Mount: All servers in
workgroup, specified Workgroup: THEBROWNS - note: no workgroup displayed
in the dropdown list - entered my Peer Id and Password and selected to
Mount to U:\THEBROWNS

The result was a sys0067 - the network name cannot be found

I do have U:\THEBROWNS displayed in the Current Resources panel though.
I decided to try and mount each peer system below that Mount point.

I selected Mount: All shares on server, Server: THEWENCH - no servers
displayed in the dropdown list, Workgroup: THEBROWNS, entered my Peer Id
and Password and selected to Mount to U:\THEBROWNS\THEWENCH

As that seemed to work I thought I'd add other servers by simply
changing the name of the server and Mount to location.
That worked and I now have all 3 systems, THEWENCH, BOYZONE and DISKZONE
showing in the Network neighbourhood panel.

I saved the configuration as LOSEPETE.evp - in the l:\samba directory.

I clicked the File, Autostart option and this error was displayed:-

Line 23 of PB_CONDET_SAVE_Click in evfsgui.VRM:
+++ resdata = resdata || VRMethod('CN_CONDET',
'GetFieldData, records.i, CD.mpointFH) || '';


No object created in the Startup folder...

I had a desktop backup with the eCS EVFSgui autostart object so copied
that into the Startup folder and modified File and path name to point to
EVFSgui 2.0b5 and parameters to point to losepete.evp.

That seemed to work fine after a reboot.


However, as I later discovered, if any of the systems is powered off
when EVFsgui autostarts that generates some error messages. This
happened when my system was the only system booted:-

"SYS0067 network name cannot be found" - cannot find the workgroup
THEBROWNS... wonder why?

3 of "SYS0058 specified server cannot perform requested operation" -
well, they not not booted so I'd expect that.

All of the above required a click on the OK button before the app continued.

Would it not be better to deliver an error message indicating which
connections failed at the end of the startup - rather than a potential
series of errors during startup?



A very related problem is that any of the systems that were powered off
when EVFsgui autostarted do not become available if they are later
powered on.

I booted 1 of the other systems and confirmed it was accessible from
File and Print Client. It is not accessible using the EVFSgui autostart
Mounted drive letter in my drives folder though... This is
U:\THEBROWN\DISKZONE and it does not seem to be possible to "Refresh"
the connection without Unmounting and then re-Mounting - or am I missing
something?


On testing EVFSgui I still find problems accessing shared directories on
the network. Here is a typical example:-

THEWENCH\GDRIVE\TEMP is fully accessible using Peer.

Using the DIR command on that directory locally (from THEWENCH) we see
36 folders (I counted) and 839 files using 266,935,295 bytes, last few
lines of dir output:-

15-01-06 4:12p 2,145 225 a--- usbdisk.txt
1-08-06 2:42a 1,732 226 a--- usbdrive.txt
20-09-07 11:18p 30,427 280 a--- via.zip
7-09-06 3:26p 1,197,628 432 a--- warpin-1-0-12.exe
11-12-06 8:22p 1,197,116 432 a--- warpin-1-0-14.exe
27-03-07 1:15a 1,199,676 0 a--- warpin-1-0-15.exe
26-09-09 1:19a 1,251,900 0 a--- warpin-1-0-19.exe
27-09-09 4:44p 1,243,831 319 a--- warpin-1-0-19.zip
839 file(s) 266,935,295 bytes used


Accessing using the EVFSgui mounted U:\THEBROWNS\THEWENCH\GDRIVE\TEMP
using the WPS I can see *2* directories and nowhere near as many files.
Using dir at a command prompt I get this (last few lines of dir output):-

22-10-09 2:54a 0 0 ---- FAP1569.TMP
22-10-09 2:54a 0 0 ---- FAP1569.TMP
22-10-09 2:54a 0 0 ---- FAP15A2.TMP
22-10-09 2:54a 0 0 ---- FAP15A2.TMP
22-10-09 2:54a 0 0 ---- FAP15A3.TMP
22-10-09 2:54a 0 0 ---- FAP15A3.TMP
22-10-09 2:54a 0 0 ---- FAP15EA.TMP
22-10-09 2:54a 0 0 ---- FAP15EA.TMP
22-10-09 2:54a 0 0 ---- FAP15EB.TMP
199 file(s) 50,428,180 bytes used


Yes, all listed files and directories are listed twice when using
eVFSgui connection - and a lot are not listed at all.

Hence the questions at the start of this post.


Regards

Pete
Herwig Bauernfeind
2009-11-17 18:14:23 UTC
Permalink
Hi Pete,
Post by Pete Brown
Does evfsgui interact OK with IBM Peer systems? - or do other systems
in my workgroup need to be running samba server?
Well, it is is not evfsgui itself that interacts with other systems, it
is evfs that interacts with other systems, evfsgui just manages the setup.
Anyway, the answer is yes, you can use evfs+evfsgui to connect to IBM
Peer systems or even LAN Server or WSEB.
Post by Pete Brown
I ask because I am not getting very encouraging results from either
evfsgui 1.3 or 2.0beta5 - both builds have problems accessing shared
directories on my peer network.
I have installed the files from evfsgui-20beta5-20091115.zip and
smbclut-3.0.37-os2-20091023.zip to l:\samba
I already had evfs.ifs and evfsctl.exe loaded as they were already in
the config.sys file so started evfsgui2.0b5 and saw the message about
the missing smb.conf file.
You might want to edit smb.conf and make the workgroup parameter match
your workgroup. At the moment only a default value is entered during
creation of the file, and this might be a problem if the "opponent" uses
a different workgroup. There is no GUI option/function yet to do this.
Look for smb.conf in %ETC%\samba
Post by Pete Brown
The Network neighbourhood panel is empty and stays that way after I
click Refresh; the animated icon suggests something happening but no
peer network is displayed when that icon disappears.
You might want to check what smbtree.exe shows: Open a command line and
run smbtree -N What does it show?
Post by Pete Brown
I clicked the File, Autostart option and this error was displayed:-
+++ resdata = resdata || VRMethod('CN_CONDET',
'GetFieldData, records.i, CD.mpointFH) || '';
Arrrgh! This is an error in evfsgui, I will fix it ASAP.
Post by Pete Brown
No object created in the Startup folder...
Normal, as the program crashed before doing so.
Post by Pete Brown
I had a desktop backup with the eCS EVFSgui autostart object so copied
that into the Startup folder and modified File and path name to point
to EVFSgui 2.0b5 and parameters to point to losepete.evp.
That seemed to work fine after a reboot.
Fine - that's a perfect workaround for the error.
Post by Pete Brown
A very related problem is that any of the systems that were powered
off when EVFsgui autostarted do not become available if they are later
powered on.
Right. This functionality has not been implemented yet (and probably
wont be in 2.0) . At the moment you only can right clock at a passive
connection to reconnect manually.

What really puzzles me (and I don't have an explanation for that yet):
For some reason browsing seems impossible in your network, I really
would like to know why, that's why I suggested the smbtree -N , because
if that does not show anything useful, the problem is in your network
and not in evfs+evfsgui (or at least evfs+evfsgui cannot do anything
about that).

However I can do browsing both in an IBM Peer network and in a Samba
network.

I am not sure if there isn't a misconception about EVFSGUI
functionality: You can browse workgroups, servers and shares in the
network neighbourhood, but you cannot browse files residing on a share
from within EVFSGUI.

Thanks for your feedback, it is appreciated, I hope we will be able to
resolve your problem,
kind regards,
Herwig B.
Pete Brown
2009-11-18 00:08:30 UTC
Permalink
Hi Herwig
Post by Herwig Bauernfeind
Hi Pete,
Post by Pete Brown
Does evfsgui interact OK with IBM Peer systems? - or do other systems
in my workgroup need to be running samba server?
Well, it is is not evfsgui itself that interacts with other systems, it
is evfs that interacts with other systems, evfsgui just manages the setup.
Right, thanks for the clarification.
Post by Herwig Bauernfeind
Anyway, the answer is yes, you can use evfs+evfsgui to connect to IBM
Peer systems or even LAN Server or WSEB.
That was my understanding - just wanted to make sure I had not got that
wrong.
Post by Herwig Bauernfeind
Post by Pete Brown
I ask because I am not getting very encouraging results from either
evfsgui 1.3 or 2.0beta5 - both builds have problems accessing shared
directories on my peer network.
I have installed the files from evfsgui-20beta5-20091115.zip and
smbclut-3.0.37-os2-20091023.zip to l:\samba
I already had evfs.ifs and evfsctl.exe loaded as they were already in
the config.sys file so started evfsgui2.0b5 and saw the message about
the missing smb.conf file.
You might want to edit smb.conf and make the workgroup parameter match
your workgroup. At the moment only a default value is entered during
creation of the file, and this might be a problem if the "opponent" uses
a different workgroup. There is no GUI option/function yet to do this.
Look for smb.conf in %ETC%\samba
Changed the line workgroup = WORKGROUP to workgroup = THEBROWNS, saved
smb.conf and restarted evfsgui. Nothing shows in Network neighbourhood
when the animated icon disappears.
Post by Herwig Bauernfeind
Post by Pete Brown
The Network neighbourhood panel is empty and stays that way after I
click Refresh; the animated icon suggests something happening but no
peer network is displayed when that icon disappears.
You might want to check what smbtree.exe shows: Open a command line and
run smbtree -N What does it show?
Umm...

[L:\MPTN\ETC\samba]smbtree -N

[L:\MPTN\ETC\samba]


That does not look very promising.
Post by Herwig Bauernfeind
Post by Pete Brown
I clicked the File, Autostart option and this error was displayed:-
+++ resdata = resdata || VRMethod('CN_CONDET',
'GetFieldData, records.i, CD.mpointFH) || '';
Arrrgh! This is an error in evfsgui, I will fix it ASAP.
Post by Pete Brown
No object created in the Startup folder...
Normal, as the program crashed before doing so.
Post by Pete Brown
I had a desktop backup with the eCS EVFSgui autostart object so copied
that into the Startup folder and modified File and path name to point
to EVFSgui 2.0b5 and parameters to point to losepete.evp.
That seemed to work fine after a reboot.
Fine - that's a perfect workaround for the error.
Post by Pete Brown
A very related problem is that any of the systems that were powered
off when EVFsgui autostarted do not become available if they are later
powered on.
Right. This functionality has not been implemented yet (and probably
wont be in 2.0) . At the moment you only can right clock at a passive
connection to reconnect manually.
Presumably the above means in the evfsgui Connections panel as RMB does
not work for those shared drives/directories/files displayed using the
Mounted drive object.
Post by Herwig Bauernfeind
For some reason browsing seems impossible in your network, I really
would like to know why, that's why I suggested the smbtree -N , because
if that does not show anything useful, the problem is in your network
and not in evfs+evfsgui (or at least evfs+evfsgui cannot do anything
about that).
Having a network that works fine apart from with evfs tends to lead me
to think the problem is within evfs though. As networking is not
otherwise a problem I do not have a "troubleshooting" start point to try
to find the cause.

All systems here belong to the workgroup THEBROWNS which works fine for
File and Print Client but seems to be a cause of a problem with evfs as
the workgroup name is not found.
Post by Herwig Bauernfeind
However I can do browsing both in an IBM Peer network and in a Samba
network.
I am not sure if there isn't a misconception about EVFSGUI
functionality: You can browse workgroups, servers and shares in the
network neighbourhood, but you cannot browse files residing on a share
from within EVFSGUI.
I'm trying to see all files in a directory using the drive object,U:, in
the drives folder that has been created as the root of all available
connections not through evfsgui.
Post by Herwig Bauernfeind
Thanks for your feedback, it is appreciated, I hope we will be able to
resolve your problem,
kind regards,
Herwig B.
I installed the evfsgui-test file.

Yes, that creates a program object in the Startup folder.

Sadly the object is of no use as the Path and file name are missing.

When testing this I noticed that using File, Autostart is a bit of a "no
brainer". This is because this method of creating an object in the
Startup folder saves the current configuration as \os2\evfsgui.evp - no
use at all in a multi user system. I think that needs to offer to save
as \os2\evfsgui.evp with the option of the user being able to change the
location and file name.


I had a look through a newly generated log (\var\log\ndpsmb.log) and
noticed mention of printer requests

As evfsgui does not offer to print anything I am intrigued as to what it
is about:-

2009/11/17 20:28:39.32: 4 2: EALIst for <\ADMIN$>
2009/11/17 20:28:39.32: 4 2: ea_get_file list failed - ERRSRV -
ERRinvdevice (Invalid device - printer request made to non-printer
connection or non-printer request made to printer connection.)
2009/11/17 20:28:39.32: 9 2: NdpEAQuery <ADMIN$> 282 0 65332
2009/11/17 20:28:39.32: 9 2: NdpEAQuery in <\CDRIVE> 000e0000 41
2009/11/17 20:28:39.32: 4 2: EALIst for <\CDRIVE>
2009/11/17 20:28:39.32: 4 2: ea_get_file list failed - ERRSRV -
ERRinvdevice (Invalid device - printer request made to non-printer
connection or non-printer request made to printer connection.)
2009/11/17 20:28:39.32: 9 2: NdpEAQuery <CDRIVE> 282 0 65245
2009/11/17 20:28:39.32: 9 2: NdpEAQuery in <\DDRIVE> 000e0000 41
2009/11/17 20:28:39.32: 4 2: EALIst for <\DDRIVE>
2009/11/17 20:28:39.32: 4 2: ea_get_file list failed - ERRSRV -
ERRinvdevice (Invalid device - printer request made to non-printer
connection or non-printer request made to printer connection.)
2009/11/17 20:28:39.33: 9 2: NdpEAQuery <DDRIVE> 282 0 65158
2009/11/17 20:28:39.33: 9 2: NdpEAQuery in <\EDRIVE> 000e0000 41
2009/11/17 20:28:39.33: 4 2: EALIst for <\EDRIVE>
2009/11/17 20:28:39.33: 4 2: ea_get_file list failed - ERRSRV -
ERRinvdevice (Invalid device - printer request made to non-printer
connection or non-printer request made to printer connection.)
2009/11/17 20:28:39.33: 9 2: NdpEAQuery <EDRIVE> 282 0 65071
2009/11/17 20:28:39.33: 9 2: NdpEAQuery in <\FDRIVE> 000e0000 41
2009/11/17 20:28:39.33: 4 2: EALIst for <\FDRIVE>
2009/11/17 20:28:39.33: 4 2: ea_get_file list failed - ERRSRV -
ERRinvdevice (Invalid device - printer request made to non-printer
connection or non-printer request made to printer connection.)
2009/11/17 20:28:39.33: 9 2: NdpEAQuery <FDRIVE> 282 0 64984
2009/11/17 20:28:39.33: 9 2: NdpEAQuery in <\GDRIVE> 000e0000 41
2009/11/17 20:28:39.33: 4 2: EALIst for <\GDRIVE>
2009/11/17 20:28:39.33: 4 2: ea_get_file list failed - ERRSRV -
ERRinvdevice (Invalid device - printer request made to non-printer
connection or non-printer request made to printer connection.)
2009/11/17 20:28:39.33: 9 2: NdpEAQuery <GDRIVE> 282 0 64897
2009/11/17 20:28:39.33: 9 2: NdpEAQuery in <\HDRIVE> 000e0000 41
2009/11/17 20:28:39.33: 4 2: EALIst for <\HDRIVE>
2009/11/17 20:28:39.33: 4 2: ea_get_file list failed - ERRSRV -
ERRinvdevice (Invalid device - printer request made to non-printer
connection or non-printer request made to printer connection.)


What printer request is the above relating to? - and could it have any
bearing on evfsgui being unable to browse my network?


Regards

Pete
Pete Brown
2009-11-18 01:22:59 UTC
Permalink
Hi Herwig

Not sure if the log below generated using

[L:\samba]smbtree -b --debuglevel=5 -N > cockup.txt

reveals anything of importance.

Regards

Pete



INFO: Current debug levels:
all: True/5
tdb: False/0
printdrivers: False/0
lanman: False/0
smb: False/0
rpc_parse: False/0
rpc_srv: False/0
rpc_cli: False/0
passdb: False/0
sam: False/0
auth: False/0
winbind: False/0
vfs: False/0
idmap: False/0
quota: False/0
acls: False/0
locking: False/0
msdfs: False/0
dmapi: False/0
lp_load: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file
"L:\MPTN\ETC/samba/smb.conf"
Processing section "[global]"
doing parameter workgroup = THEBROWNS
doing parameter log level = 1
pm_process() returned Yes
Attempting to register new charset UCS-2LE
Registered charset UCS-2LE
Attempting to register new charset UTF-16LE
Registered charset UTF-16LE
Attempting to register new charset UCS-2BE
Registered charset UCS-2BE
Attempting to register new charset UTF-16BE
Registered charset UTF-16BE
Attempting to register new charset UTF8
Registered charset UTF8
Attempting to register new charset UTF-8
Registered charset UTF-8
Attempting to register new charset ASCII
Registered charset ASCII
Attempting to register new charset 646
Registered charset 646
Attempting to register new charset ISO-8859-1
Registered charset ISO-8859-1
Attempting to register new charset UCS2-HEX
Registered charset UCS2-HEX
Attempting to register new charset CP850
Registered charset CP850
Attempting to register new charset CP437
Registered charset CP437
Anzahl interfaces 3 added interface ip=192.168.1.110 bcast=192.168.1.255
nmask=255.255.255.0
name_resolve_bcast: Attempting broadcast lookup for name
__MSBROWSE__<0x1>
socket option SO_KEEPALIVE = 0
socket option SO_REUSEADDR = 4
socket option SO_BROADCAST = 32
Could not test socket option TCP_NODELAY.
socket option IPTOS_LOWDELAY = 0
socket option IPTOS_THROUGHPUT = 0
Could not test socket option SO_REUSEPORT.
socket option SO_SNDBUF = 9216
socket option SO_RCVBUF = 41600
socket option SO_SNDLOWAT = 4096
socket option SO_RCVLOWAT = 1
socket option SO_SNDTIMEO = 0
socket option SO_RCVTIMEO = 0
Sending a packet of len 50 to (192.168.1.255) on port 137
tdb(unnamed): tdb_open_ex pid 163 global handle -2147417841
tdb(unnamed): tdb_open_ex pid 163 active handle -2147417840
tdb(unnamed): tdb_open_ex pid 163 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex pid 163 global handle -2147417841
tdb(unnamed): tdb_open_ex pid 163 active handle -2147417840
tdb(unnamed): tdb_open_ex pid 163 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex pid 163 global handle -2147417841
tdb(unnamed): tdb_open_ex pid 163 active handle -2147417840
tdb(unnamed): tdb_open_ex pid 163 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
Sending a packet of len 50 to (192.168.1.255) on port 137
tdb(unnamed): tdb_open_ex pid 163 global handle -2147417841
tdb(unnamed): tdb_open_ex pid 163 active handle -2147417840
tdb(unnamed): tdb_open_ex pid 163 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex pid 163 global handle -2147417841
tdb(unnamed): tdb_open_ex pid 163 active handle -2147417840
tdb(unnamed): tdb_open_ex pid 163 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex pid 163 global handle -2147417841
tdb(unnamed): tdb_open_ex pid 163 active handle -2147417840
tdb(unnamed): tdb_open_ex pid 163 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
Sending a packet of len 50 to (192.168.1.255) on port 137
tdb(unnamed): tdb_open_ex pid 163 global handle -2147417841
tdb(unnamed): tdb_open_ex pid 163 active handle -2147417840
tdb(unnamed): tdb_open_ex pid 163 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex pid 163 global handle -2147417841
tdb(unnamed): tdb_open_ex pid 163 active handle -2147417840
tdb(unnamed): tdb_open_ex pid 163 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex pid 163 global handle -2147417841
tdb(unnamed): tdb_open_ex pid 163 active handle -2147417840
tdb(unnamed): tdb_open_ex pid 163 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
Unable to find master browser by broadcast
Herwig Bauernfeind
2009-11-18 07:27:43 UTC
Permalink
Post by Pete Brown
Not sure if the log below generated using
Yes - that was the next thing I was going to ask you.
Post by Pete Brown
[L:\samba]smbtree -b --debuglevel=5 -N > cockup.txt
reveals anything of importance.
Processing section "[global]"
doing parameter workgroup = THEBROWNS
doing parameter log level = 1
Ok, these are good. I have to think about a good solution to provide a
more appropriate solution for the workgroup value - however this is not
that easy as it may seem, because if there is more than one workgroup,
how to determine which one to enter into smb.conf.... we'll see, have to
think about that.
Post by Pete Brown
Sending a packet of len 50 to (192.168.1.255) on port 137
tdb(unnamed): tdb_open_ex pid 163 global handle -2147417841
tdb(unnamed): tdb_open_ex pid 163 active handle -2147417840
tdb(unnamed): tdb_open_ex pid 163 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
Ok, the client obviously needs a bit more of the server infrastructure -
next evfsgui testbuild creates this directory also. This will make these
messages go away.
Post by Pete Brown
Unable to find master browser by broadcast
And this is the reason why your network neighbourhood stays empty.
We'll see, if this will go away, if we create a \lock directory, but I
doubt it will.

A new one: http://msplins06.bon.at/%7Eadmin139/files/evfsgui-test.zip

Please redo smbtree test and provide log again, thx in advance.

Kind regards,
Herwig
Pete Brown
2009-11-18 16:42:27 UTC
Permalink
Hi Herwig
Post by Herwig Bauernfeind
Post by Pete Brown
Not sure if the log below generated using
Yes - that was the next thing I was going to ask you.
Post by Pete Brown
[L:\samba]smbtree -b --debuglevel=5 -N > cockup.txt
reveals anything of importance.
Processing section "[global]"
doing parameter workgroup = THEBROWNS
doing parameter log level = 1
Ok, these are good. I have to think about a good solution to provide a
more appropriate solution for the workgroup value - however this is not
that easy as it may seem, because if there is more than one workgroup,
how to determine which one to enter into smb.conf.... we'll see, have to
think about that.
Post by Pete Brown
Sending a packet of len 50 to (192.168.1.255) on port 137
tdb(unnamed): tdb_open_ex pid 163 global handle -2147417841
tdb(unnamed): tdb_open_ex pid 163 active handle -2147417840
tdb(unnamed): tdb_open_ex pid 163 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
Ok, the client obviously needs a bit more of the server infrastructure -
next evfsgui testbuild creates this directory also. This will make these
messages go away.
Post by Pete Brown
Unable to find master browser by broadcast
And this is the reason why your network neighbourhood stays empty.
We'll see, if this will go away, if we create a \lock directory, but I
doubt it will.
Sorry but it does not.

The missing bit is unexpected.tdb - the directory
L:\MPTN\ETC/samba/lock/ already existed.
Post by Herwig Bauernfeind
A new one: http://msplins06.bon.at/%7Eadmin139/files/evfsgui-test.zip
No change in the object created in Startup folder - there is no Path and
file name entry.
Post by Herwig Bauernfeind
Please redo smbtree test and provide log again, thx in advance.
Kind regards,
Herwig
smbtree log generated using this command
[L:\samba]smbtree -b --debuglevel=5 -N > cockup_01.txt


INFO: Current debug levels:
all: True/5
tdb: False/0
printdrivers: False/0
lanman: False/0
smb: False/0
rpc_parse: False/0
rpc_srv: False/0
rpc_cli: False/0
passdb: False/0
sam: False/0
auth: False/0
winbind: False/0
vfs: False/0
idmap: False/0
quota: False/0
acls: False/0
locking: False/0
msdfs: False/0
dmapi: False/0
lp_load: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file
"L:\MPTN\ETC/samba/smb.conf"
Processing section "[global]"
doing parameter workgroup = THEBROWNS
doing parameter log level = 1
pm_process() returned Yes
Attempting to register new charset UCS-2LE
Registered charset UCS-2LE
Attempting to register new charset UTF-16LE
Registered charset UTF-16LE
Attempting to register new charset UCS-2BE
Registered charset UCS-2BE
Attempting to register new charset UTF-16BE
Registered charset UTF-16BE
Attempting to register new charset UTF8
Registered charset UTF8
Attempting to register new charset UTF-8
Registered charset UTF-8
Attempting to register new charset ASCII
Registered charset ASCII
Attempting to register new charset 646
Registered charset 646
Attempting to register new charset ISO-8859-1
Registered charset ISO-8859-1
Attempting to register new charset UCS2-HEX
Registered charset UCS2-HEX
Attempting to register new charset CP850
Registered charset CP850
Attempting to register new charset CP437
Registered charset CP437
Anzahl interfaces 3 added interface ip=192.168.1.110 bcast=192.168.1.255
nmask=255.255.255.0
name_resolve_bcast: Attempting broadcast lookup for name
__MSBROWSE__<0x1>
socket option SO_KEEPALIVE = 0
socket option SO_REUSEADDR = 4
socket option SO_BROADCAST = 32
Could not test socket option TCP_NODELAY.
socket option IPTOS_LOWDELAY = 0
socket option IPTOS_THROUGHPUT = 0
Could not test socket option SO_REUSEPORT.
socket option SO_SNDBUF = 9216
socket option SO_RCVBUF = 41600
socket option SO_SNDLOWAT = 4096
socket option SO_RCVLOWAT = 1
socket option SO_SNDTIMEO = 0
socket option SO_RCVTIMEO = 0
Sending a packet of len 50 to (192.168.1.255) on port 137
tdb(unnamed): tdb_open_ex pid 124 global handle -2147417847
tdb(unnamed): tdb_open_ex pid 124 active handle -2147417845
tdb(unnamed): tdb_open_ex pid 124 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex pid 124 global handle -2147417847
tdb(unnamed): tdb_open_ex pid 124 active handle -2147417845
tdb(unnamed): tdb_open_ex pid 124 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex pid 124 global handle -2147417847
tdb(unnamed): tdb_open_ex pid 124 active handle -2147417845
tdb(unnamed): tdb_open_ex pid 124 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
Sending a packet of len 50 to (192.168.1.255) on port 137
tdb(unnamed): tdb_open_ex pid 124 global handle -2147417847
tdb(unnamed): tdb_open_ex pid 124 active handle -2147417845
tdb(unnamed): tdb_open_ex pid 124 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex pid 124 global handle -2147417847
tdb(unnamed): tdb_open_ex pid 124 active handle -2147417845
tdb(unnamed): tdb_open_ex pid 124 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex pid 124 global handle -2147417847
tdb(unnamed): tdb_open_ex pid 124 active handle -2147417845
tdb(unnamed): tdb_open_ex pid 124 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
Sending a packet of len 50 to (192.168.1.255) on port 137
tdb(unnamed): tdb_open_ex pid 124 global handle -2147417847
tdb(unnamed): tdb_open_ex pid 124 active handle -2147417845
tdb(unnamed): tdb_open_ex pid 124 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex pid 124 global handle -2147417847
tdb(unnamed): tdb_open_ex pid 124 active handle -2147417845
tdb(unnamed): tdb_open_ex pid 124 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
tdb(unnamed): tdb_open_ex pid 124 global handle -2147417847
tdb(unnamed): tdb_open_ex pid 124 active handle -2147417845
tdb(unnamed): tdb_open_ex pid 124 transaction handle -2147417839
tdb(unnamed): tdb_open_ex: could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory
Unable to find master browser by broadcast



My possibly silly question is what "master browser" is this looking for?


Regards

Pete
Herwig Bauernfeind
2009-11-19 16:13:19 UTC
Permalink
Hi Pete,
Post by Pete Brown
Sorry but it does not.
The missing bit is unexpected.tdb - the directory
L:\MPTN\ETC/samba/lock/ already existed.
Ok, I see, try to add unexpected.tdb from
http://msplins06.bon.at/%7Eadmin139/files/unexpected.zip
This is a "fresh" one created by a 3.0.36 server...

Let's see if this helps...
Post by Pete Brown
A new one: http://msplins06.bon.at/%7Eadmin139/files/evfsgui-test.zip
No change in the object created in Startup folder - there is no Path
and file name entry.
This is really strange, as this works normally here (and I can't see why
it shouldn't somewhere else). I will add some debug messages to find out
what is going on in your place.
Post by Pete Brown
Unable to find master browser by broadcast
My possibly silly question is what "master browser" is this looking for?
The master browser is the computer in your LAN which is responsible for
maintaining the so called browse list (i.e. the content of network
neighbourhood). It seems like none of your computers feels responsible
for that...

http://www.comptechdoc.org/os/windows/ntwsguide/ntwsnfinding.html

Despite there is a lot of Windows specific stuff, all the rest also
applies to "us".

Regards,
Herwig
Pete Brown
2009-11-19 17:46:23 UTC
Permalink
Hi Herwig
Post by Herwig Bauernfeind
Hi Pete,
Post by Pete Brown
Sorry but it does not.
The missing bit is unexpected.tdb - the directory
L:\MPTN\ETC/samba/lock/ already existed.
Ok, I see, try to add unexpected.tdb from
http://msplins06.bon.at/%7Eadmin139/files/unexpected.zip
This is a "fresh" one created by a 3.0.36 server...
Let's see if this helps...
It removes the errors "could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory" - log
below.
Post by Herwig Bauernfeind
Post by Pete Brown
A new one: http://msplins06.bon.at/%7Eadmin139/files/evfsgui-test.zip
No change in the object created in Startup folder - there is no Path
and file name entry.
This is really strange, as this works normally here (and I can't see why
it shouldn't somewhere else). I will add some debug messages to find out
what is going on in your place.
Could it be that you already have a Startup object and the Autostart is
simply *updating* that rather than creating a new object?
Post by Herwig Bauernfeind
Post by Pete Brown
Unable to find master browser by broadcast
My possibly silly question is what "master browser" is this looking for?
The master browser is the computer in your LAN which is responsible for
maintaining the so called browse list (i.e. the content of network
neighbourhood). It seems like none of your computers feels responsible
for that...
http://www.comptechdoc.org/os/windows/ntwsguide/ntwsnfinding.html
Despite there is a lot of Windows specific stuff, all the rest also
applies to "us".
I thought that was what the "master browser" bit was about.

I did a network course in 2001 - CompTIA Network+ - that was so Windows
based that the course barely acknowledged the possibility of connecting
to non-Windows networks.

Mention was made of the master browser being "elected" from within the
network and, if I remember correctly, this is done automatically as part
of windows networking.

I never even thought about a master browser on OS/2 networks; I simply
presumed there is not such a beast.

It looks like LAN Server has a setting maintainserverlist with a default
of Yes. Searching File and Print Help does not find any mention of
master browser or how to set it.

Network Administrator Tasks mentions:-

Network Neighborhood Browser Enabler Allows OS/2 Warp Server to function
as a master browser for Windows Clients. The master browser function
provides Windows 95 and Windows NT clients the ability to view the
domain's LAN Server machines and their resources via the Network
Neighborhood object.

Yet again only on a Server version of OS/2.

Maybe I am missing something, somewhere?

Regards

Pete
Post by Herwig Bauernfeind
Regards,
Herwig
Log generated using
[L:\samba]smbtree -b --debuglevel=5 -N > cockup_03.txt

INFO: Current debug levels:
all: True/5
tdb: False/0
printdrivers: False/0
lanman: False/0
smb: False/0
rpc_parse: False/0
rpc_srv: False/0
rpc_cli: False/0
passdb: False/0
sam: False/0
auth: False/0
winbind: False/0
vfs: False/0
idmap: False/0
quota: False/0
acls: False/0
locking: False/0
msdfs: False/0
dmapi: False/0
lp_load: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file
"L:\MPTN\ETC/samba/smb.conf"
Processing section "[global]"
doing parameter workgroup = THEBROWNS
doing parameter log level = 1
pm_process() returned Yes
Attempting to register new charset UCS-2LE
Registered charset UCS-2LE
Attempting to register new charset UTF-16LE
Registered charset UTF-16LE
Attempting to register new charset UCS-2BE
Registered charset UCS-2BE
Attempting to register new charset UTF-16BE
Registered charset UTF-16BE
Attempting to register new charset UTF8
Registered charset UTF8
Attempting to register new charset UTF-8
Registered charset UTF-8
Attempting to register new charset ASCII
Registered charset ASCII
Attempting to register new charset 646
Registered charset 646
Attempting to register new charset ISO-8859-1
Registered charset ISO-8859-1
Attempting to register new charset UCS2-HEX
Registered charset UCS2-HEX
Attempting to register new charset CP850
Registered charset CP850
Attempting to register new charset CP437
Registered charset CP437
Anzahl interfaces 3 added interface ip=192.168.1.110 bcast=192.168.1.255
nmask=255.255.255.0
name_resolve_bcast: Attempting broadcast lookup for name
__MSBROWSE__<0x1>
socket option SO_KEEPALIVE = 0
socket option SO_REUSEADDR = 4
socket option SO_BROADCAST = 32
Could not test socket option TCP_NODELAY.
socket option IPTOS_LOWDELAY = 0
socket option IPTOS_THROUGHPUT = 0
Could not test socket option SO_REUSEPORT.
socket option SO_SNDBUF = 9216
socket option SO_RCVBUF = 41600
socket option SO_SNDLOWAT = 4096
socket option SO_RCVLOWAT = 1
socket option SO_SNDTIMEO = 0
socket option SO_RCVTIMEO = 0
Sending a packet of len 50 to (192.168.1.255) on port 137
tdb(unnamed): tdb_open_ex pid 97 global handle -2147417851
tdb(unnamed): tdb_open_ex pid 97 active handle -2147417850
tdb(unnamed): tdb_open_ex pid 97 transaction handle -2147417849
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLKW, rw_type
F_WRLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 0, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLK, rw_type
F_UNLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(unnamed): tdb_open_ex pid 97 global handle -2147417851
tdb(unnamed): tdb_open_ex pid 97 active handle -2147417850
tdb(unnamed): tdb_open_ex pid 97 transaction handle -2147417849
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLKW, rw_type
F_WRLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 0, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLK, rw_type
F_UNLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(unnamed): tdb_open_ex pid 97 global handle -2147417851
tdb(unnamed): tdb_open_ex pid 97 active handle -2147417850
tdb(unnamed): tdb_open_ex pid 97 transaction handle -2147417849
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLKW, rw_type
F_WRLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 0, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLK, rw_type
F_UNLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
Sending a packet of len 50 to (192.168.1.255) on port 137
tdb(unnamed): tdb_open_ex pid 97 global handle -2147417851
tdb(unnamed): tdb_open_ex pid 97 active handle -2147417850
tdb(unnamed): tdb_open_ex pid 97 transaction handle -2147417849
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLKW, rw_type
F_WRLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 0, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLK, rw_type
F_UNLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(unnamed): tdb_open_ex pid 97 global handle -2147417851
tdb(unnamed): tdb_open_ex pid 97 active handle -2147417850
tdb(unnamed): tdb_open_ex pid 97 transaction handle -2147417849
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLKW, rw_type
F_WRLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 0, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLK, rw_type
F_UNLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(unnamed): tdb_open_ex pid 97 global handle -2147417851
tdb(unnamed): tdb_open_ex pid 97 active handle -2147417850
tdb(unnamed): tdb_open_ex pid 97 transaction handle -2147417849
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLKW, rw_type
F_WRLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 0, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLK, rw_type
F_UNLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
Sending a packet of len 50 to (192.168.1.255) on port 137
tdb(unnamed): tdb_open_ex pid 97 global handle -2147417851
tdb(unnamed): tdb_open_ex pid 97 active handle -2147417850
tdb(unnamed): tdb_open_ex pid 97 transaction handle -2147417849
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLKW, rw_type
F_WRLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 0, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLK, rw_type
F_UNLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(unnamed): tdb_open_ex pid 97 global handle -2147417851
tdb(unnamed): tdb_open_ex pid 97 active handle -2147417850
tdb(unnamed): tdb_open_ex pid 97 transaction handle -2147417849
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLKW, rw_type
F_WRLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 0, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLK, rw_type
F_UNLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(unnamed): tdb_open_ex pid 97 global handle -2147417851
tdb(unnamed): tdb_open_ex pid 97 active handle -2147417850
tdb(unnamed): tdb_open_ex pid 97 transaction handle -2147417849
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLKW, rw_type
F_WRLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 0, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417851, offset 0
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1424, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2588, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1668, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1208, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 696, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2344, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2804, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 1884, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_RDLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 2128, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): tdb_brlock pid 61, fd 3,
lck_type F_SETLKW, rw_type F_UNLCK, offset 8, len 1
tdb(L:\MPTN\ETC/samba/lock/unexpected.tdb): _mutex_brlock handle
-2147417849, offset 8
tdb(unnamed): tdb_brlock pid 61, fd 3, lck_type F_SETLK, rw_type
F_UNLCK, offset 0, len 1
tdb(unnamed): _mutex_brlock handle -2147417851, offset 0
Unable to find master browser by broadcast
Pete Brown
2009-11-19 23:43:57 UTC
Permalink
Hi Herwig
Post by Pete Brown
Hi Herwig
Post by Herwig Bauernfeind
Hi Pete,
Post by Pete Brown
Sorry but it does not.
The missing bit is unexpected.tdb - the directory
L:\MPTN\ETC/samba/lock/ already existed.
Ok, I see, try to add unexpected.tdb from
http://msplins06.bon.at/%7Eadmin139/files/unexpected.zip
This is a "fresh" one created by a 3.0.36 server...
Let's see if this helps...
It removes the errors "could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory" - log
below.
Post by Herwig Bauernfeind
Post by Pete Brown
A new one: http://msplins06.bon.at/%7Eadmin139/files/evfsgui-test.zip
No change in the object created in Startup folder - there is no Path
and file name entry.
This is really strange, as this works normally here (and I can't see why
it shouldn't somewhere else). I will add some debug messages to find out
what is going on in your place.
Could it be that you already have a Startup object and the Autostart is
simply *updating* that rather than creating a new object?
Well, I put a copy of a working startup object into the startup folder
and then used evfsgui Autostart to create a startup object.

The new object does not have Path and file name.

How it works for you and not for me I do not know...
Post by Pete Brown
Post by Herwig Bauernfeind
Post by Pete Brown
Unable to find master browser by broadcast
My possibly silly question is what "master browser" is this looking for?
The master browser is the computer in your LAN which is responsible for
maintaining the so called browse list (i.e. the content of network
neighbourhood). It seems like none of your computers feels responsible
for that...
http://www.comptechdoc.org/os/windows/ntwsguide/ntwsnfinding.html
Despite there is a lot of Windows specific stuff, all the rest also
applies to "us".
I thought that was what the "master browser" bit was about.
I did a network course in 2001 - CompTIA Network+ - that was so Windows
based that the course barely acknowledged the possibility of connecting
to non-Windows networks.
Mention was made of the master browser being "elected" from within the
network and, if I remember correctly, this is done automatically as part
of windows networking.
I never even thought about a master browser on OS/2 networks; I simply
presumed there is not such a beast.
It looks like LAN Server has a setting maintainserverlist with a default
of Yes. Searching File and Print Help does not find any mention of
master browser or how to set it.
Network Administrator Tasks mentions:-
Network Neighborhood Browser Enabler Allows OS/2 Warp Server to function
as a master browser for Windows Clients. The master browser function
provides Windows 95 and Windows NT clients the ability to view the
domain's LAN Server machines and their resources via the Network
Neighborhood object.
Yet again only on a Server version of OS/2.
Maybe I am missing something, somewhere?
Regards
Pete
I had a look at the samba man pages -
http://us1.samba.org/samba/docs/man/manpages-3/smb.conf.5.html - and
found master browser is set in smb.conf - but the setting is used by
nmbd. Whatever that is? - there is no nmbd.* file installed here.

Regards

Pete
Alex Taylor
2009-11-21 03:04:56 UTC
Permalink
On Thu, 19 Nov 2009 17:46:23 UTC, Pete Brown
Post by Pete Brown
Mention was made of the master browser being "elected" from within the
network and, if I remember correctly, this is done automatically as part
of windows networking.
I never even thought about a master browser on OS/2 networks; I simply
presumed there is not such a beast.
It looks like LAN Server has a setting maintainserverlist with a default
of Yes. Searching File and Print Help does not find any mention of
master browser or how to set it.
Network Administrator Tasks mentions:-
Network Neighborhood Browser Enabler Allows OS/2 Warp Server to function
as a master browser for Windows Clients. The master browser function
provides Windows 95 and Windows NT clients the ability to view the
domain's LAN Server machines and their resources via the Network
Neighborhood object.
Yet again only on a Server version of OS/2.
You are correct.

Normally, OS/2 (Peer and Server) does not use a master browser system.
I don't recall what it DOES use offhand, but I think it just relies on
sending out "I'm here" broadcasts when some other system calls out
"Hey, who's out there?".)

However, a master browser facility was introduced as an addon to LAN
Server 5.0 (used in Warp Server 4). It was available for download from
IBM's FTP sites, and worked as a service called BROWSER.

I believe it's included out of the box in LAN Server 5.20 (a.k.a. WSeB).

However, it only applies to LAN Server. I'm pretty sure Peer systems
still have to rely on the old broadcast method.
--
Alex Taylor
Fukushima, Japan
http://www.socis.ca/~ataylo00

Please take off hat when replying.
Herwig Bauernfeind
2009-11-22 18:24:58 UTC
Permalink
Post by Pete Brown
Hi Herwig
Post by Pete Brown
Hi Herwig
Post by Herwig Bauernfeind
Hi Pete,
Post by Pete Brown
Sorry but it does not.
The missing bit is unexpected.tdb - the directory
L:\MPTN\ETC/samba/lock/ already existed.
Ok, I see, try to add unexpected.tdb from
http://msplins06.bon.at/%7Eadmin139/files/unexpected.zip
This is a "fresh" one created by a 3.0.36 server...
Let's see if this helps...
It removes the errors "could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory" - log
below.
Post by Herwig Bauernfeind
Post by Pete Brown
A new one: http://msplins06.bon.at/%7Eadmin139/files/evfsgui-test.zip
No change in the object created in Startup folder - there is no Path
and file name entry.
This is really strange, as this works normally here (and I can't see why
it shouldn't somewhere else). I will add some debug messages to find out
what is going on in your place.
Could it be that you already have a Startup object and the Autostart is
simply *updating* that rather than creating a new object?
Well, I put a copy of a working startup object into the startup folder
and then used evfsgui Autostart to create a startup object.
The new object does not have Path and file name.
How it works for you and not for me I do not know...
Post by Pete Brown
Post by Herwig Bauernfeind
Post by Pete Brown
Unable to find master browser by broadcast
My possibly silly question is what "master browser" is this looking for?
The master browser is the computer in your LAN which is responsible for
maintaining the so called browse list (i.e. the content of network
neighbourhood). It seems like none of your computers feels responsible
for that...
http://www.comptechdoc.org/os/windows/ntwsguide/ntwsnfinding.html
Despite there is a lot of Windows specific stuff, all the rest also
applies to "us".
I thought that was what the "master browser" bit was about.
I did a network course in 2001 - CompTIA Network+ - that was so Windows
based that the course barely acknowledged the possibility of connecting
to non-Windows networks.
Mention was made of the master browser being "elected" from within the
network and, if I remember correctly, this is done automatically as part
of windows networking.
I never even thought about a master browser on OS/2 networks; I simply
presumed there is not such a beast.
It looks like LAN Server has a setting maintainserverlist with a default
of Yes. Searching File and Print Help does not find any mention of
master browser or how to set it.
Network Administrator Tasks mentions:-
Network Neighborhood Browser Enabler Allows OS/2 Warp Server to function
as a master browser for Windows Clients. The master browser function
provides Windows 95 and Windows NT clients the ability to view the
domain's LAN Server machines and their resources via the Network
Neighborhood object.
Yet again only on a Server version of OS/2.
Maybe I am missing something, somewhere?
Not sure at this point.
As Alex indicated there was/is the browser service addon for LAN-Server.
I wonder if this also would work with Peer, never tried that, though.
Post by Pete Brown
I had a look at the samba man pages -
http://us1.samba.org/samba/docs/man/manpages-3/smb.conf.5.html - and
found master browser is set in smb.conf - but the setting is used by
nmbd. Whatever that is? - there is no nmbd.* file installed here.
nmbd.exe is the Samba Server process which is responsible for name
resolution and browsing. There is no nmbd.exe on the client. Running an
nmbd.exe on one of your machines might resolve the problem, but that
would not be the next thing to do.

Pete, does your Network Neighbourhoud fill if you add a single Windows
machine to your LAN? NT4, 2K or XP would be sufficient.

Kind regards,
Herwig
Pete Brown
2009-11-23 00:25:08 UTC
Permalink
Hi Herwig
Post by Herwig Bauernfeind
Post by Pete Brown
Hi Herwig
Post by Pete Brown
Hi Herwig
Post by Herwig Bauernfeind
Hi Pete,
Post by Pete Brown
Sorry but it does not.
The missing bit is unexpected.tdb - the directory
L:\MPTN\ETC/samba/lock/ already existed.
Ok, I see, try to add unexpected.tdb from
http://msplins06.bon.at/%7Eadmin139/files/unexpected.zip
This is a "fresh" one created by a 3.0.36 server...
Let's see if this helps...
It removes the errors "could not open file
L:\MPTN\ETC/samba/lock/unexpected.tdb: No such file or directory" - log
below.
Post by Herwig Bauernfeind
Post by Pete Brown
A new one: http://msplins06.bon.at/%7Eadmin139/files/evfsgui-test.zip
No change in the object created in Startup folder - there is no Path
and file name entry.
This is really strange, as this works normally here (and I can't see why
it shouldn't somewhere else). I will add some debug messages to find out
what is going on in your place.
Could it be that you already have a Startup object and the Autostart is
simply *updating* that rather than creating a new object?
Well, I put a copy of a working startup object into the startup folder
and then used evfsgui Autostart to create a startup object.
The new object does not have Path and file name.
How it works for you and not for me I do not know...
Post by Pete Brown
Post by Herwig Bauernfeind
Post by Pete Brown
Unable to find master browser by broadcast
My possibly silly question is what "master browser" is this looking for?
The master browser is the computer in your LAN which is responsible for
maintaining the so called browse list (i.e. the content of network
neighbourhood). It seems like none of your computers feels responsible
for that...
http://www.comptechdoc.org/os/windows/ntwsguide/ntwsnfinding.html
Despite there is a lot of Windows specific stuff, all the rest also
applies to "us".
I thought that was what the "master browser" bit was about.
I did a network course in 2001 - CompTIA Network+ - that was so Windows
based that the course barely acknowledged the possibility of connecting
to non-Windows networks.
Mention was made of the master browser being "elected" from within the
network and, if I remember correctly, this is done automatically as part
of windows networking.
I never even thought about a master browser on OS/2 networks; I simply
presumed there is not such a beast.
It looks like LAN Server has a setting maintainserverlist with a default
of Yes. Searching File and Print Help does not find any mention of
master browser or how to set it.
Network Administrator Tasks mentions:-
Network Neighborhood Browser Enabler Allows OS/2 Warp Server to function
as a master browser for Windows Clients. The master browser function
provides Windows 95 and Windows NT clients the ability to view the
domain's LAN Server machines and their resources via the Network
Neighborhood object.
Yet again only on a Server version of OS/2.
Maybe I am missing something, somewhere?
Not sure at this point.
As Alex indicated there was/is the browser service addon for LAN-Server.
I wonder if this also would work with Peer, never tried that, though.
Post by Pete Brown
I had a look at the samba man pages -
http://us1.samba.org/samba/docs/man/manpages-3/smb.conf.5.html - and
found master browser is set in smb.conf - but the setting is used by
nmbd. Whatever that is? - there is no nmbd.* file installed here.
nmbd.exe is the Samba Server process which is responsible for name
resolution and browsing. There is no nmbd.exe on the client. Running an
nmbd.exe on one of your machines might resolve the problem, but that
would not be the next thing to do.
Pete, does your Network Neighbourhoud fill if you add a single Windows
machine to your LAN? NT4, 2K or XP would be sufficient.
Kind regards,
Herwig
I started w2k in VPC/2 and when that had booted I started EVFSgui.

Network Neighbourhood was populated with the Workgroup name and all
systems currently booted were hanging off that.

Looks like we need to either make OS/2 peer systems have a "master
browser election" or somehow get rid of that need in samba in order to
get evfsgui interacting a bit better with OS/2 peer.

Of course, with the whole network converted to samba the above problem
would not apply - would it?

A minor problem comes in at this point: I need to be certain samba
server and evfsgui will work very well and I also need to be more
conversant with samba and evfs before I can implement it as the standard
"peer" network here. This is a home network but I find my family are
more demanding of my technical skills - such as they are - than any
office users ;-)


Regards

Pete

Alex Taylor
2009-11-21 03:05:47 UTC
Permalink
On Wed, 18 Nov 2009 07:27:43 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Pete Brown
[L:\samba]smbtree -b --debuglevel=5 -N > cockup.txt
Unable to find master browser by broadcast
And this is the reason why your network neighbourhood stays empty.
We'll see, if this will go away, if we create a \lock directory, but I
doubt it will.
Isn't the whole point of the '-b' option to NOT require a master browser?
--
Alex Taylor
Fukushima, Japan
http://www.socis.ca/~ataylo00

Please take off hat when replying.
Herwig Bauernfeind
2009-11-22 18:18:05 UTC
Permalink
Post by Alex Taylor
On Wed, 18 Nov 2009 07:27:43 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Pete Brown
[L:\samba]smbtree -b --debuglevel=5 -N > cockup.txt
Unable to find master browser by broadcast
And this is the reason why your network neighbourhood stays empty.
We'll see, if this will go away, if we create a \lock directory, but I
doubt it will.
Isn't the whole point of the '-b' option to NOT require a master browser?
That's what I thought too, however looking at the smbtree sources
reveals that with the -b option broadcasts are used to get to know who
the master browser is.
In Pete's LAN there is none....

Regards,
Herwig
Herwig Bauernfeind
2009-11-18 07:57:35 UTC
Permalink
Hi Pete,
Post by Pete Brown
Umm...
[L:\MPTN\ETC\samba]smbtree -N
[L:\MPTN\ETC\samba]
That does not look very promising.
Indeed.
Post by Pete Brown
Post by Herwig Bauernfeind
Right. This functionality has not been implemented yet (and probably
wont be in 2.0) . At the moment you only can right clock at a passive
connection to reconnect manually.
Presumably the above means in the evfsgui Connections panel as RMB
Right.
Post by Pete Brown
Having a network that works fine apart from with evfs tends to lead me
to think the problem is within evfs though.
It is probably more difficult than that. I am quite sure at this point
that it is not an EVFS problem (and it definitely is not an EVFSGUI
problem). From your other msg I already have an idea, but I need to do
some reading.

The problem might be that IBM Peers protocols are ancient versions of
SMB - Samba client stuff might not be able to cope with these if not
specially configured for these. We might need to add several options to
smb.conf to get that to work (that's guesswork at this point), but as I
said I need to do some reading to figure that out.
Post by Pete Brown
As networking is not otherwise a problem I do not have a
"troubleshooting" start point to try to find the cause.
I hope I will be able to provide that :-)
Post by Pete Brown
Yes, that creates a program object in the Startup folder.
Sadly the object is of no use as the Path and file name are missing.
That definitely works normally here. Eventually rebooted before the
object was properly written back to the INI files....
Post by Pete Brown
When testing this I noticed that using File, Autostart is a bit of a
"no brainer".
Yes, that's right - this is a more or less a One-Trick-Pony (at the
moment). I have plenty of ideas of cool features I'd like to implement,
a better autostart is definitely on my list, but not for 2.0.
Post by Pete Brown
This is because this method of creating an object in the Startup
folder saves the current configuration as \os2\evfsgui.evp - no use at
all in a multi user system. I think that needs to offer to save as
\os2\evfsgui.evp with the option of the user being able to change the
location and file name.
Point taken, sounds reasonable, will add that to my notes.
Post by Pete Brown
I had a look through a newly generated log (\var\log\ndpsmb.log) and
noticed mention of printer requests
[plugin - log removed]
The plugin tries to figure out what's a printer and what's a file share
- nothing wrong with that IMHO, but definitely completely unrelated to
our empty network neighbourhood problem.

Kind regards,
Herwig
Pete Brown
2009-11-18 16:47:06 UTC
Permalink
Hi Herwig
Post by Herwig Bauernfeind
Hi Pete,
Post by Pete Brown
Umm...
[L:\MPTN\ETC\samba]smbtree -N
[L:\MPTN\ETC\samba]
That does not look very promising.
Indeed.
Post by Pete Brown
Post by Herwig Bauernfeind
Right. This functionality has not been implemented yet (and probably
wont be in 2.0) . At the moment you only can right clock at a passive
connection to reconnect manually.
Presumably the above means in the evfsgui Connections panel as RMB
Right.
Post by Pete Brown
Having a network that works fine apart from with evfs tends to lead me
to think the problem is within evfs though.
It is probably more difficult than that. I am quite sure at this point
that it is not an EVFS problem (and it definitely is not an EVFSGUI
problem). From your other msg I already have an idea, but I need to do
some reading.
The problem might be that IBM Peers protocols are ancient versions of
SMB - Samba client stuff might not be able to cope with these if not
specially configured for these. We might need to add several options to
smb.conf to get that to work (that's guesswork at this point), but as I
said I need to do some reading to figure that out.
I think that may be where the incomplete directory and file listing
problem comes from - a certain amount of incompatibility between samba
and peer currently.


Regards

Pete
Post by Herwig Bauernfeind
Post by Pete Brown
As networking is not otherwise a problem I do not have a
"troubleshooting" start point to try to find the cause.
I hope I will be able to provide that :-)
Post by Pete Brown
Yes, that creates a program object in the Startup folder.
Sadly the object is of no use as the Path and file name are missing.
That definitely works normally here. Eventually rebooted before the
object was properly written back to the INI files....
Post by Pete Brown
When testing this I noticed that using File, Autostart is a bit of a
"no brainer".
Yes, that's right - this is a more or less a One-Trick-Pony (at the
moment). I have plenty of ideas of cool features I'd like to implement,
a better autostart is definitely on my list, but not for 2.0.
Post by Pete Brown
This is because this method of creating an object in the Startup
folder saves the current configuration as \os2\evfsgui.evp - no use at
all in a multi user system. I think that needs to offer to save as
\os2\evfsgui.evp with the option of the user being able to change the
location and file name.
Point taken, sounds reasonable, will add that to my notes.
Post by Pete Brown
I had a look through a newly generated log (\var\log\ndpsmb.log) and
noticed mention of printer requests
[plugin - log removed]
The plugin tries to figure out what's a printer and what's a file share
- nothing wrong with that IMHO, but definitely completely unrelated to
our empty network neighbourhood problem.
Kind regards,
Herwig
Herwig Bauernfeind
2009-11-17 18:23:07 UTC
Permalink
Hi Pete,
Post by Pete Brown
I clicked the File, Autostart option and this error was displayed:-
+++ resdata = resdata || VRMethod('CN_CONDET',
'GetFieldData, records.i, CD.mpointFH) || '';
Please try with http://msplins06.bon.at/%7Eadmin139/files/evfsgui-test.zip
I could reproduce your error and it is fixed with this one.

Kind regards,
Herwig
Loading...