<div>
Is this websphere application server standalone Server?<br />
<br />
You have DMZ between WAS and LDAP?<br />
<br />
if so first you need to make sure open LDAP ports in network default port is 389 for non-ssl and 636 for ssl
</div>


Is this websphere application server standalone Server?

You have DMZ between WAS and LDAP?

if so first you need to make sure open LDAP ports in network default port is 389 for non-ssl and 636 for ssl

<div>
No it is not a websphere application server. &nbsp; &nbsp; It is currently a domain controller, but I do not want to have a DC on the DMZ and was reading that it should be a standalone server with LDAP authentication. &nbsp; I do not much experience in this area and wanted to obtain procedures on how to go about setting up server. &nbsp; &nbsp;Currently have 3 other servers on DMZ that is using AD on this DC to authenticate. &nbsp;Any help is greatly appreciated :)
</div>


No it is not a websphere application server.     It is currently a domain controller, but I do not want to have a DC on the DMZ and was reading that it should be a standalone server with LDAP authentication.   I do not much experience in this area and wanted to obtain procedures on how to go about setting up server.    Currently have 3 other servers on DMZ that is using AD on this DC to authenticate.  Any help is greatly appreciated :)

<div>
It would be helpful to a clearer picture of what you're trying to accomplish and why all these servers in the dmz that are part of the AD
</div>


It would be helpful to a clearer picture of what you're trying to accomplish and why all these servers in the dmz that are part of the AD

<div>
<div class="content wysiwyg-content">
How do I set up a DMZ Standalone Server with AD Authentication via LDAP?
</div>
</div>


How do I set up a DMZ Standalone Server with AD Authentication via LDAP?

DMZ Standalone Server using LDAP Authentication

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.

Networking Protocols

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.