13 replies
by downrighttired Accepted solution
by litehouse Accepted solution
by downrighttired Accepted solution
by cg it Accepted solution
create a logon script for the user that connects to the drive and provides credentials.
see microsoft's scripting center. http://www.microsoft.com/technet/scriptcenter/default.mspx
by downrighttired Accepted solution
by cg it Accepted solution
to capture packets then try to break in.
Since this is a domain, you can control the user experience and remove from users sight, the ability to look at settings that require access to the control panel and MMCs [such as logon scripts].
you can create a mandatory domain profile stored on the server that invokes the logon script and setup in Active Directory Users and Computer\User Account Properties\profile.
in there you can use the connect and list the mapped drive.
just ideas.
Nothing in IT is "safe" with the level of sophistication that hackers have and the tools available to them.
by dryflies Accepted solution
Force them to fix the DB problem. For many reasons, not the least of which is controlling security policy, I do not support local logins accessing domain shares.
I tried to add permissions for a computer\user account to a share and was unable to.
Now, looking at the other side of the problem. Just what is the problem with the DB? It sounds (with the limited info given) thaqt there is a possibility it is a permissions problem. review all of the permissions for the DB and see if you can modify them to allow the users access the db using their domain logins instead of local logins. That is a win/win because you now have access over your security policy and the users have transparent access to their shares. not to mention getting rid of the headache of when a user changes their local login password and have to relogin to all the shares.
Maybe not the answer you are looking for but this is the "best practices" answer.
if this is helpful, tell TR
by downrighttired Accepted solution
by ugadata Accepted solution
The NET USE command line option will allow you to save the username/password combination used to map a drive to a network share and could be used in a batch file or logon script.
Keep in mind this is not secure. anyone who can view the batch file can see the username/password. They may even see it as it is executed.
The authenication is sent as clear text (I think)and is also viewable over the network, if someone was "sniffing" around
by downrighttired Accepted solution
i work at a small office (8 users locally). Which is why letting them log on to their pcs locally hasnt really bothered me that much. The majority of the administration I do deals with the other 95% of our organization thats spread out from central america to europe. So GP's applied to the computer rather than users provide enough control for me. So threats on the inside arent a big concern.
Good suggestion though, thanks!
by ugadata Accepted solution
What about setting the permissions/security for the share to allow everyone.
Again, it's not secure but sometimes you do what you must to keep the masses happy
by downrighttired Accepted solution
by downrighttired Accepted solution
This discussion is closed to new replies.
Trending Hardware posts
Sort by Trending