We have a single Windows 3.11 computer on our network. Users have not been able to authenticate ever since we upgraded our domain controllers to Windows Server 2008 R2 and disabled support for LANMAN hashes.
This computer only needs access to a single file location. To get around our authentication problem, we disabled all security to the network share in question. All has been working fine ever since.
The path to this folder has changed, so we need to modify the drive mapping within Windows 3.11. Unfortunately, it seems that any modifications of drive mappings through the command-line interface or GUI require user authentication. Each of the following commands triggers a logon prompt, which fails.
NET USE /PERSISTENT:LIST NET USE O: /DELETE /YES NET USE O: \\server\win311 ? /PERSIST:YES
I know that if I could only force the drive mapping configuration it would work just fine. Unfortunately, it seems that
NET USE isn't going to work for me.
I've checked through
win.ini etc. From what I've found online Windows may store these configurations in
wfwsys.cfg, but this is a binary file.
Does anyone know of a way to get around
NET USE prompting me for a password?
- According too KB90210, drive mapping information is stored in a file named
connect.dat. This file is encrypted to prevent people from modifying it by hand.
- The requirement to log on to our domain is likely being caused from left over configurations in the
win.inifiles. If the computer could be placed in peer-to-peer workgroup mode, we would probably be able to set up this drive mapping.
- We settled on creating a file share from the Windows 3.11 box. This computer cannot access remote resources, but other computers on the network can access its shares.