Re: unable to access non-trusted resource by default - why?
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 24 Jan 2007 22:55:38 -0600
Sharing the C or any drive drive of a domain controller is a very bad idea,
particularly when giving a user domain administrator access. It is best if a
domain controller not do any function other than being a domain controller.
If that is not possible for some reason then share only the folder that a
user needs access to and then give the user needed access to the shared
folder as a regular domain user and not a domain administrator. If the user
is trying to access from a non trusted domain the user possibly still can
access if the user uses credentials [user account/password] of a user
account in the domain that access is needed in though the user may need to
specify user name as domain\user.
Steve
"seeker01" <seeker01@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:499B84F8-110F-4A79-A19E-85D7DAAFECBA@xxxxxxxxxxxxxxxx
hi there,
How I enable a Windows XP Professional user to access a network
application
from a non-trusted Windows 2000 domain controller is bad, so need to fix
it
ASAP. XP user (from VLAN 1) is a member of a NT4 domain (from VLAN2). For
it
to work today, first I added W2K application server name (from VLAN3) to
host
and lmhost.sam files. Then I do map network drive to the Windows 2000
domain
controller C:\ root drive using the server IP address and domain
administrator password. The network access of both VLAN 1 & VLAN 3 are
fully
opened; VLAN1 & VLAN2 are fully opened; no access between VLAN2 & VLAN3.
Is
there a seamless solution without exposing the root administrator
password?
.
- Prev by Date: Re: Microsoft Management Console
- Next by Date: Re: digital signature on network batch file
- Previous by thread: Re: Microsoft Management Console
- Next by thread: Re: unable to access non-trusted resource by default - why?
- Index(es):
Relevant Pages
|