Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Mark Szkolnicki

Pages: [1] 2 3 ... 29
1
Article Discussions / Re: Too many cases of "OS/2 is dead, dying, etc"
« on: March 18, 2024, 10:03:47 pm »
Heh Guys!

Hello

Let's expect the next dead for "April 15th, 2024" when Hobbes NMSU gets disconnected.  ;D ;D ;D

Regards

Been using OS/2 since 2.0 then on to 2.1, 2.11 into Warp 3, then Warp 4, including fixpacks, all versions, then the eComstation versions, through to ArcaOS 5.0 - 5.1 - OS/2 was declared "Dead", as Martin points out since 1996, when IBM really did not want to develop for "Personal OS's" anymore, ceding that back to Microsoft and Windows, wanting to get back into solely the server / mainframe software business (Lew Gerstner was somewhat adverse to enthusiasts running "Doom" on what he considered a corporate business based Operating System),

People like Brad Wardell at Stardock jumped in to create remarkable pieces of software like Object Desktop and the first Version of Galactic Civilizations at the time, solely for OS/2, but with Gerstners business decision to get out, it was really IBM who first declared OS/2 dead, by stopping development, and developers like Brad had no choice but to move on (As an aside I still use Object Desktop on ArcaOS, and it still functions perfectly after all these incarnations of a "dead" operating system).

Twenty eight years after 1996, I still run most of my business, personal software and games on it (including virtual machines for DOS and Windows), on a full network with towers, portables and peripherials, including a wide variety of legacy systems and equipment on it, when people need something from the past (yes, there still are people who want to transfer data from 360K and 1.2 M floppies).

People, the word "Dead" has morphed technically to mean "depreciated" or "not supported as per intent", with corporate management placing big money and thousands of developers into creating a new version that the mainstream "must" move to every year or so, because they do not want to learn how to technically do things for themselves - with cloud computing and Smartphones, they substitute paying again and again to stay up to date, pushed by the companies they subscribe to, for many products that they never use to their full potential anyway - but it creates the constant revenue stream that a corporation craves - I remember reading an article many years ago, where someone in IBM management acknowledging they screwed up with the IBM PC, because once someone with the technical knowledge has the technology and knowledge on their desktops, standalone, and can maintain it themselves, they don't need to constantly go back to the parent corporation to pay and pay again .............

Personally, I don't need the latest and greatest every few months, and I don't need my data to live in the clouds for a fee. Strangely enough, when I turn on my systems and networks everyday, some of the youngest ones 5-10 years old, they still function perfectly, and if not, I fix them - haven't build a latest and greatest system in a while, but still ticking along on the successors to an operating system declared "dead" long ago ...........

I don't see any of our small talented group who continue to produce remarkable results caring about the word "dead", technology wise - I remember my dad saying no one is ever dead, if there are people who remember them.

For the newbies here, welcome - as for the rest of us, I don't think you'll find many, if any, of the usual suspects lurking here much interested in reading tombstones - we're to busy trying to do what we feel is important, even if its only to us.

Best of the Rest of the Week to you!

Mark

Mark Szkolnicki




2
Networking / Re: ArcaMapper and Network Protocols
« on: February 02, 2024, 02:57:39 am »
Heh Dariusz!

Mark,

...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...

Not sure if this contributing, but the following occurs every 10 secs:

Code: [Select]
...
MEMORY-ALPHA2024/01/31 15:55:04.43: 4 3:  session setup ok. Sending tconx <archive> <********>
...

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.

And FWIW (and its worth lots), Thanks!

At the moment I'm not quite sure if this is client or server related - the reason I asked about what the difference is between Samba Client and Server earlier - at the moment I'm not quite sure what I'm delving into, but at least its moving forward.

This has been an interesting troubleshooting lesson - and I've learned a lot about SMB - there is a "speed" setting in "Interfaces" as well, which I might try - but I'll have a look at your SMB.conf first.

M


3
Networking / Re: ArcaMapper and Network Protocols
« on: February 01, 2024, 05:56:02 am »
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 

4
Networking / Re: ArcaMapper and Network Protocols
« on: February 01, 2024, 12:42:28 am »
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


