How to check DC&RODC authentication issues

By default, client will contact the DC in same site. And the site is configured in “AD sites and services”. We can simulate the DC locator process and gather network monitor package to see what happens during finding DC. Following is action plan:

Download Network Monitor 3.3 and install it on client (by default path)
http://www.microsoft.com/downloads/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en

Nltest.exe is a command tool in “support tools”. Please download support tool from:
http://www.microsoft.com/downloads/details.aspx?FamilyID=6ec50b78-8be1-4e81-b3be-4e7ac4f0912d&DisplayLang=en.

On client, open a command prompt and run following command to start Network Monitor:
"%ProgramFiles%\Microsoft Network Monitor 3\nmcap" /network * /capture /file %ComputerName%_test.cap:50M /DisableConversations /DisableLocalOnly

On client, open another command prompt, navigate the path in which nltest.ext resides, run following command:
ipconfig /flushdns
nltest /dsgetdc:domainname /force > dsgetdc.txt
nltest /dsgetsite > dsgetsite.txt
set l > setl.txt
NOTE:please place the “domainname” with your real domain name
In the command prompt of step 3, click “CTRL+C” to stop network monitor. The log is at current path.

Find the dsgetdc.txt ,dsgetsite.txt and setl.txt result s in same place

How to Enable ADFS Change Password Portal without Workplace Join

This summary is not available. Please click here to view the post.

Vmware – Cannot ping NLB IP from Different Subnet

Symptoms:-

You can ping all the NLB Host from any subnet but NLB IP cannot ping Different subnet (in same subnet you can ping all the IP including NLB IP)

Check MAC address, for sure you can see different MAC Address for each

How to get MAC Address

Log in different machine which is connected same subnet and ping all three IPs (Host 1 and Host 2 and NLB IP). You can ping all the IP’s without any issue.

After that you can run in same command prompt “ arp –a” (result are below)

How to fix it

Remove all existing NLB configuration

Create New NLB connection in Node 01, with multicasting and Add Node 02

Run        netsh interface ipv4 set interface "NLB" forwarding=enabled

Login Node 02 Server and Add existing NLB Connection (with NLB IP)

Run        netsh interface ipv4 set interface "NLB" forwarding=enabled