As I understand it, LDAP Ping is more of a handshake test - not an open
port check.
--
Espi
On Thu, Nov 3, 2016 at 2:56 PM, Christopher Bodnar <
christopher_bod...@glic.com> wrote:
> I understand the function of an LDAP Ping over UDP/389 in the DC Locator
> process, but shouldn’t that respond
I understand the function of an LDAP Ping over UDP/389 in the DC Locator
process, but shouldn't that respond to a Portqry? When I test this I receive
the following:
UDP port 389 (unknown service): LISTENING or FILTERED
I've tested this in 3 separate forests against multiple domain controllers
Thanks, I have seen that. But no, it doesn't, unfortunately. Not for me, anyway.
On Thu, Nov 3, 2016 at 11:51 AM, Sean Martin wrote:
> I don't have any experience setting up a SQL cluster in vSphere, but it
> appears this article may answer most of your questions:
>
>
Sorry for the OT, but I haven't received any answers on the VMware forums.
I need to set a 2 node Win2008 R2/SQL 2008 R2 cluster on ESXi 5.5 U3b.
This will be only for testing; I have a production cluster on 2
physical nodes already, but what I need to do is test making some
changes to the
4 matches
Mail list logo