• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

Need help with SAMBA

Started by klipp, 2008.01.30, 02:00:11

Previous topic - Next topic

klipp

I've installed SAMBA-3.0.27a-os2-20071126-v1.wpi and everything looks good except that I can't make a connection to the server.
smbclient -L INTERNET gives "Connection to INTERNET failed (error NT_STATUS_BAD_NETWORK_NAME)! whereas giving the same smbclient -L BOSS (a client) works fine.
  I did remove the NETBIOS over TCP/IP protocol as the install instructions said.
  NET VIEW shows all boxes in the workgroup including INTERNET.

Could somebody tell me what I'm missing?  Thanks

klipp
********************************************************************
Windoz Free! eCS 2.0 serving Linux, Windoz & OS2
rklipp@megared.net.mx
********************************************************************

herwigb

Setup a loglevel of 5 and take look into the logfile.
This usually gives you an idea what is going wrong.

Wild guess: Guest account not setup properly, nullpassword = yes not set?

KInd regards,
Herwig
Kind regards,
HerwigB.

klipp

Thank you, herwigb, for you're response. I do have nullpassword set to "yes". Setting the loglevel as you suggested indicates that it was not possible to read the contents of n:/programs/samba/var/locks! Even though the files are installed in that directory.  It looks like the permissions to read that directory aren't correct.
  Testparm.exe backs this up by giving the "WARNING: lock directory N:\programs\Samba/var/locks should have permissions 0755 for browsing to work. I know how to correct this in Linux, but have no idea how to correct this using eCS (btw I'm running eCS 2.0-rc4).
   I can add or delete users using you're excellent utilities but the Samba status monitor shows no users,files or services.
Thank you for you're interest & help

klipp
********************************************************************
Windoz Free! eCS 2.0 serving Linux, Windoz & OS2
rklipp@megared.net.mx
********************************************************************

herwigb

I have had the very same warning about "permissions 0755 for browsing to work." ever since I have used Samba on OS/2 but this warning does not seem to have any impact, as browsing works here (and everything else that can work at the moment, works, too).

You do have a line "lock directory = n:/programs/samba/var/locks" in the [global] section of your smb.conf?

That directory exists?

Samba is somewhat picky about non-existing directories, it doesn't create (most) of them, just falls on its nose, and aborts with usually not too meaningful error messages...

Eventually set loglevel to 10, try again, and see if that reveals something relevant...
Kind regards,
HerwigB.

klipp

Still no luck herwigb! Yes I do have the "lock directory" line also. The only thing new that I didn't notice before is that when I "Restart Samba Server" I get in a os2 screen:
Restarting SMB services:
Shutting down SMB services:
Can't find pid for destination 'nmbd'
Done
Cleanup
Done
Configuring SMB services
Done
Starting SMB services
The Process Identification Number is 191
The Process Identification Number is 192
Done
Done

I'm using the .wpi version of Samba, maybe I should try one of you're versions?
I have the Requester & Peer services running -- is this a mistake?

Thanks for "hanging in there" with me, I really desperatly need Samba running on my Lan.

klipp
********************************************************************
Windoz Free! eCS 2.0 serving Linux, Windoz & OS2
rklipp@megared.net.mx
********************************************************************

klipp

Well, I got it working! I'm not exactly sure what the solution was, but the last thing I changed was to eliminate a bunch of the "shares" the install program setup in smb.conf. I deleted 8 of them and settled with just sharing a drive with another install of eCS on it.  It appears everything is working using anonymous login, next I'll plug in the different users and see what happens

Thanks again

klipp.
********************************************************************
Windoz Free! eCS 2.0 serving Linux, Windoz & OS2
rklipp@megared.net.mx
********************************************************************

klipp

Well, "Back to square #1" ReBooting and all my success's wen't down the tubes. I don't know what made it work previously, but I do know the problem is an inability of Samba to establish a server connection. When everything works "smbclient -L Internet" displays everything when invoked from the server or a client.
Now I'm back to:
"smbclient -L internet" responding "Error connecting to 192.168.1.105 (Invalid argument)
                                                                    "Connection to Internet failed (Error NT_STATUS_INVALID_HANDLE)

klipp
********************************************************************
Windoz Free! eCS 2.0 serving Linux, Windoz & OS2
rklipp@megared.net.mx
********************************************************************

klipp

A little more information. It appears to be NETBIOS detection problem. When it worked briefly , using the "Find SMB Machines" program (findsmb.cmd) it detected everything correctly: IP ADDR, NETBIOS NAME,WORKGROUP/OS/VERSION. Now while it doesn't work it detects:IP ADDR 192.168.1.105 correctly, NETBIOS NAME INTERNET correctly, WORKGROUP IBMPEERS correctly, OS Win 95 INCORRECT, VERSION unknown also INCORRECT.
   Is it possible to change the port samba uses?

klipp
********************************************************************
Windoz Free! eCS 2.0 serving Linux, Windoz & OS2
rklipp@megared.net.mx
********************************************************************

herwigb

I think you do not have a Samba problem (anymore) but a TCP/IP problem. For me (somebody correct me if I am wrong) it looks like if your routing doesn't work correctly, also name resolution might be broken.

The symptoms you decribe cannot be solved by removing some shares from smb.conf, so if you had it going briefly you must have made a different change...

I don't think it would make sense to exchange Paul's build with mine, they are both very similar (I definitely cannot produce "better" builds than Paul  ;) ), and I am very sure that my builds will not behave different than Paul's on your system.

Samba can be made to use another port, but that would not make sense either.

findsmb.cmd reports OS Win95 in case it was unable to detect something different, the reason for that is that Windows 95 cannot be detected by the ways findsmb.cmd normally uses, so in case nothing is detected Windows 95 is assumed.

You can run Samba and IBM Peer/Requester on the same machine (I have it that way for several reasons), but:

1.) NetBIOS over TCP/IP MUST be uninstalled (Samba can and will never ever work if it is installed).
2.) IBM Peer/Requester MUST use only plain NETBEUI.

Done this way, IBM Peer/Requester can only connect to plain NETBEUI machines, for all the other you MUST use the Samba Client for OS/2...
Kind regards,
HerwigB.

klipp

Hi, once again herwigb!
You have cleared up a lot of questions I had, thank you for you're time & patience!
GREAT NEWS! I think I've found the answer to the problems I've been having. This will probably make no sense at all, but it got me working! (I've tried installing Samba on three different machines now , all with different problems, seemingly intermittant!) In each case I was modifying the default smb.conf suggested by the setup program. In all three cases I un-installed and re-installed and didn't mess with the smb.conf and just accept what it came up with Samba would detect the server correctly (smbclient -L (name of server) and Samba would function GREAT!  This solution almost has to be irrevellent, BUT -- I'm up & running!
   Findsmb.cmd now finds the servers correctly and also finds my router 192.168.1.1(Gateway) -- I don't understand this, but probably its normal.
   You're utilities really remove the "PAIN" in using Samba on eCS/OS2 thank you again for you're efforts in supporting Samba.
   
klipp 
********************************************************************
Windoz Free! eCS 2.0 serving Linux, Windoz & OS2
rklipp@megared.net.mx
********************************************************************

klipp

Hi again herwigb! I've found what is causing the problem! What the solution is, I don't know.  Like I stated in my previous post, doing a fresh clean install and using the unaltered smb.conf file created by the install process all works fine. "Find SMB machines" gives the following:

IP ADDR                   NETBIOS NAME                 WORKGROUP/OS/VERSION
----------------------------------------------------------------------------------------------------------------------------------------------------------
192.168.1.11             BOSS                                    * BOSS/Unix/Samba 3.0.23d
192.168.1.12             BACKUP                                 BACKUP/Unix/Samba 3.0.23d
192.168.1.105           INTERNET                            IBMPEERS/OS2/ (eCS) /Samba 3.0.27a

Then, if I add a user (using "Add users"  in the Samba 3.0.27a for OS/2 and eComstation folder) --- I stop Samba, add the new user (klipp), reload configuration, then restart Samba Server ---  "Find SMB machines" gives this:

IP ADDR                    NETBIOS NAME                WORKGROUP/OS/VERSION
------------------------------------------------------------------------------------------------------------------------------------------------------------
192.168.1.11             BOSS                                   *BOSS/Unix/Samba 3.0.23d
192.168.1.12             BACKUP                               BACKUP/Unix/Samba 3.02.23d
192.168.1.105           INTERNET                          IBMPEERS/Win 95/unknown

And all access to INTERNET is gone. But, if I go back and delete the user I just added (klipp) and start Samba up again, everything is back to normal and everything works once again.
    I don't know what to make of this, possibly, am I adding a user incorrectly?  I'll keep screwing with it, maybe I can learn more about whats going on.  Sorry to keep bothering you but I thought this might be interesting to you.

klipp
********************************************************************
Windoz Free! eCS 2.0 serving Linux, Windoz & OS2
rklipp@megared.net.mx
********************************************************************

herwigb

You are welcome!

Glad it seems to work now BUT from the output of findsmb I see a big flaw in your Setup:

The WORKGROUP value MUST be the same on ALL machines regardless if they run Windows, OS/2, *nix, regardless if the server is Samba, IBM Peer, WseB.

You can find this hint on almost every readme coming with whatever distribution of Samba.

You are operating several workgroups in one subnet, which also can be done, but which does not make sense at all for half a dozen of machines and is just a way asking for problems.
Kind regards,
HerwigB.

klipp

Hi herwigb. I see you're point about multiple workgroups and agree! I set all workgroups to IBMPEERS and it made no difference, the results are the same -- I can not add users ( I can add them, but that causes the server to no longer be recognized).  This is probably something I'm doing wrong although the process seems pretty straight forward.  I guess I'll give up on Samba for now (gotta get back to doing what I'm supposed to be doing!) and wait for Paul to "crank out" a new updated version with hopefully some additional OS2 based documentation.
   Thanks again for all the help.

klipp
********************************************************************
Windoz Free! eCS 2.0 serving Linux, Windoz & OS2
rklipp@megared.net.mx
********************************************************************

Paul Smedley

Hi Klipp,

Quote from: klipp on 2008.02.03, 01:25:41
Hi herwigb. I see you're point about multiple workgroups and agree! I set all workgroups to IBMPEERS and it made no difference, the results are the same -- I can not add users ( I can add them, but that causes the server to no longer be recognized).  This is probably something I'm doing wrong although the process seems pretty straight forward.  I guess I'll give up on Samba for now (gotta get back to doing what I'm supposed to be doing!) and wait for Paul to "crank out" a new updated version with hopefully some additional OS2 based documentation.
   Thanks again for all the help.

Sorry I haven't been able to contribute much to this thread, hwoever a word of warning - I wouldn't hold your breath waiting for OS2 based documentation from me..... I really hate doing documentation! Of course, if someone contributes something, I'm happy to include it.... and of course Herwig has done a great job with all his Rexx utils and also keeping the wiki up to date.

Cheers,

Paul.

herwigb

Hi Paul,
> I really hate doing documentation!
I know and that's why I try to jump in here  ;)

> and of course Herwig has done a great job with all his Rexx utils and also keeping the wiki up to date.
Thanks for your kind words, I appreciate that (and I apologize for nagging you sometimes  ;) )

Kind regards,
herwigb
Kind regards,
HerwigB.