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 4 ... 29
16
Networking / Re: ArcaMapper and Network Protocols
« on: January 19, 2024, 06:57:06 pm »
Heh Rich!

how does Samba server fit into ArcaOS, as it seems ArcaMapper is about using Samba Client

It's no different than, say, http:
* if you want your machine to send files to other computers on request, Samba Server
* if you want your machine to request files from other computers, Samba Client

A Peer network just combines both functions in a single package.

From both you, Rich, and Paul, Thanks.

It may sound like a stupid question to some, but as my Dad, now 20 years gone used to say - "There's no such thing as a stupid question, if you really don't know"

Haven't had a chance to try out Paul's suggestions just yet - a birthday (my wife's) yesterday, and entertaining has made this a busy week.

Best to you, Sirs!

M

17
Networking / Re: ArcaMapper and Network Protocols
« on: January 18, 2024, 11:49:32 pm »
Hi Paul!

Long time no talk

I expect you're rather more comfortable down under than us rather frozen Albertans


You mention the NAS is circa 2010? It will be running an ancient version of Samba, and probably using an authentication mechanism that has been deprecated in Samba 4.x

It may be worth trying adding some or all of the following to smb.conf - and either rebooting, or killing and restarting ndctl.exe before re-trying:
Code: [Select]
client lanman auth = no
client min protocol = NT1
client NTLMv2 auth = no
client plaintext auth = no

Note that it's worth reading https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html to understand that the impact of these switches is, in terms  of  network security.'

If all this fails,  I'd be suggesting we work through enabling debug logging for the Netdrive plugin which should show the issue -  I'm pretty confident though,  that it's a mismatch in authentication protocols due to increased security in the Samba client included in AOS.

At some point (probably Samba 5.0) all the code for support of SMB1 will be removed,  as opposed  to being deprecated.

From my general reading on Samba so far, Paul, as well as the ArcaMapper Docs, I was also thinking along the same lines as you when I started this subject, about mismatch in the authentication protocols - as mentioned at the top of this thread, my technical familiarity with Samba is nil - most of my experience has been with the original peer networks and Netbios over TCPIP for decades, so a steep learning curve. I will have a look at the link you suggested with interest.

As you know my involvement with Linux / Unix is also nil, as I don't wander between the worlds like most of you gents who are developing and porting, so I needed a few hints as to where to start the troubleshooting, with a system that is Unix based - SMB.conf files are not my bag .......... at least so far.

As to:

client lanman auth = no
client min protocol = NT1
client NTLMv2 auth = no
client plaintext auth = no

I already have client min protocol=NT1 in SMB.conf (it seems to be in the .conf file by default)

Will add the other statements in the order you have them in, and see if that helps.

Just one other thing - as I mentioned, peer networks are what I'm familiar with - your other thread is about porting Samba Server, newer version - how does Samba server fit into ArcaOS, as it seems ArcaMapper is about using Samba Client - any way you can quickly sum up how the two fit into this - the ArcaMapper docs mention it is really a combination of multiple programs thrown together to produce the desired outcome.

if its too complex to quickly explain, don't worry about it - I'm trying to catch up on a year and two months of developments, when I have the time. I'm sure I can puzzle out what all of you have been up to, eventually.

Best to you Sir as always!

M


18
Networking / Re: ArcaMapper and Network Protocols
« on: January 18, 2024, 11:03:26 pm »
Saludos to you as well Roberto

I now can access at Least one of the Windows machines, a portable running Windows 7 - the ReadyNAS is still not accessible for mounting and logon
Mark
Is ReadyNAS in WORKGROUP?
In all cases you can put the ip of your ReadyNAS without Workgroup, similar //IP/folder
Saludos

The ReadyNAS is the system listed as MEMORY ALPHA under PALNET which is the name of my Network workgroup as seen in the graphic I provided, I have it as a storage location for archiving files from all of my systems, as backup.

M

19
Networking / Re: ArcaMapper and Network Protocols
« on: January 18, 2024, 04:59:11 pm »
Hi Alex!

Long time no talk!

In the New Connection dialog, select the "Options" button and try the following connection settings:
  • Enable encryption: turn OFF
  • Enable NTLMv1: turn ON

Tried you suggestion, Sir ................. AND IT WORKED!

I should say though it worked ......... but only partially.

I now can access at Least one of the Windows machines, a portable running Windows 7 - the ReadyNAS is still not accessible for mounting and logon.

I've attached a picture showing the Network Browser, when I display the resources available on MEMORY ALPHA - I don't know where ArcaMapper gets the information but it shows it as a UNIX based system in the bottom left of the window. As it is circa 2010, but still functions perfectly, I assume that the problem may be one of two things:

1) the credentials are still not being recognized

2) something may be different related to the network protocols it recognizes

Any idea, anyone, as to what those protocols may have been?

Best!

Mark


