I think Richard's suggestion is the best. Set Logon to the domain in the network properties. That way the domain will handle the logon & the server will handle all the permissions. It is a long time since I used Win9x but I think that if you don't then the local machine handles everything. Then you have to be in the same local workgroup or domain as the machine you wish to access when you boot up. The logon ID that Win9x picks up locally will be then be the logon ID it feeds to the machine you are trying to attach. If it is a machine inside a domain, that machine will insist on you supplying a domain authorized logon ID plus password.
If your Win9x is suddenly asking for a logon ID you changed something in the network properties.
Also, without a domain server logon, I do not think you can autorun a logon script. You need to logon into the domain & auto pick up the script from the netlogon share. If remember, I think you can auto run a script on the local machine but you might need to run it from the autorun key in the registry. This is real old stuff - trying to find advice on the non-standard use of Win9x in a domain will be a challenge.
Edited by Jack Lothian (2006-03-23 01:45 AM)
_________________________
Jack
