Cannot get client to work

[REXX]

I have server and client installed on two (2) eCS machines, NETBios names HCM and HHCM. I have client access to both machines from Windows 7. I have client access to HHCM from HCM. I have no client access to HCM from HHCM.

The server installation on HHCM appears to be incomplete (no saving and updating of CONFIG.SYS and "homes" not created, even though it exists in the smb.conf file).

I executed the group of troubleshootinf tests on both HCM and HHCM (see the attached 2 files). On HHCM the domain is "BLACKBODY". It should be "HHCM. And there are other problems on HHCM, as indicated in these tests.

[REXX]

Many of the comments in Ticket #194 also apply to me:

1. No problems with Samba server, when using Windows 7 clients (all shares on HCM and HHCM afe available and accessible)
2. On HHCM Samba client will not show any subfolders on any of the shares (folders) present on HCM. When I try to click on any HCM folder, I get the hourglass and no response
3. On HHCM Samba client shows all of the subfolders existing in any shares (folders) on HHCM.

[Herwig Bauernfeind]

Please provide smb.conf files from server as well as from client(s).

[REXX]

Thank you for your response. Attached please find the smb.conf files from HCM and HHCM.

[Herwig Bauernfeind]

The smb.conf appear to be from servers both, none from a client. If the machines are acting both as servers and clients, make sure you have at least latest 3.3 on both server and client.

Try to use smbclient.exe to connect to servers. If that works, but not using EVFS/Netdrive/plugin - then client configuration is borked.

Eventually also post the output in the about box from EVFSGUI...

[REXX]

OK, I'm a little confused here. The smb.conf files are both from the server installation. I installed the server first, then the client (true on both HCM and HHCM). I used smbclut-1-1-1-674.zip as part of the install packages for the client. The "Readme.clut" file from that zip package states to place the smb.conf file in the "\samba directory in your %ETC% directory". On my machines that directory is "E:\MPTN\ETC\samba\", since E:\ is the boot drive. However, the smb.conf file already exist there, because of the server install. I did not replace the smb.conf from the server install.

Was I supposed to replace the smb.conf from the server install?

How do it use smbclient.exe to connect to a Samba server? Right now I'm starting the server on both machines (Start Samba server program object), then using evfsgui.EXE or ndpm.exe to start up client services. And of course client services fail on HHCM, but not HCM.

[REXX]

Also, I have the latest Samba server and client on both machines. Specifically:

Server

kLibc Runtime libraries (libc-0_6_5-csd5.wpi) GCC 4 runtime libraries (gcc4core-1_2_1.wpi) REXX libraries (rxlib4smb.wpi) WarpIn install package (Samba-1-1-2.wpi)

Client

ndpsmb-2_1_2-GA-20120315.wpi evfsgui-25RC1-20130217.zip smbclut-1-1-1-674.zip

[REXX]

Hello, I think if you examine the testing I did on HHCM (Tests_on_HHCM.TXT), you will find that I've already tested out using smbclient to connect. Does not work, when trying to connect to HCM (the other Samba server).

A key to this problem is that HHCM says that the Domain is "BLACKBODY". Why does it do that? It should be "HHCM".

[Herwig Bauernfeind]

Domain "Blackbody" is ok - that is the value for workgroup in both smb.conf files.

[Herwig Bauernfeind]

we need a loglevel 10 log from the server that stops responding.

[REXX]

OK, I'll send out a loglevel 10 later today.

I still wonder about my test results (part of my domain question). If you examine the 2 test files ("Tests_on_HHCM.TXT" and "Tests_on_HCM.TXT") you find that, using smbclient, HCM calls the domain "HCM", the name of the computer. HHCM calls it "BLACKBODY" the name of the workground. Also, HCM asks for the password on "Guest", while HHCM asks for the password on "HHCM". There is no "HHCM" account. I cannot get HHCM to request the password for "Guest". Why does smbclient do that on HHCM? How do I get HHCM to prompt for the credentials on user account (Guest, not HHCM).

[Herwig Bauernfeind]

What is the value of your %USER% environment variable? Samba Core asks for the password of the user defined there in order to user these credentials per default.

Use the following to force smbclient to use specific credentials

smbclient \\srv\share --user=MyUserName%supersecretpassword

[Herwig Bauernfeind]

Please also provide to output of

smbtree -N

in your network.

[REXX]

Hello, Thank your for your help and the information you provided.

Attached please find the loglevel 10 log files (log.zip). Also, please find the "About" reading from both Samba clients. When reading the log files, it is HHCM where I cannot establish a client connection to HCM.

[REXX]

Attached please find the "smbtree -N" output from both machines. The USER environmental variable is not defined on HCM. It is "HHCM" on HHCM. Thank you for that information. I guess that explains the behavior of smbclient.exe on HHCM

[Herwig Bauernfeind]

From looking at the logs I see that that there is something very odd going on, however I don't fully understand the how and what.

Please make sure that %USER% does not have the same value as the machine name. That confuses me (and possibly Samba, too) ;-)

For testing, I'd suggest to set %USER% to "root" on both machines. Later on, as soon as we have resolved the issues, I'd suggest defining a proper user for each machine (both not named HCM or HHCM) using smbusers.exe and use these.

Please provide the logs again with a proper setup of %USER%!

[REXX]

Good morning, Attached please find the log files from HCM and HHCM after fixing the USER problem (setting USER=root on both machines). Missing from the upload is a single file, log.smbd.guest.192.168.0.7. At 331K compressed, it is larger than the NetLabs file limit. Please note that on this Samba execution, HCM is 192.168.0.5 the Master Browser, while HHCM is 192.168.0.7.

[Herwig Bauernfeind]

From looking into the logs, I clearly see that you are providing a false password.

It looks like the user/groups setup on both machines is borked (groups missing, users setup wrongly).

I do not know, what you did during installation, but it appears there was clearly something wrong (erasing obligatory group entries or the like?).

I recommend to run

sscc /install 

and create a new backend and start over again. Then use

smbusers 

in order to setup user properly and add them to the appropriate groups.

Make sure you have at least TINFO5.DLL and READLN6.DLL (from rpm/yum) in your LIBPATH. Some revisions of the core binaries require these and the error messages in case they are missing are misleading...

[REXX]

Thank you for your help and recommendations.

[Silvan Scherrer]

is this ticket now fixed?

[Silvan Scherrer]

it seems like this one is either fixed or was a non issue.