6
« Last post by ChrisGWarp on Today at 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
Recent Posts