20
Networking / Re: ArcaMapper and Network Protocols
« on: January 17, 2024, 09:59:45 pm »
Quote
Reading generally it seems there are statements you can add related to adding specific protocols to SMB.conf, like Netbios - there were also statements about various network protocols listening on different ports - was looking to see if anyone can tell me any success stories about connecting to some of these legacy systems under ArcaMapper.

Yes, there are many (mostly useless) things. You probably want to get back to the DEFAULTS, because they work most often. The defaults may need to be restored in the other devices (NAS, win 7) too.

It would help if you told us exactly what you are doing, and what the results are.

Been a busy day today, as we had to pick up our daughter, in from Winnipeg, for a visit so not much time to reply today and I will be brief.

By the defaults, Doug, I'm assuming your meaning in ArcaMapper and in SMB.conf, when I've opened Network Browser - those are at the default levels, and no additions or deletions related to any of the settings.- IOW as they would be the "right out of the box" setup after installation of ArcaOS v5.1.

I think its rather obvious what I'm trying to do - namely use ArcaMapper on one machine the way I think it was intended - namely, to access other systems, to mount partitions on those systems to ArcaOS, so I can access and transfer files located there. I have used Netbios over TCPIP, and File and Print Client extensively on my network in the past to transfer and access items between ArcaOS / OS/2 systems, but those network protocols are now very old, and outdated and I have not been able to do this in the past with the type of systems I have mentioned.

I can see both the partitions present on the ReadyNAS and on one of the other computers running Windows 7 in the ArcaMapper Network Browser. When I attempt to mount a partition from either as a connection, I get the window asking for the logon credential for these systems, so the mount can occur - entering the correct user name and password on either brings up an error message about the logon credentials not being recognized.

Its about as simple as that.

M

21
Networking / Re: ArcaMapper and Network Protocols
« on: January 17, 2024, 05:10:43 pm »
Heh Neil!

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

Actually that was in SMB.conf by default so no joy there.

Reading generally it seems there are statements you can add related to adding specific protocols to SMB.conf, like Netbios - there were also statements about various network protocols listening on different ports - was looking to see if anyone can tell me any success stories about connecting to some of these legacy systems under ArcaMapper.

M

22
Networking / ArcaMapper and Network Protocols
« on: January 16, 2024, 08:06:33 pm »
Good Morning Guys!

That is, good if you like waking up to -41 C with an overnight low of -46 C. We had 3 months of balmy winter here in Alberta and are now paying for it - I see some of our colleagues in the states are having winter storms, so I guess we're all in it together.

However, the cold is allowing me to turn my thoughts once again to technical problem solving, after approximately one year and two months of constant emergencies, both personal and for protecting the greater public good, (you can see what that entailed in another general post of mine from December).

But I thought I'd solicit some opinions from the brain trust here, related to a problem I'm having with ArcaMapper. I already had a look at a couple of the other more Samba specific topics, but I decided to start a new one, as this problem seemed more specific to using and connecting, as opposed to the technical intricacies of the client or server itself.

I finally installed ArcaOS v5.1, and was attempting to get the current version of ArcaMapper to mount items in two ways - one with my NetGear ReadyNAS server and the other with some of my towers running dual operating systems (ArcaOS and Windows 7).

The Network Browser does see both the ReadyNAS and Windows 7 systems as separate machines and displays the partitions in the window on the right, however when I attempt to create the proper credentials and apply those to mount the item I select (ie. the credentials I successfully use accessing the resources in Windows) the credentials are not accepted.

Reading the ArcaMapper documentation (yes, some people still do that), and some general documentation related to Samba and SMB - I suspect the problem is actually related to Samba and SMB.conf - I think the NetGear ReadyNAS uses Unix based network protocols (whatever they were around 2010) while Windows 7, I think uses SMB2.1.

Reading up both on Samba and SMB.conf, generally and the help documentation provided with ArcaMapper, it looks like I may need to specify these other network protocols directly in SMB.conf - however, not knowing much about the specific workings of Samba, especially our current version(s), I'm on the normal steep technical learning curve at the moment.

I will say as background, I've never been able to successfully connect to these resources using ArcaMapper, or its previous incarnations under ArcaOS in the past - so I decided a cold winter day was the time to try to solve this problem once and for all.

I already reviewed the limited troubleshooting options in the ArcaMapper docs without success (client minimum protocol=NT1 is already present in SMB.conf). Are there any other specific statements that I should add or modify, or am I looking in the wrong direction?

Any have thoughts that will lead me to the correct path, as opposed to going over the cliff?

Best and a fine Week to all!

Mark

23
General Discussion / Re: A Ghost of Christmas Past is Still Present
« on: December 28, 2023, 02:43:04 am »
Sounded inclusive to me, Sir - there's many people who may have joined in the last year and one month for me, that I've never met, and many we know that are still plugging along, in their own brilliant way, keeping the dream alive, Unix and ArcaOS both - like Martin, we're just the old souls of the group, Dariusz - I go back to Compuserve, Golden Compass, and OS/2 2.0 .............. !

