Re: administrative shares
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 21 Sep 2006 14:14:02 -0500
John already gave some good advice. I just want to add if there is a need to
not allow non domain computers to access domain computers [other then domain
controllers] you can use ipsec require policy. Ipsec by default in an AD
domain uses Kerberos authentication between computers to set up a security
association. Non domain computers can not use Kerberos. Ipsec however takes
planning and testing so do not implement without first reading up on
Microsoft documentation on how to deploy it and never assign ipsec
require/request default ipsec policy in Domain Security Policy.
Steve
"Auddog" <will_k@xxxxxxxxxxx> wrote in message
news:Ovs1ipY3GHA.3508@xxxxxxxxxxxxxxxxxxxxxxx
I was checking over our network when I started to discover a potential
problem that I have. I have a new laptop that has not been added into our
domain. I'm logging into the laptop as the administrator and I'm
connecting to my network via the wireless connection. I have been able to
connect to several (but not all) of our desktops administrative shares (C$)
without having to enter any credentials. Does anyone know how to fix this
problem? Any help that you may be able to provide is greatly appreciated.
A
.
- References:
- administrative shares
- From: Auddog
- administrative shares
- Prev by Date: Re: Clear User Name Field when Unlocking PC
- Next by Date: Re: Clear User Name Field when Unlocking PC
- Previous by thread: Re: administrative shares
- Next by thread: Windows XP Pro booting directly to Administrator Logon and password error
- Index(es):
Relevant Pages
|