>>>>Hi Stephen,
>>>>
>>>>>someone said that you need to call the primary share via $C that doesn't do it either.
>>>>
>>>>I tried to post this earlier, and had technical problems. That should read C$ in your original post, and this only works if you have administrative rights.
>>>>
>>>>HTH,
>>>>Bill
>>>
>>>Thanks! I knew I was close but,,,,
>>>
>>>This is a Peer to Peer network so I'm sure that the boxes leave our shop with the rights set for this administration correctly. < I hope they do >
>>>
>>
>>Then there's no domain authentiation - you have to explicitly log into each system. A workgroup is not a domain.
>
>Thanks Ed. The login is done automatically? I think. We have a domain at the office so that is what I'm testing with.
>

If you log into the domain (when you look at the User in User Manager, your logon ID is DomainName/UserName) then the domain's authentication can be used to authorize access to other domain members and other domains with trust relations. If you log into a local account, you never authenticate with the domain, and you must either at some point log into the domain to gain its authentication services, or log into each machine with an explicit local account/password.

IOW, if I log into my NT box \\FOO as EdR in Domain FOO, I'm logging into it's local account as user EdR; if I log on as EdR in Domain EDATHOME, I'm logging in as the domain EDATHOME user EdR. User EDATHOME/EdR could be authenticated by the domain controller for domain resource accesses.

In a peer-to-peer environment with no domain (IOW a workgroup) you log into each machine locally and each machine provides its own authentication and security - there is no domain authentication service available without a domain controller to administer it.