Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, August 31, 2016 12:22 AM
Hello,
I am having issues connecting using the remote sccm console inside of SMSAdminUI.log I see the following error:
[4, PID:8372][08/29/2016 16:52:33] :Transport error; failed to connect, message: 'The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.SmsConnectionException\r\nThe RPC server is unavailable. (Exception from HRESULT: 0x800706BA)\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)
I am able to connect successfully using the remote console from the same subnet as the sccm server. The console attempts from outside subnets are failing to connect. I have verified the firewall is disabled between connection points and I am able to see traffic going between the sccm server and tcp 135 also some dynamic tcp traffic is being allowed. I have also verified user account permissions are in place to allow connectivity. Any assistance troubleshooting this would be appreciated I am at a loss as to why these clients are failing to connect.
All replies (13)
Wednesday, August 31, 2016 6:44 PM âś…Answered
The issue turned out to be firewall related with outbound traffic inspection blocking some of the communication.
Wednesday, August 31, 2016 2:16 AM
Can you remotely connect to WMI on the site server from the affected subnet? There are many ways to verify, this is my favorite. This will find all your Freds. Replace PS1 with your sitecode.
Get-WmiObject -query "Select * from SMS_R_USER where name like '%fred%'" -Namespace "Root\SMS\Site_PS1" -ComputerName siteserver.domain.local
Fred Bainbridge | President, MNSCUG | Systems Consultant, Now Micro | fredbainbridge.com
Wednesday, August 31, 2016 2:29 AM
This command fails if I used the FQDN of the site server. If I use the ip of the server or a different DNS suffix it works. The FQDN does resolve to the correct ip however.
Wednesday, August 31, 2016 2:59 AM
You have found your problem! You must be able to resolve the site server via FQDN. Happy hunting.
Fred Bainbridge | President, MNSCUG | Systems Consultant, Now Micro | fredbainbridge.com
Wednesday, August 31, 2016 3:43 AM
Thank you but the FQDN is resolvable. I am able to ping the server with the FQDN. The console still will not connect. I do not suspect this is a DNS issue.
Wednesday, August 31, 2016 12:27 PM
Have you looked at the firewall? Have you disabled it for a few minutes and tried again?
Garth Jones
Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx
Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased
Wednesday, August 31, 2016 12:35 PM
Ok, if you dont think its DNS it's definitely the fact you can't connect via WMI to the FQDN of the site server. (which sounds like DNS) Resolve your WMI Connectivity issue and your console should start working.
Can you connect via WMI to other resources in that subnet?
Troubleshoot this one with some efficacy and you will find your problem. It is almost certainly not related to ConfigMgr.
-Fred
Fred Bainbridge | President, MNSCUG | Systems Consultant, Now Micro | fredbainbridge.com
Wednesday, August 31, 2016 3:04 PM
Yes I have disabled the firewall and the connection issue persists.
Wednesday, August 31, 2016 4:59 PM
Should I able able to connect to the console using ip to eliminate any dns issues or do I have to use FQDN?
Wednesday, August 31, 2016 5:47 PM
Should I able able to connect to the console using ip to eliminate any dns issues or do I have to use FQDN?
If you used the PoSH command, you can used IP address instead of FQDN.
Garth Jones
Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx
Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased
Wednesday, August 31, 2016 5:52 PM
From the ConfigMgr Console you can go to the little drop down menu in the upper left and select "Connect to another site" you can specify an IP address there and test...
but who cares? fix the problem, don't bandage it. If you can connect by IP but not FQDN you have bigger problems you need to address or you may forever have a really crappy configmgr (and probably lots of other things) experience.
-Fred
Fred Bainbridge | President, MNSCUG | Systems Consultant, Now Micro | fredbainbridge.com
Thursday, September 27, 2018 3:38 PM
How did you resolve? I assume you opened some ports but what ports?
Thomas Faherty
Thursday, September 27, 2018 7:22 PM
have you seen the network port doc for CM12?
https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/ports
Garth Jones
Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/
Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed