Ask a questionAsk a question
 

AnswerWMI issues

  • Wednesday, October 28, 2009 7:45 AMMicrosoft Gal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I tried to install sccm client using the sccm console. I got the error of "RPC Server is unavailable".

    I tried to use wbemtest to test the WMI connection using hostname of the client, I also got the same error. But when I tried to use IP address of the client instead of the hostname on wbemtest testing, I manage to connect to its root\cimv2. I tried to ping the hostname of the client, it manage to resolve the name and display the IP address.

    What is the problem?

Answers

All Replies

  • Wednesday, October 28, 2009 7:59 AMTorsten [MVP]MVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Is the name resolved to the exact same IP address in that case?
  • Wednesday, October 28, 2009 8:00 AMMicrosoft Gal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Yes, from the ping reply, it's the exact same IP address.
  • Wednesday, October 28, 2009 10:33 AMJie-Feng Ren - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Also, is firewall turned on on SCCM client?


    Jie-Feng Ren - MSFT
  • Wednesday, October 28, 2009 10:40 AMMicrosoft Gal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,

    Yes, I turn on windows firewall on sccm client, but it still able to connect via WBEMTEST using IP address. I just dont understand why hostname couldnt as it manages to resolve the computer name.
  • Wednesday, October 28, 2009 1:52 PMGarth JonesMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    BTW, a reply from a ping does not mean that it resolved the name to the correct IP.

     

    Try this… from a CMD

    nbtstat –a <IP Address>


    Are you getting the PC name that you are expecting? If not then you have an DNS/WINS issue.


    http://www.enhansoft.com/
  • Thursday, October 29, 2009 12:33 PMMicrosoft Gal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,

    Now I use hostname/IP address via wbemtest without all the firewall, it cannot connect to those clients in different segment with SCCM Server. What is the problem? Any troubleshooting steps I could do?
  • Thursday, October 29, 2009 1:44 PMTorsten [MVP]MVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    That's not a ConfigMgr problem ... it's OS or even network related. Any (hardware) firewalls between those segments? You could use NetMon to see if the request makes it to the destination client.

  • Wednesday, November 04, 2009 3:17 AMNick P. - Capgemini Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sounds like a name resolution issue.

    When you RDP onto the machine (by IP address), and you pull down the 3rd box ("Log on to:"), does the correct machine name show up in the list (what shows up as "this computer")?

    If you PING MACHINENAME and PING MACHINENAME.CONTOSO.COM, do you get the same address back?

    Nick.
  • Wednesday, November 04, 2009 6:59 AMReddy Surendar Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    It looks like a DNS issues, initiate ipconfig /flushdns on client machine and wait for 30 mins to check it again. if still you have issues contact your DNS and Network administrators.
    Surendar Reddy
  • Wednesday, November 04, 2009 7:50 AMTorsten [MVP]MVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    No, it's not a DNS issue, because he wrote "Now I use hostname/IP address via wbemtest without all the firewall" ... so no DNS involved in that case.
  • Wednesday, November 04, 2009 8:38 AMMicrosoft Gal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi,

    Thank you very much on these replies. I got it solve after the network guy uncheck "enforce strict RPC compliance" on firewall.
  • Thursday, November 05, 2009 5:28 PMNick P. - Capgemini Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    The symptoms changed part way thru this thread.

    Oct. 28: "I tried to use wbemtest to test the WMI connection using hostname of the client, I also got the same error. But when I tried to use IP address of the client instead of the hostname on wbemtest testing, I manage to connect to its root\cimv2"

    Oct. 29: "Now I use hostname/IP address via wbemtest without all the firewall, it cannot connect to those clients in different segment with SCCM Server"

    The Oct. 28 issue looks like a name resolution issue.  The Oct. 29 issue looks like a firewall issue.

    Anyway, glad to hear that your problem(s) has/have cleared.

    Nick.