The Christmas Season is always about coming together, in any way, no matter who's here - in a troubled world, I'm sure the sentiments resonant with everyone here ..............

M

24
General Discussion / Re: A Ghost of Christmas Past is Still Present
« on: December 25, 2023, 10:14:46 pm »
And to you, Dave! Replied to Lewis about Netlabs - see you and Steve did the same.

M

25
General Discussion / Re: A Ghost of Christmas Past is Still Present
« on: December 25, 2023, 09:51:18 pm »
Heh Dariusz:

Good hearing from you too - life in the storm is always interesting - but having been there for about 42 years its not unusual - merely "Interesting"

More later - but hope your having a fine Christmas Day and Best!, Sir

M

26
General Discussion / Re: A Ghost of Christmas Past is Still Present
« on: December 23, 2023, 04:54:51 pm »
Thanks Martin - as related have not had a moment to consider any of the GamePad / Joystick related stuff - as you can see games had to give way to life ............. and life cannot be considered a game, when lives are on the line.

Plan to review where the conversation went after about a year and a month, as with many of the other topics I was following - if I have any thoughts, I will let everyone know.

Best of the Christmas season to you and all you hold dear, Sir

M

 

27
General Discussion / A Ghost of Christmas Past is Still Present
« on: December 23, 2023, 05:52:14 am »
Hello Everyone!

Well, I'm not haunting a miser by the name of Scrooge, but just wanted to let all of you know a Ghost of OS2World past is still present.

Its been a strange odyssey for me since November 11, 2022.

A major death in the family then, and another death two months later (luckily not mine nor my wife's, but still major in the family). Then a couple of surgeries in between (this time involving my wife). And finally a constant stream of crisis related work - Pandemic Planning in British Columbia first, then a horrendous forest fire season in Western Canada starting in May and heading into October, had me busy in Alberta, BC and the Northwest Territories. Then a rush job creating an Emergency Response Plan for a client in two weeks, finished only last week.

So no time to post or even lurk, but in my limited off time I did spend some time learning the intricacies of 3D printing.

But since I by chance talked with Dave Yeo a couple of weeks ago, I thought I'd stop in, to say that, no, I have not dropped off the planet or been transported into an alternate reality (although some days I wonder if that would be preferable, given the state of global affairs)

I hope to be less ghost like and more visible here sometime in the New Year, but we will see. In the meantime, a fine Holiday Season to all - may all your Christmas Seasons be blessed, and may all our 2024's be a lot less chaotic than this year, and much more grounded in the name of Peace.

Best!

Mark

Mark B. Szkolnicki

28
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: November 18, 2022, 04:21:47 am »
Heh Martin!

Hi Mark

Just for my records and wiki pages, can you please let me know the list of the joystick devices that you have that you consider that are working fine?

On my side I have:
- Huskee PSX Adapter - 0c12:0005
- PCS SNES Gamepad - 0810:e501

According to you guide you have:
- Logilink Gameport to USB converter
- Thrustmaster T. Flight Stick X

And I guess that Wim Brul tested the:
- Manta MM812

Mark, can you help me with the HardwareIDs for your two devices?

By the way, I think I will have some time this Saturday and I will go and check all the OS/2 Native games from my OHFOWG project to look for more games with joystick support.

Regards

Will get to this at some point, Sir - had a death in the family on Nov. 11 (Lou Gehrigs disease - ALS) so dealing with it as it is Annes former brother-in-law from a former marriage - in this year one thing at a time - with your dad I know you'll understand and Best!

M

29
Games / Re: DOS VDM - USB and Game port Gamepad support
« on: November 09, 2022, 07:07:22 pm »
Heh Wim!

Hi David,

..
  Here is the line I use in CONFIG.SYS:

DEVICE=C:\OS2\BOOT\USBECD.SYS /D:046D:C21#:4014 /N:$GAMEPD$ /S

 seems to work fine in XInput mode, not so in DirectInput mode.
..

I think that is because bcdDevice 4014 applies to XInput mode whereas bcdDevice 0414 applies to DirectInput mode.

Regards,
Wim

P.S. I am already lurking for quite a while now and gradually beginning to like to react again.

I was curious as to what you thought about XInput mode vs DirectInput mode for these GamePads - should both work with your drivers?

M


30
Multimedia / Re: Updated Uniaud32 build
« on: November 08, 2022, 11:57:05 pm »
Hi Mark!

That weather sounds hideous! We've just had our first tast of summer, with a couple of days above 30C - it's been glorious!

Sorry about the issues with Trac - I've now created a Uniaud32 project at my own bug tracker - https://mantis.smedley.id.au - please raise issues there.

Cheers,

Paul

Thats normal January weather here, Paul ........... only this is beginning of November  ???

Thanks for the link between being out for supplies, lunch and more shovelling, no time today - will have a look tomorrow and Best!

M

Pages: 1 [2] 3 4 ... 29