Client can't ping the WSUS server

Qasim Afzal 101 Reputation points

Domain Environment:
1 Domain: Qasim.local
2 Sites: Vancouver& Provost

3 Clients

2 Clients in Vancouver

1 Clients in provost

diagram in environment:

Note: clients not added
User's image

WSUS Servers are deployed for updates to push to clients / Computers etc.

The client in provost can't ping the wsus server that is set in provost

User's image

User's image

the wsus server set in provost is there to use it as updates in provost clients computer.
I checked the firewall their configured.

I have DHCP set in the site 1 and site 2 however my dhcp for site 2 doesn't work. Hence, my client that is in provost is set to static ip:
Using a vyos router vm for the network connection.

All on VMs, like DC's in site 1 is server 2019 so on so forth.

I have setup GPO to apply automatic update but only target to the provost pc (site 2).

DNS is running and DHCP.

Not sure what is wrong. As mentioned spend hours to troubleshoot.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,432 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,030 questions
0 comments No comments
{count} votes

Accepted answer
  1. Dave Patrick 426K Reputation points MVP

    I'd check that all members got the domain firewall profile. Try to ping the gateway, try to tracert to see where the connection is dropped. An unedited ipconfig /all of problem member, domain controller and the WSUS might help.


    --please don't forget to upvote and Accept as answer if the reply is helpful--

2 additional answers

Sort by: Most helpful
  1. Limitless Technology 43,916 Reputation points

    Hi. Thank you for your question and reaching out. I’d be more than happy to help you with your query

    I have linked an article below that may help solve your issue. Here is what the article has to say:

    If the WSUS server is unreachable from the client, the most likely causes include: There's a name resolution issue on the client. There's a network-related issue, such as a proxy configuration issue.

    Use standard troubleshooting procedures to verify name resolution is working on the network. If name resolution is working, the next step is to check for proxy issues. Check windowsupdate.log (C:\windows) to see if there are any proxy related errors. You can run the proxycfg command to check the WinHTTP proxy settings.

    If there are proxy errors, go to Internet Explorer > Tools > Connections > LAN Settings, configure the correct proxy, and then make sure you can access the WSUS URL specified.

    Once done, you can copy these user proxy settings to the WinHTTP proxy settings by using the proxycfg -u command. After the proxy settings are specified, run wuauclt /detectnow from a Command Prompt and check windowsupdate.log


    If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.

    0 comments No comments

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more