Hi Doug and Herwig
Firstly: Thank you both for having the patience to persist with helping
me get samba server up and running.
Secondly: Hope you don't mind me "top posting" this.
Another attempt at getting samba server 1.0.3 running properly.
I had another look at samba server today.
I logged into "Samba users and groups' as guest (no password) to check
the user previously added.
This user has no password set for some strange reason.
I entered the Password, and the Repeat Password and clicked Save.
I was rewarded with the below error message which I have not seen before:-
Line 28 of PB_upSave_Click in smbusers. VRM:
+++ If
length(VRget('EF_password', 'Value'))<
MinPWLength
Clicking OK to the message exits "samba users and groups" - not the best
option here. Surely it would be better to simply close the error message
- in fact, it would probably be better if the error message stated what
the problem is in plain language so that the user knows what they did wrong.
I guess there is a minimum Password length and 7 chars is not long enough?
Checking the %TEMP% location I find it filling up with files called
smb_err.xxx and smb_msg.xxx (where xxx is a sequence of 3 numbers). All
these files are empty and are obviously not needed. Please sort samba
server out to delete these files after creation - there is no point in
having them cluttering up the drive.
To try and get to grips with samba server I totally uninstalled samba
1.0.3 using Warpin and then had a rummage around the drive to remove any
traces missed by Warpin - including the mess of samba related files in
%TEMP%.
NOTE: config.sys configuration is *not* undone as claimed during the
Warpin Uninstall - the SET UNIXROOT line was not removed from the
config.sys file.
Possibly worth noting here: My previous attempts to uninstall/reinstall
this package did not include cleaning the %TEMP% directory. Maybe
something in that directory prevented successful reinstallation of the
package?
I then rebooted and ran the samba 1.0.3 install again and all seemed to
go well - apart from the sharewiz.exe object not being created due to a
dependency on software not installed (xWP). I clicked Ignore to that
message.
Simple Samba Configuration Center then started and I entered a Password
for the root account.
A question: What is the difference between the "backends" smbpasswd and
tdbsam? - I went with the pre-selected tdbsam but would like to know
what the difference is for future installs.
I left the "Server type" as the pre-selected Standalone and clicked
"Migrate IBM Peer/LANServer configuration".
This resulted in some messages that look good:-
Created user root
Created user guest
Created c:\mptn\etc\samba\lmhosts
and finally
Please, close this program in order to complete installation - I clicked
OK, closed the program and Warpin finished.
I then opened the Samba Server desktop folder - this has a url for
"SYS0317: The system cannot find message 0035 in message file
C:\VAR\TEMP\SMBWPI_EN.MSG"
As the file exists I can only guess that message 0035 is not in the file?
I attempted to run Samba users and groups. This asked for a login which
I gave as root with the password entered during the SSCC part of the
install. That worked!
I now suspect the problems I had with this previously were related to
password length - in previous installs SSCC had accepted root passwords
of 7 chars length without any complaint - this time I used a longer
password based on the error message from Samba users and groups
displayed above.
On to "Add User".
A question: what is the option "Machine Account"? - and why does it not
respond to being clicked? When I click on the Unchecked checkbox it
stays Unchecked; surely it should become Checked.
I created a new user and entered a password, saved the details and
exited Samba Users and Groups.
In theory if I now run EVFSgui with the new user name and password I
should be able to connect to the samba shares.
Shame that does not work in practice...
Having started EVFSgui the Network neighbourhood view is populated with
my network. Brilliant! - No need for a Windows system to be running on
the network then.
I dragged the icon of DISKZONE (system with samba server installed) to
the Current Resources panel which popped up the "Mount to" window. I
selected drive U:\DISKZONE and then completed the Login detail as per
the new user on the samba server and clicked OK.
Result: SYS0065: Network access is denied.
I tried again and got a different result: The parameter is incorrect.
OK...
I then tried to mount DISKZONE using Dialog View.
Mount: All shares on server
Server: DISKZONE
Workgroup: THEBROWNS
User ID: as per new user on server
Password: as per new user on server
Mount to: U:\DISKZONE
Result: The parameter is incorrect.
Explanation:-
Mount ***@THEBROWNS\\DISKZONE\ to U:\DISKZONE
The parameter is incorrect.
I hope the above means something to someone?
Here is the chunk of log to go with the attempt to mount DISKZONE using
Dialog View:-
network = NETWORK
16:39:32 Mount procedure started
16:39:32 MyFreeDriveMap(proc) started
16:39:32 MyFreeDriveMap(proc) done, result "M: N: O: P: Q: R: S: T: U:
X: Y: Z: "
16:39:32 ok = EVFSRxAttach( vfs.!drive )
16:39:32 Attach "U:" = 0
16:39:32 CreateMP = EVFSRxCreateMountPoint( vfs.!mountpoint )
16:39:32 Create "U:\DISKZONE" = 0
16:39:32 ParseResourceData started
receiving "U:\DISKZONE" "SMBFS SMBFS64
\\THEBROWNS:DISKZONE\@LOSEPETE;WORKGROUP=THEBROWNS;SERVER=DISKZONE;USER=LOSEPETE;PASSWORD=NRB060260;EASUPPORT=1
W" length (127)
returning "U:\DISKZONE;THEBROWNS:\\DISKZONE\*"
16:39:32 ParseresdataData done
16:39:32 ok = EVFSRxMount('smbfs', vfs.!mountpoint, src, rwFlag)
16:39:32 Mount "U:\DISKZONE" = 87
16:45:27 Mount procedure done
16:45:27 Refresh started
#68:PMWP.DLL
Remove records, disable buttons done.
16:45:27 MyFreeDriveMap(proc) started
16:45:27 MyFreeDriveMap(proc) done, result "M: N: O: P: Q: R: S: T: U:
X: Y: Z: "
16:45:27 GetMountPoints started
16:45:27 GetMountPoints done
16:45:27 Refresh done
16:45:27 PB_MOUNT_Click done
This bit looks right:-
" receiving "U:\DISKZONE" "SMBFS SMBFS64
\\THEBROWNS:DISKZONE\@LOSEPETE;WORKGROUP=THEBROWNS;SERVER=DISKZONE;USER=LOSEPETE;PASSWORD=NRB060260;EASUPPORT=1
W" length (127)"
Look like PMWP.DLL is involved... Is #68:PMWP.DLL where the attempt to
mount DISKZONE goes wrong?
I can access DISKZONE (running samba server) using OS/2 Peer.
Out of interest I just looked in \\DISKZONE\%TEMP% and already have a
growing collection of samba related files:-
17-02-10 3:22p 262 0 a--- group
17-02-10 3:22p 324 0 a--- master.passwd
17-02-10 3:33p 730 0 a--- netgrouplist.txt
17-02-10 3:33p 1,657 0 a--- netgroupmap.txt
28-12-09 6:04p 5,281 0 a--- smbwpi_en.msg
17-02-10 1:48p 0 0 a--- smb_err.585
17-02-10 3:19p 0 0 a--- smb_err.737
17-02-10 1:47p 138 0 a--- smb_msg.110
17-02-10 3:19p 14 0 a--- smb_msg.262
17-02-10 1:20p 388 0 a--- sscc.testparm
17-02-10 3:22p 841 0 a--- UserProperties.txt
Should samba server be writing all these files to %TEMP%?
Anyway, I now seem to have samba server up'n'running on DISKZONE but am
stumped by the failure of EVFSgui to access the shares.
Regards
Pete
Post by Herwig BauernfeindHi Pete,
Post by Pete BrownPost by Herwig BauernfeindPost by Pete BrownPost by Herwig BauernfeindPost by Pete BrownPost by Herwig BauernfeindPost by Pete BrownPost by Herwig BauernfeindPost by Pete BrownPost by Pete BrownPost by Pete BrownOk - I give up.
Having created a root password when I enter that password when
prompted
by Samba users and groups I only get the "Network access
denied"
message.
Obviously something wrong, somewhere...
What am I - or samba - doing wrong?
Well, as I understand the explanation of master.passwd fields here
http://svn.netlabs.org/samba/wiki/MasterPasswdSyntax it looks
like
what
I am doing wrong is supplying a password. The wiki shows this:-
Field : Description : Recommended value when using Samba : Example
"Password : Not used currently : Leave empty or add * as value : *"
Can someone confirm the above is actually the case.
Yes, that is correct.
We are only using Samba passwords, not the klibc Unix emulation password.
Sorry but the explanation means nothing to me...
http://svn.netlabs.org/samba/wiki/Cookbook was extended recently.
Does not seem to be extended in respect of installing from WPI package...
Post by Herwig BauernfeindPost by Pete BrownPost by Herwig BauernfeindPost by Pete BrownPost by Herwig BauernfeindPost by Pete BrownI did get samba server working yesterday by the simple expedient of
not creating a root account. I did setup a user account with a password.
Sigh. You will definitely need "root" and "guest" accounts.
Interesting.
I did have samba server 1.0.3 working fine with OS/2 Peer with no
"root" account.
It did not work with EVFSgui 2.0.3 though and displayed various errors
such as "incorrect parameter" and "access denied". This may be a
problem with EVFSgui 2.0.3 as trying to access samba server resulted
in several os2popup.log entries.
I must admit that I am not very keen on having a "root" account that
is not password protected.
Why on earth should you want the root account not to be password
protected? It definitely should be password protected...
Make your mind up.
Either root has no password or a "*" as password - you confirmed that
in the above:-
Please, Pete, you can savely assume, I know what I am talking about (at
least most of the time).
That could well be the problem - you know what you are talking about
but I'm not getting the gist of it.
Post by Herwig BauernfeindThe information stored in master.passwd IN NOT USED for
authentification in Samba.
Right - that is straight over my head.
Post by Herwig BauernfeindKeep in mind that Samba is a port of a Unix software.
On Unix the system user/passwords are stored in master.passwd. Samba
has to be able to talk to Windows systems, the Unix user/password
infrastructure in not suitable for that purpose - so Samba creates
its own, which is almost (but not completely) independent from the
Unix system user/password infrastructure.
Do I understand the above to mean that master.passwd exists solely for
compatibility with *nix systems and is not actually used by samba?
Yes, almost. Samba only duplicates a few informations found in there
(but not password), that's why it should in sync with the correpsonding
Samba files (located in %etc%\samba\private and not user editable). One
of the (many) jobs smbusers.exe, usermod.cmd and groupmod.cmd do is to
keep those files in sync. Basically there is no need at all to manually
fiddle with master.passwd.
In case you modified master.passwd manually, did you rebuild pwd.db and
spwd.db
In case you did not - run usermod.cmd without any parameter to rebuild them.
Post by Pete BrownPost by Herwig Bauernfeindremember OS/2 is a single user OS.
On OS/2 the klibc Runtime (found in libc063.dll and libc064x.dll)
provides a Unix emulation layer. The information stored in
master.passwd is just there to make programs, such as Samba, which
rely on its presence, to be happy. The user/password infrastructure
that Samba creates, synchronizes several bits of information with
master.passwd (check the usermod.cmd to exactly see what it does and
what it does not). The password is not syncronized and completely
independent. On OS/2 there is no software that ever evaluates the
password stored in master.passwd, that's why none is required. When
Samba Server asks for credentials it checks them against its own
user/password database, found in whatever backend is used by Samba
(smbpasswd, tdbsam).
On OS/2 there is no such thing as a system user/password infrastructure,
When I install samba server from WPI we get to the sscc.exe /install
stage and I am asked to supply a password for root - if I use a root
account.
Yes. Future release will not disallow the creation anymore, because this
only make sense in situation when a root account already exists.
Post by Pete BrownHaving run through the sscc.exe /install stage successfully and
entered a root password I then try to run "Samba Users and Groups".
This asks for a root password.
If I enter the password created during sscc.exe /install "Samba Users
and Groups" fails to run as the password is rejected.
What should I put in when "Samba Users and Groups" asks for root
password? Is this where the password is either nothing or "*"?
No. You should provide the password the provided in sscc.exe /install
Post by Pete BrownPost by Herwig Bauernfeind- The 'root' account, with a secure password, as it may do anything.
The Samba server processes run in this users context. If it is not
present (it is on every single Unix system in the world),
unpredictable things may happen. I know of several, but there is no
list of definitive/likely/possible failures and I have no intention
to create such a list.
I'd recommend to follow Doug recommendation and uninstall Samba using
the unistall feature of Warpin. Upon deinstallationa little program of
mine is called that asks whether every single trace of Samba should be
removed from the system. Choose yes and reboot afterwards.
Then try reinstalling using the WPI.
Regards,
Herwig