Jul 01 2022 01:09 AM
Jul 01 2022 01:09 AM
We have a Windows 2016 AD deployed in our organization which I cannot ping or do a Remote Desktop into from my machine which is on the same local network as the server. Sometimes if I do a tracert and then it starts pinging and I am able to remote into it. Otherwise it just doesn't ping/connect at all. I have another server to which I can remote and then through this server I can ping/RD to the AD fine. I have checked firewall settings/changed my IP/enabled network sharing etc. but nothing seems to work. Not sure what I am missing out. This problem just started all of a sudden sometime back, before it was working fine.
Jul 01 2022 07:49 AM
I'd start by checking that the domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS
Jul 01 2022 08:27 AM
@Dave Patrick Tried, The static IP of DC as the only DNS entry for both the server and the client computer. Didn't work.
Jul 01 2022 08:33 AM
Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt
ipconfig /all > C:\dc3.txt
ipconfig /all > C:\problemworkstation.txt
then put `unzipped` text files up on OneDrive and share a link.
Jul 14 2022 04:45 AM
Hello Zubair null,
I hope you are doing well!
The problem may occur because an earlier software installation on the server has left the computer in a pending state, and restarting the computer does not clear the state.
You should try restarting your server to fix the problem. If the restart option does not fix the issue, follow the steps below to resolve it.
Click on the Download button. Then, under the File Download dialog box, click Run and follow the steps in the easy fix wizard.
Change your firewall settings:
You must close the window and try connecting again. If the firewall was only the problem, you should be able to connect to the remote computer now.
I hope your problem may resolve with the above-given fixes.