Here in the Research Institute, we came up with an interesting problem: Several years ago, we set up some of our machines to connect to various VAX/VMS directories, using Windows' map network drive feature. The process was pretty simple and straightforward. It worked just like connecting to a shared directory on another Windows machine.
However, on newer computers running (we thought) the same operating system, we could not make the connections work. No matter what we typed for a password, the system complained that it was the wrong one. Obviously, Windows was "munging" the password before sending it.
It turns out that in newer releases of Windows 95 and in all releases of Windows 98, the security has been enhanced. The same is true if you upgrade Windows NT 4.0 by applying Service Pack 3. The default behaviour in the older machines was to send passwords unencrypted. Newer releases encrypt the password. Unfortunately, Gallaudet's VAX/VMS system doesn't deal well with encrypted passwords. They must arrive at the machine in plain text.
So, the "solution" such as it is, is to cripple Windows security by messing in the registry. WARNING: THIS IS DANGEROUS!!! PROCEED WITH CAUTION! If you mess up your registry, you've screwed yourself royally, and may wipe out lots of valuable work. In addition, if you do everything correctly, you've opened a potential security hole in your network. But if you're careful, you should be okay.
Here's what to do. (NOTE: The instructions cover Windows 95, Windows 98 and Windows NT 4.0. The instructions for 95 and 98 are identical. NT 4.0 is a little different.)
On NT 4.0 systems use:
|ab||(Default)||(value not set)|
|ab||(Default)||(value not set)||Required.|
|ab||ComputerName||"PC????"||Required. Usually something like PCHB1B.|
|ab||FileSharing||"Yes" or "No"||Required.|
|ab||PrintSharing||"Yes" or "No"||Required.|
|ab||Workgroup||"Department" or "WORKGROUP"||If you've setup your workgroup correctly, everyone in your department will have the same name here.|
|0011||New Value #1||0x00000000 (0)|
If you've done everything correctly, you should now be able to map to your VAX/VMS directory using a path name of \\GALLUK\username, substituting a valid VAX username in place of username (Note: The double backslash at the start is required.)