Thread: Win2k Security
March 1st, 2003, 12:33 AM #21
His problem as I see it ....is he is not running a domain when he has "a lot of users " on the network.. For security reasons I would personally never enable/use the guest account just opens up to many problems. If you really need to share THAT printer and want to share it with everyone put it on a stand-alone machine that will act as NOTHING but a print server.-Mntsnow-
March 1st, 2003, 12:38 AM #22
in short. Since he is not running a DOMAIN with DOMAIN Accounts all accounts are LOCAL (meaning to the individual box) Accounts. To openly share the printer or other items under his current setup he will either have to create accounts for since user or enable the "guest account" which is very insecure by default
Welcome to the world of network security of NT vs 9x-Mntsnow-
March 1st, 2003, 02:07 AM #23
agreed... but obviously he could care less about security.
i just think a AD domain is soooo much easier to deal with
July 29th, 2003, 02:01 PM #24
- Join Date
- Jul 2003
There are two ways of doing what you require but neither of them is simple or "clean"
1) As stated previously make sure the account you use on the remote machine has the same name as a valid account on the server machine
2) Run a command that will prompt you for user name and password to authenticate to the server (this will be cached and you will then be able to map the printer using the cached info)
you could for instance type in: \\dadscomputer\c$ into the run textbox in the startmenu and it will pop-up with a username/password box, then type in dadscomputer\dad and leave password blank. Then you will be able to map and print to the printer until you log out (when you have to repeat the process).
There are no other ways I know of for doing this within a workgroup or "loose" environment.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)