5
Networking / Re: ArcaMapper and Network Protocols
« on: January 28, 2024, 06:58:00 pm »
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)

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: [Select]
...
[2024/01/26 11:52:44.426000,  5] ../../auth/credentials/credentials_ntlm.c:182(cli_credentials_get_ntlm_response)
  NTLMSSP challenge set by NTLM2
...

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).


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.



6
Networking / Re: ArcaMapper and Network Protocols
« on: January 27, 2024, 03:03:36 am »
Hi Paul!

Given we're now seeing  a connection (which we weren't previously),  and that  Windows can connect without modification, I would remove the following from smb.conf:
Code: [Select]
   client lanman auth = yes
   client min protocol = NT1
   client NTLMv2 auth = no
   client plaintext auth = yes

and try with the defaults. Is that the full log.smbc? It seems shorter than I would expect...

Ran the logon three times with the paladin credentials, Paul - log.smbc ended each time at the statements you saw in the one I sent.

As to removing the smb.conf statements - taking all of them out and I couldn't see the resources in the Network Browser - I suspect I have to retain the client min protocol = NT1, but no time tonight to test.

M

7
Networking / Re: ArcaMapper and Network Protocols
« on: January 26, 2024, 10:14:50 pm »
Given we're now seeing  a connection (which we weren't previously),  and that  Windows can connect without modification, I would remove the following from smb.conf:
Code: [Select]
   client lanman auth = yes
   client min protocol = NT1
   client NTLMv2 auth = no
   client plaintext auth = yes

and try with the defaults. Is that the full log.smbc? It seems shorter than I would expect...

As to log.smbc I noted that too - I was expecting it to show an error at the bottom, but it was like it just ended abruptly - thought I'd let you see it as is first - will run it again and see what happens

M

8
Networking / Re: ArcaMapper and Network Protocols
« on: January 26, 2024, 08:14:17 pm »
Heh Paul!

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.

So this is where we seem to have advanced to, Sir:

Entering the IP as the UserName and the password for user "Paladin" the error message this time in log.ndpsmb is:

2024/01/26 11:52:44.42: 4 2: MEMORY-ALPHA2024/01/26 11:52:44.43: 4 2:  session setup ok. Sending tconx <archive> <********>
2024/01/26 11:52:44.43: 4 2: tree connect failed: NT_STATUS_ACCESS_DENIED

So login has occurred successfully and the session is set up, but if I'm reading this correctly it can't see the organizational structure of the resource.

That would make sense, as a blank mount was created - i.e. the ArcaMapper drive shows nothing in it (window empty when opened).

Attached that log and the latest log.smbc (both in .txt format)

That was with 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
   client lanman auth = yes
   client min protocol = NT1
   client NTLMv2 auth = no
   client plaintext auth = yes

Was also wondering, Paul, if you had ever used or seen used the "Interface" parameter, in smb.conf? As mentioned previously, I was wondering if setting up a [home] section for the ReadyNAS in smb.conf, with Interface and potentially other parameters would potentially be a solution for this?

As the Windows systems seem to connect fine to ArcaMapper, perhaps also moving client lanman auth and client plaintext auth, if needed, would also be appropriate specifically for the ReadyNAS resource under a [Home] section?

Just lateral thinking again,

M

9
Networking / Re: ArcaMapper and Network Protocols
« on: January 26, 2024, 07:21:49 pm »
Good Morning, Paul
(my time)

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.

I was thinking the same thing - I actually hadn't disabled ndpsmb.dbg at all, so planning to run a number of new tests today. I'm also wondering after reading up on the link you provided, whether it may be useful to create a (Home) resource section in smb.conf specifically related to the ReadyNAS.

Will get back here soon and Best, Sir!

M

10
Networking / Re: ArcaMapper and Network Protocols
« on: January 26, 2024, 01:03:18 am »
Heh Paul!

Try using the IP  instead of paladin

The error suggests paladin is unreachable -  you can ping the server?

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

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

11
Networking / Re: ArcaMapper and Network Protocols
« on: January 26, 2024, 12:42:11 am »
Heh Paul!

Try using the IP  instead of paladin

The error suggests paladin is unreachable -  you can ping the server?

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

12
Networking / Re: ArcaMapper and Network Protocols
« on: January 26, 2024, 12:17:42 am »
Hi Paul!

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

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






13
Networking / Re: ArcaMapper and Network Protocols
« on: January 24, 2024, 12:42:32 am »
Heh Alex!

