DNS is solid. I can ping IP and hostname on the server and from a remote machine on the network. I'm not using a domain controller at the present moment.
The WSUS server is a virtual machine running Windows Server 2012R2. I'm remote desktop'd into it, but that shouldn't matter. I've tried it on the console just the same, still no luck.
Does anyone have any other information they would need from me for more troubleshooting, or anything else I should try. This seems like a solid solution to pushing out 3rd party updates via WSUS. I really don't want to find another solution (if there is even one) and our old solution LUP no longer works since we've upgraded to WS2012R2.
Additionally, I can connect with port 8530, No SSL and Not Local. It just gives me the warning, "You don't have any certificat." You will not be able to publish updates." Which, you know, kills the whole reason for me using this product.
The WSUS server is a virtual machine running Windows Server 2012R2. I'm remote desktop'd into it, but that shouldn't matter. I've tried it on the console just the same, still no luck.
Does anyone have any other information they would need from me for more troubleshooting, or anything else I should try. This seems like a solid solution to pushing out 3rd party updates via WSUS. I really don't want to find another solution (if there is even one) and our old solution LUP no longer works since we've upgraded to WS2012R2.
Additionally, I can connect with port 8530, No SSL and Not Local. It just gives me the warning, "You don't have any certificat." You will not be able to publish updates." Which, you know, kills the whole reason for me using this product.
<WsusPackagePublisher>
<Server>
<Name>WSUSSERVERNAME</Name>
<IsLocal>False</IsLocal>
<Port>8530</Port>
<UseSSL>False</UseSSL>
<IgnoreCertErrors>False</IgnoreCertErrors>
<DeadLineDaysSpan>0</DeadLineDaysSpan>
<DeadLineHour>0</DeadLineHour>
<DeadLineMinute>0</DeadLineMinute>
<VisibleInWsusConsole>Never</VisibleInWsusConsole>
</Server>
</WsusPackagePublisher>