OS/2, eCS & ArcaOS - Technical > Networking
ArcaMapper and Network Protocols
Mark Szkolnicki:
Hi Paul!
--- Quote from: Paul Smedley on January 25, 2024, 09:26:33 am ---Client logs might help us understand more.
Add to smb.conf:
log level = 8
Create a file in the root of the OS drive - ndpsmb.dbg
Reboot or restart ndctl.exe
try to connect
zip/share x:\var\log\log.ndpsmb & x:\var\log\log.smbc
Once logs are captured - you can reset log level and remove x:\ndpsmb.dbg
--- End quote ---
Thanks for the info Sir.
Following your instructions above for setting loglevel=8 and generating the logs you mentioned, I spent about 3 hours this morning trying various ideas and combinations of settings and generating a number of logs. I will summarize what I've tried, to see if it can give us a clue what the problem is.
I've attached one copy only of log.ndpsmb, because frankly after each test the logs pretty well said the same thing:
(I have included the file as .txt as I couldn't upload it otherwise)
session setup failed: NT_STATUS_IO_TIMEOUT
I tried it with three separate sets of credentials for the ReadyNAS, that I know work in Windows partitions on my systems.
Looking at the info present in log.smbc I thought the problem might involve SPNEGO, as in all cases, the log terminated with:
SPNEGO login failed: {Device Timeout} The specified I/O operation on %hs was not completed before the time-out period expired.
However, adding the parameter CLIENT USE SPNEGO = no, to SMB.conf and running the test again generated:
NT1 login failed: NT_STATUS_IO_TIMEOUT
I've included the log.smbc logs to this post, with both SPNEGO disabled and enabled. (I have included these files as .txt as I couldn't upload them otherwise)
I can relate additional information, if you or anyone else wants some idea of what else I tried, but as expected it indicates a timeout before completing the credential authentication -- the question is - WHY.
Much warmer here at the moment, in Alberta - imagine two Mondays ago it being -36 C as a high ............ -1 C today and a high of 9 C expected in 3 days.
Wild and Best!
M
M
Paul Smedley:
Try using the IP instead of paladin
The error suggests paladin is unreachable - you can ping the server?
Mark Szkolnicki:
Heh Paul!
--- Quote from: Paul Smedley on January 26, 2024, 12:20:52 am ---Try using the IP instead of paladin
The error suggests paladin is unreachable - you can ping the server?
--- End quote ---
The ReadyNAS is at static IP 192.168.1.90
Pinged it just before this message and it is there.
Will try using the IP in the logon, if that is what you are suggesting.
M
Mark Szkolnicki:
--- Quote from: Mark Szkolnicki on January 26, 2024, 12:42:11 am ---Heh Paul!
--- Quote from: Paul Smedley on January 26, 2024, 12:20:52 am ---Try using the IP instead of paladin
The error suggests paladin is unreachable - you can ping the server?
--- End quote ---
The ReadyNAS is at static IP 192.168.1.90
Pinged it just before this message and it is there.
Will try using the IP in the logon, if that is what you are suggesting.
M
--- End quote ---
Don't have a lot of time, given the supper hour at the moment, but we may be making progress, Paul.
Tried the IP just before dinner as the User logon, plus password and got an error message potentially related to incorrect protocols as opposed to the timeout message - could be I need to adjust or remove some of the statements in smb.conf
Will see if I can try that later this evening or tomorrow morning.
But, as always, the reason I find helpful developers and hackers posts so interesting - you, Sir, know what to look for - I don't, experienced user or no.
M
Paul Smedley:
Hey Mark - glad we're making progress - if you re-enable log level in smb.conf, and recreate ndpsmb.dbg and capture a log - the full log may tell us what the authentication problem is and guide how to fix it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version