Sharing WSeB Server drives to Win 10/11 Clients

[ChrisGWarp]

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

[Paul Smedley]

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

[Roderick Klein]

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

[ChrisGWarp]

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

[Neil Waldhauer]

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.

[Paul Smedley]

https://www.neowin.net/amp/microsoft-begins-removing-ntlm-on-windows-11-24h2-server-2025-already/ won't help either...

[ChrisGWarp]

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

[ChrisGWarp]

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

[Dave Yeo]

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

[Paul Smedley]

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?