OS/2, eCS & ArcaOS - Technical > Networking
ArcaMapper and Network Protocols
Dariusz Piatkowski:
Mark,
1) If you include 'client max protocol = NT1' in smb.conf, is there a difference?
Further on this topic, you could try setting 'ntlm auth = yes' to force just the use of NTLMv1 authentication protocol. I say this because I see the following in the log:
--- Code: ---...
[2024/01/26 11:52:44.426000, 5] ../../auth/credentials/credentials_ntlm.c:182(cli_credentials_get_ntlm_response)
NTLMSSP challenge set by NTLM2
...
--- End code ---
which to me means: yup, it's trying to use NTLMv2 authentication.
In fact, 'ntlm auth' and 'lanman auth' go hand-in-hand, both need to be set to 'no' in order to force NTLMv1.
2) Do you have 'name resolve order =' line in your smb.conf?
This has previously caused me some issues as I wasn't able to resolve my lan hostnames and needed to use their static IP addresses. It's been a while though and today things work fine here with the following setting:
'name resolve order = lmhosts host wins bcast'
Above comments based on my reading of O'Reilly's "Using Samba" 3rd ed, 2007 (yup, a little old).
Mark Szkolnicki:
Heh Dariusz
Hope your having a fine start to the year - we were in a frozen hell here tow weeks ago (-47 C start only going up to -36 C)
Today we're supposedto hit 9 C (yes that is without the minus)
--- Quote from: Dariusz Piatkowski on January 27, 2024, 10:49:00 pm ---Mark,
1) If you include 'client max protocol = NT1' in smb.conf, is there a difference?
Further on this topic, you could try setting 'ntlm auth = yes' to force just the use of NTLMv1 authentication protocol. I say this because I see the following in the log:
--- Code: ---...
[2024/01/26 11:52:44.426000, 5] ../../auth/credentials/credentials_ntlm.c:182(cli_credentials_get_ntlm_response)
NTLMSSP challenge set by NTLM2
...
--- End code ---
which to me means: yup, it's trying to use NTLMv2 authentication.
In fact, 'ntlm auth' and 'lanman auth' go hand-in-hand, both need to be set to 'no' in order to force NTLMv1.
2) Do you have 'name resolve order =' line in your smb.conf?
This has previously caused me some issues as I wasn't able to resolve my lan hostnames and needed to use their static IP addresses. It's been a while though and today things work fine here with the following setting:
'name resolve order = lmhosts host wins bcast'
Above comments based on my reading of O'Reilly's "Using Samba" 3rd ed, 2007 (yup, a little old).
--- End quote ---
Above comments based on my reading of O'Reilly's "Using Samba" 3rd ed, 2007 (yup, a little old).
Going from back to front - that last remark hit home first, and I laughed, Sir .............. because I resemble it <grin>
As to the other suggestions, I will try them - from using multiple incarnations of various smb.conf statements (and mostly not knowing a thing about what I'm doing), I'm always coming back to seeing using the IP address as the key, and finding that for some reason, the ReadyNAS is not seeing the login correctly, based on the error statement attached to the login.
So I tried the "interfaces" statement and idmap, the "name mangling" statements and also different syntaxes when it came to using the the IP as the username (ie. using the subdirectory I wanted to attach as part of the IP username) - in all cases I kept getting the same error, which was showing I had made some progress from nothing been seen in the first place, but still chasing my tail.
So it won't hurt to try your suggestions - the worst thing that can happen is that I loop back to where I am - but it might also mean that something may change in the logs being generated - bast case would be that it mounts successfully.
But thanks for the suggestions - will get back here after I try them out.
M
Mark Szkolnicki:
Heh Guys and Gals!
Haven't been idle in the last few days, related to all the great suggestions I received - just busy with more entertaining and crazy 10-14 C weather - ran many permutations of statements in SMB.conf, and always got the same failure to connect, protocols not recognized messages .......... until now.
I was finally able to mount the ReadyNAS Pro 6 using the following SMB.conf:
# Samba Configuration file for Clients
# Required place for this file %ETC%\samba\smb.conf
# Change the value of WORKGROUP according to your needs
[global]
workgroup = PALNET
loglevel = 8
interfaces = eth0 192.168.1.90/255.255.255.0
client min protocol = NT1
client max protocol = SMB2
ntlm auth = yes
name resolve order = lmhosts host wins bcast
client NTLMv2 auth = no
I suspect the one item that solved this was probably using the "interfaces = eth0 192.168.1.90/255.255.255.0" statement, as I didn't have to try to mount the resource using the IP address, based on Paul's suggestions.
Dariusz's suggestions were useful as well, but still not sure if they helped solve the problem - I'm reporting this early - I need to subtract lines to see what is actually needed and what is not - but as with the Beatles song its always nice to "get by with a little help from my friends".
Still need some help though, Guys and Gals - mount connection is VERY slow (30 seconds), and accessing the subdirectories by clicking them in the resource is slow as well (about 30 seconds). Have attached the log.ndpsmb and log.smbc as .txt files, to see if you have any bright ideas.
Perhaps I need to have more parameters in the "Interfaces" statement related to speed, but a big step forward related to solving this issue, as the mount shows the directories now.
For people looking in, I also found the file TESTPARM.exe very useful - it can be run from an ARCAOS prompt, and is a Samba related file which allows you to test statements in SMB.conf, to see if they work.
But a nice present to receive at the end of January!
M
Mark Szkolnicki:
Heh!
Later in the evening, but confirmed most of the SMB.conf statements present are unnecessary.
Down to:
# Samba Configuration file for Clients
# Required place for this file %ETC%\samba\smb.conf
# Change the value of WORKGROUP according to your needs
[global]
workgroup = PALNET
loglevel = 8
interfaces = eth0 192.168.1.90/255.255.255.0
client min protocol = NT1
One thing I did notice - can't find the Windows 7 shared resources at the moment, even though I could mount them previously - may need to put the Interfaces statement under a [homes] specific resource in future - but that is an issue for tomorrow ................
Good Night and Best!
Mark
Dariusz Piatkowski:
Mark,
--- Quote from: Mark Szkolnicki on February 01, 2024, 12:42:28 am ---...Still need some help though, Guys and Gals - mount connection is VERY slow (30 seconds), and accessing the subdirectories by clicking them in the resource is slow as well (about 30 seconds). Have attached the log.ndpsmb and log.smbc as .txt files, to see if you have any bright ideas...
--- End quote ---
Not sure if this contributing, but the following occurs every 10 secs:
--- Code: ---...
MEMORY-ALPHA2024/01/31 15:55:04.43: 4 3: session setup ok. Sending tconx <archive> <********>
...
--- End code ---
and I'm thinking there is parameter somewhere that controls how long a share cache can exist? So perhaps if you have this set to 10 secs. it's driving this.
EDIT
====
For what it's worth, I've attached my smb.conf, used for client side purposes as I do not run the server on my OS/2 box.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version