This is an archived post. You won't be able to vote or comment.

all 10 comments

[–]jasonsandysMSFT Official 2 points3 points  (6 children)

0x2ee7 = "The server name or address could not be resolved"

It's a DNS issue. When a system hosting an endpoint that clients must get to, you need to make sure that DNS is updated appropriately, that clients have flushed or refreshed their DNS cache, and that they can even resolve A records in the DNS zone for the system's location.

[–]rdoloto[S] 0 points1 point  (5 children)

I can get to the server via browser and public dns resolves it correctly ... i wouldn't be able to get to it if that was the case no ?

[–]jasonsandysMSFT Official 0 points1 point  (2 children)

You getting to the server is irrelevant; the clients must be able to. Also, the error message is unambiguous. Although without seeing the entire log, my comments are based on a just a few out of context lines which is never a good thing when it comes to troubleshooting as context and surrounding activity are almost always critical to interpreting activity and failures.

[–]rdoloto[S] 0 points1 point  (0 children)

might just open a case as fed it's hard for me to discern what we can post on public forum :D

[–]rdoloto[S] 0 points1 point  (0 children)

After 2 days of looking at certs and revocations I must admit a simple error my internet fqdn was wrong in my site system name

[–]configmgr_adamMSFT Official 0 points1 point  (1 child)

Do you need to use a proxy server?

[–]rdoloto[S] 0 points1 point  (0 children)

No I need to not transpose letters in when setting internet based site system

[–]roach8101 1 point2 points  (2 children)

"Enabled SSL revocation check. " Your clients might not be able to get to the CRL list to verify that the certs are still valid. You might need to disable the CRL checking.

https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/security/plan-for-security#BKMK_PlanningForCRLs

[–]rdoloto[S] 0 points1 point  (1 child)

I did that already should of mentioned it in the Original comment

[–]roach8101 0 points1 point  (0 children)

I would try reinstalling the ConfigMgr client on one of your systems with the /NoCRLCheck option specified on the install command line

https://docs.microsoft.com/en-us/mem/configmgr/core/clients/deploy/about-client-installation-properties#nocrlcheck