OS2 World Community Forum
OS/2, eCS & ArcaOS - Technical => Networking => Topic started by: ChrisGWarp on December 12, 2024, 04:05:50 am
-
Hi Everyone,
I've virtualized my WSeB development box (from waaaaaay back) and my Windows NT 4.0 Server as well.
I can map (net use ... from windows) that works successfully, and I can even do a properties on the drive, but, a DIR fails. Mapping a drive and using a specified user, gives a different result entirely.
This is from a windows 11 client (Windows 10 was the same):
C:\Users\Chris>net use m: \\DEVELSMP\SMP-C
The command completed successfully.
C:\Users\Chris>dir m:
Volume in drive M is OS2
Volume Serial Number is 2D6E-F814
Directory of M:\
File Not Found
C:\Users\Chris>net use m: /del
m: was deleted successfully.
C:\Users\Chris>net use m: \\DEVELSMP\SMP-C /user:Chris
Enter the password for 'Chris' to connect to 'DEVELSMP':
System error 5 has occurred.
Access is denied.
C:\Users\Chris>
However, things like viewing the shares of the OS2 host works:
C:\Users\Chris>net view \\DEVELSMP
Shared resources at \\DEVELSMP
SMP Development Machine
Share name Type Used as Comment
-------------------------------------------------------------------------------
NETLOGON Disk Domain controller share
SMP-C Disk SMP Drive C:
SMP-D Disk SMP Drive D:
SMP-E Disk SMP Drive E:
SMP-F Disk SMP Drive F:
SMP-G Disk SMP Drive G:
SMP-H Disk SMP Drive H:
SMP-I Disk SMP Drive I: (CD-ROM)
The command completed successfully.
I'm guessing that there might be some SMB functions being called that the OS2 host does not recognise and is choking on.
Has anyone successfully mounted some OS2 Server drives (and Windows NT 4.0 for that matter too) from a modern Windows 10/11 client?
Ideally, I'd prefer to avoid Samba and stick with the base functionality, but (if I absolutely must, then I'll consider it).
Cheers,
-Chris
-
Hey Chris,
later versions of windows have deprecated SMB1 and the legacy NTLM authentication. https://winsides.com/enable-smb-1-0-cifs-file-sharing-support-windows-11/ might help....
-
Hey Chris,
later versions of windows have deprecated SMB1 and the legacy NTLM authentication. https://winsides.com/enable-smb-1-0-cifs-file-sharing-support-windows-11/ might help....
I tried that for years after Windows 7 and higher SMB 1 support is complete broken is my experience. I tested with a lot of LAN MAN settings in the registry but gave up.
SMB 1 support from Windows 10/11 seems to be to much broken. Maybe some magic registry setting can get it to work. But I spent long nights on this.
Roderick
-
Hey Guys,
Yes, it looks like they have broken things badly.
I can't tell if it's a function call or an auth error that is causing the issues (or an auth error caused by newer functionality).
Given the age of the systems, they probably removed any explicit support for them.
The SMB/CIFS stuff has been added and enabled.
Cheers,
-Chris
-
For all its faults, SAMBA networks pretty well with Windows. Also with Mac, Linux, iOS. I was kind-of hoping you would get SMB1/NTLM working in a recent Windows, but I'm not surprised that it isn't.
-
https://www.neowin.net/amp/microsoft-begins-removing-ntlm-on-windows-11-24h2-server-2025-already/ won't help either...
-
Well, that sums it up:
NTLMv1 is removed starting in Windows 11, version 24H2
And I'd only upgraded to W11 24H2 last week. This was one of the final tests that I wanted to perform.
Can I roll back a Windows 11 upgrade back to Windows 10? The command prompt still reports at Windows V10 ????
-Chris
-
As if to rub salt into the wound, I just successfully mounted an OS/2 Server drive from an XP VM. And a DIR worked.
So, yes, it looks like the removal of NTLM is what's causing the issues.
And all I wanted to do was to run an A/V scan using a modern tool against the old VM's - god knows what I'd find.
Thanks all for your help everyone! :)
-Chris
-
Can I roll back a Windows 11 upgrade back to Windows 10? The command prompt still reports at Windows V10 ????
-Chris
You have a week before Windows cleans up and you can't
-
And all I wanted to do was to run an A/V scan using a modern tool against the old VM's - god knows what I'd find.
You could try clamav?
-
Well. I'm back on this old chestnut. :)
I have a Win 7 Ultimate RC1 (of all things) VM! And that WORKS. I can mount an OS/2 share and DIR works.
I have a Win 7 SP1 VM and that's broken too. I've played with all of the SecPol.msc and RegEdit settings I can find, but although I can mount an OS/2 share, the DIR shows incorrect function calls.
To be clear, has anyone managed to get any Win 7 SP1 versions talking to an NT or OS/2 share?
Or, failing that, does someone have some setup instruction for SAMBA for WSeB (4.50 and 4.52)?
Cheers,
-Chris
Hey Chris,
later versions of windows have deprecated SMB1 and the legacy NTLM authentication. https://winsides.com/enable-smb-1-0-cifs-file-sharing-support-windows-11/ might help....
I tried that for years after Windows 7 and higher SMB 1 support is complete broken is my experience. I tested with a lot of LAN MAN settings in the registry but gave up.
SMB 1 support from Windows 10/11 seems to be to much broken. Maybe some magic registry setting can get it to work. But I spent long nights on this.
Roderick
-
Chris,
I am running WSeB on bare metal - an HP Elitedesk 800 mini that consumes about 12 watts at the desktop.
That system is an AOS 5.1 install minus the networking, with the networking from WSeB installed on top of that.
I am running the Samba 3.6.25 server for connections from earlier Macs, Win7, Win10, and connect OS/2 and WinXP via Netbuei to the WSeB. I have not been able to get any version of Samba server greater than 3.6.25 running correctly. I run a domain for WSeB and a different domain for samba. Previously I had WSeB running on top of ECS and used the same domain name for both samba and WSeB, but to do that you have to connect in a special sequence or you cannot connect to both at the same time: either samba first or WSeB first, I don't remember which. With different domain names you can connect to both at the same time without worrying about connecting in the correct sequence.
In order to connect the Win10 machine I had to add the line
max protocol = SMB2
to the samba.conf file on the samba server.
I have not been able to get any of the family's latest Macs to connect to this setup but the older Macs connect fine.
With the WSeB on AOS 5.1 I cannot get the samba configuration to work when adding a user. So I use the WSeB on ECS machine to make a configuration and transfer that the WSeB on AOS machine. You probably wont have that issue if you are running a "pure" WSeB install.
The other issue I have found with samba is it gets very unhappy when transferring a very large set (number of) of files - like for instance backing up the entire C drive by copying the individual files over. It works fine if those same files are zipped into one large file and that large file is copied across the network. This is not an issue with WSeB.