🚀 go-pugleaf

In article <277099389wnr@dagorn.demon.co.uk>, david@dagorn.demon.co.uk says...
>
>I've recently been installing a network which has an NT server and 
>several PC's running Windows for Workgroups 3.11.  It works fine but, 
>you guessed it, I do have one or two problems with it.
>
>Problem 1 :
>
>Is there any way to get rid of password lists for WfW?  If a user logs 
>into the Workgroup they are always prompted to create a password list if 
>they didn't create one beforehand.  This is all well and fine for the 
>Workgroup, but when it comes to logging into the Domain they have the 
>option to save this in their password list as well.  And users being 
>users they won't hesitate to accept these options to make life easier.
>
>I have had a brief chat with a Microsoft technician but all to no avail. 
> The problem is simply that logging into the Workgroup will 
>automatically log you into the domain without prompting for the password 
>(and YES the company does want their users to log into the Domain at 
>startup, but not without entering a password!).  Whilst you need a 
>password to unlock your password list you still have the problem of 
>maintaining such lists on each individual PC, exactly what the NT server 
>was intended to avoid.
>
>Surely there must be a way around this hassle.  As far as I can tell you 
>can't simply log in to a Domain at startup, you have to log in to the 
>Workgroup first!?
>
>Problem 2:
>
>The other problem lies with access times.  By default, WfW loads in the 
>basic redirector and this has a major affect when downloading data from 
>the NT server.  This was first noticed when accessing a DOS program 
>which has most of it components on the server itself.  When running from 
>Windows it takes ages before a client shows any signs of activity (the 
>hard drive shows no activity for a good while) and for that matter the 
>same can be said of the server.  Eventually it does kick into action but 
>downloading is very slow.
>
>When you compare this with the DOS setup, which was intended to avoid 
>Windows and run this package straight from DOS itself (calling NET START 
>FULL beforehand in its batch file) the difference is remarkable.
>I assumed this to be the use of the full redirector since putting 
>AUTOSTART=FULL in the SYSTEM.INI file brings the same performance under 
>Windows.
>
>However, the cost is that a client can't share files or printers when 
>this is done.
>
>I've tried another setting which loads the Full redirector as the 
>preffered one and notice that this action alone is not the solution.  It 
>seems to be when the adapter is loaded with NDIS, which shows prior to 
>login which gives the benefits, as this doesn't occur when asking for 
>just the full redirector to be loaded.
>
>I'm therefore wondering if there is a Windows equivalent to this DOS 
>load in (it does say that the service was started from DOS and that file 
>and print sharing are disabled).
>
>Any help/suggestions for these two dilemnas would be greatly 
>appreciated.
>
>Many thanks in advance.
>
>-- 
>--------------------------------------------
>| david    EMail david@dagorn.demon.co.uk  |
>--------------------------------------------
>

Hi

There is a utility called ADMINCFG.EXE which allows you to modify the 
WFWSYS.CFG (If memory serves). You can disable password cacheing with this 
utility, and therefore you only get prompted for a domain password. I believe 
that once you have been validated by the server, you should have no problems 
with workgroups. 

Hope this helps.

Paul