Perhaps you could see if the following combination of options gets you anywhere:

Code: [Select]
   client lanman auth = yes
   client min protocol = NT1
   client NTLMv2 auth = no
   client plaintext auth = yes

Tried a number of things today - again no joy.

I think they were really good suggestions, Alex but still get the "no access" error message, regarding the credentials - if the ReadyNAS Pro 6 is seen clearly by ArcaMapper seen as a resource, there must be something I'm missing - tried a number of permutations of statements in SMB.conf (after reading the information in the link Paul provided) as well as your suggestions in OPTIONS, and using various User_Name/ Password combinations, including one new one within the 8.3 character limit, with a simple password (8 character), which I created - again nothing.

But as always, we soldier on - and learn from every success and failure.

Banging your head against a wall is painful ........... but if you learn something in the end, always somewhat rewarding ..............

M

 

14
Networking / Re: ArcaMapper and Network Protocols
« on: January 23, 2024, 04:31:28 pm »
Heh Alex!

Perhaps you could see if the following combination of options gets you anywhere:

Code: [Select]
   client lanman auth = yes
   client min protocol = NT1
   client NTLMv2 auth = no
   client plaintext auth = yes

Thanks! Will try it.

Paul gave me a link to a site explaining the implications of some of the statements, but had no time yesterday to follow up. I was thinking along the same lines, as I was assuming from some of Paul's explanation that certain services may need to be present and enabled explicitly in SMB.conf, not disabled - we will see if that is indeed the case

15
Networking / Re: ArcaMapper and Network Protocols
« on: January 22, 2024, 09:05:25 pm »
Both of Mark's servers are old. The new client demands more security, and perhaps the servers aren't offering it. You can reduce the client demand for security by adding this line to smb.conf

 client min protocol = NT1

NB: This only impacts the version of the protocol protocol - some of  the authentication methods (eg lanman) are also deprecated and need  to be forced on.

Hi Paul!

Was a busy 5 days guest entertaining and interacting - but its now Monday and back to tech troubleshooting ............

Modified smb.conf with the following (cut and pasted the statements you provided):

# 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 = 0
   client lanman auth = no
   client min protocol = NT1
   client NTLMv2 auth = no
   client plaintext auth = no

(I retained the format that was present in the original version of SMB.conf below, as I expected syntax may be sensitive to how it was formatted - cutting and pasting this seems to have dropped some space(s) in front of the statements

The original SMB.conf only contained the following:

# 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 = 0
   client min protocol = NT1

After making those modifications, rebooted and attempted to mount one of the shares on the Ready NAS Pro6, and received the same access denied message.

This was done in concert with Alex's suggestion about OPTIONS, but also did not work with the original default logon OPTIONS settings.

Its been quite a while since I accessed the ReadyNAS through the software admin package included with it called "RAIDar", but did that on the weekend to see how I set things up (in 2010 I knew little about RAID systems, so it was interesting seeing what I had done then)

The ReadyNAS could be set up for all or just a limited set of standard file sharing protocols of the time, including CIFS, NFS, AFP, FTP, HTTP and HTTPS. I saw that I chose CIFS for all (or perhaps that was a default added by the system), and AFP and HTTPS as well for a couple of the shares.

The shares I am most interested in mounting are all associated with CIFS on the ReadyNAS, if that helps a little more to isolate the access problem. I did try three separate User / Password sets that I created to log on to the ReadyNAS for those shares, and all of the accesses were denied.

I am curious about two things related to Samba and credentials, if anyone can enlighten me -

1) Two of the three User Names have more than ten letters in them and a strong level of password with more than ten characters in them. These are recognized no problem logging into the ReadyNAS through Windows, but is there a limit in User Name or Password as to number of characters that may be used in ArcaMapper?

2) One of the three User Names (paladin) is the same as I use to log into the workgroup (named PALNET) but with a different password - in that case originally playing with ArcaMapper, I did receive an error message saying "paladin is already logged on" if I used the different User / Password combination. In Windows I log on the "paladin" user name to access the system, and then access the ReadyNAS using "paladin" and the different password, so not sure if ArcaMapper handles that differently.

Anyway that summarizes my latest efforts - if anyone has any other ideas to try, I'm all ears.

Best of the Rest of the Week!

Mark



Pages: [1] 2 3 ... 29