Re: Active Directory
- From: Arne Garvander <ArneGarvander@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 1 May 2008 10:42:00 -0700
Blank for server seems to have connected to something.
I have no clue what to do next. I am a developer not an admin.
--
Arne Garvander
Certified Geek
Professional Data Dude
"Joe Kaplan" wrote:
Generally, if AD is deployed correctly and the current machine is domain.
joined, you can provide ldp with a null value for the server name and it
will locate a domain controller based on the domain that the current user is
logged in to. You can also usually just put in the DNS name of the domain
you want to use and it will find a DC in that domain.
There is generally no reason to change the port as AD always uses port 389
for LDAP.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Jack Black" <jackisback@xxxxxxxxxxx> wrote in message
news:OyNtVf6qIHA.1872@xxxxxxxxxxxxxxxxxxxxxxx
Either check with your network admin or use a port scanner on your network
and scan for responses at port 389 (for example).
Jack
"Arne Garvander" <ArneGarvander@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:308050B7-3279-458D-AFBA-B7998A0F0835@xxxxxxxxxxxxxxxx
Thanks,
I have no idea at what Ip address I would find my active directory.
Any tips?
--
Arne Garvander
Certified Geek
Professional Data Dude
- References:
- Active Directory
- From: Arne Garvander
- Re: Active Directory
- From: Jack Black
- Re: Active Directory
- From: Arne Garvander
- Re: Active Directory
- From: Jack Black
- Re: Active Directory
- From: Joe Kaplan
- Active Directory
- Prev by Date: Re: Active Directory
- Next by Date: Re: Smart card enrollment issues
- Previous by thread: Re: Active Directory
- Next by thread: Re: Active Directory
- Index(es):
Relevant Pages
|
Loading