Re: SCCM Client Push Fails
- From: Scott Wom <ScottWom@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 30 Nov 2009 14:51:01 -0800
Both Client and Server have the subnet set as 255.255.255.252. I didn't
build the network. I spoke with our Network Engineer and he says he plans on
resolving that some day. Never the less the client and server communicate
fine. (excluding wmi of course).
When I use WBEMTEST from Server to \\ <IP> \root\cimv2 I get the error :
---------------------------------------------------
Number: 0x800706ba
Facility: Win32
Description: The RPC server is unavailable.
RPC service is running on client w/o issue. DCOM permissions ok. F/W off
for the time being. I can even connect to client's wmi from another client
w/o issues. Its somehow just has a problem connecting from SCCM server to
the clients.
--------------------------------------------------
Results of previously requested tests: I replaced actual host name and IPs.
C:\Windows\system32>ping clienthostname
Pinging clienthostname.domain.com [x.x.x.x] with 32 bytes of data:
Reply from x.x.x.x: bytes=32 time=8ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Ping statistics for x.x.x.x:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 8ms, Average = 2ms
C:\Windows\system32>ping -a x.x.x.x
Pinging clienthostname.domain.com [x.x.x.x] with 32 bytes of data:
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time<1ms TTL=128
Reply from x.x.x.x: bytes=32 time=2ms TTL=128
Ping statistics for x.x.x.x:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms
C:\Windows\system32>nbtstat -a x.x.x.x
Local Area Connection:
Node IpAddress: [10.10.12.102] Scope Id: []
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------
clienthostname <00> UNIQUE Registered
clienthostname <20> UNIQUE Registered
domain <00> GROUP Registered
domain <1E> GROUP Registered
MAC Address = 00-xx-70-xx-04-xx
"Garth" wrote:
It not the correct IP address you are looking for, it is the correct.
NetBIOS Name.
/22 subnet is huge! Why using such a large subnet? Are the clients
really using /22 subnet mask or are they using a /24 or smaller subnet
mask? If the subnet mask is not correct, you will have problems
installing the client.
"Scott Wom" <ScottWom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:56CDDF3E-1732-42DA-866E-933C9769FAD8@xxxxxxxxxxxxx:
One more thing, Oddly enough I can connect to WS from another WS using
\\WSName\root\cimv2, just not from any servers (including the new SCCM
server). Our servers are on a differnet subnet than the clients, maybe thats
the isssue?? No FW between subnets, they are all under the same x.x.x.x/22
class B. SMS had no issues with this...
"Scott Wom" wrote:
Thanks for your response Garth. I don't think its DNS though. All the ping
tests/nbtstat -a test comes back with correct IP and sucessfull response.
However running wbemtest connect to \\<IP>\root\cimv2 I get
Number: 0x800706ba
Facility: Win32
Description: The RPC server is unavailable.
I verified RPC service on WS is running as well as DCOM.
RPC
Scott
"Garth" wrote:
It sounds like a DNS/WINS problem:
.. Pick a WS that is having problem.
.. Ping he WS by name, note the IP address
.. Take that IP address and ping -a <IP>, is the name the same as
above?
.. Do an nbtstat -a <IP>, do you see the computer name in the
list?
.. Using wbemtest connect to \\<IP>\root\cimv2
<file:///\\%3cIP%3e\root\cimv2> Then review the results for
win32_ComputerSystem, is the name what you expect?
If any of these three tests don't show you the PC name that you are
expecting then your issue is with DNS/WINS.
"scott.womersley@xxxxxxxxxxxx" <scott.womersley@xxxxxxxxxxxx> wrote in
message news:#RVZD#VbKHA.5728@xxxxxxxxxxxxxxxxxxxx:
Dear group,
I have a SMS environment side by side with a new SCCM environment and I can
not get the client push to work on most of my workstations after migrating
to SCCM. Oddly enough its random. Discover works fine assigns a site code
Client push account is smsremote and is a domain admin. I log in with the
smsremote account and have no problems accessing the admin$. I know
00000005 is typically a access is denied but that just cant be the case.
(of course unless i missed something) Domain admin all around.
When trying to remote WMI to the client from the SCCM server it fails
(Although I can connect to that client's wmi remotely from another client,
just not from any server including the SCCM server). "Failed to connect to
\\client because "Win32 The RPC Server is unavailable" and posts a Event iD
10009 in the event viewer. "DCOM was unable to communicate with the
computer clientname using any of the configured protocols." Verified DCOM
permissions has local administrators (which includes domain admins) with
remote access even gave "everyone" rights to no avail. .
Verified local WMI Security includes Local Administrators.
Firewall on Server and Client are turnned off for the time being.
Tried portqry -n clientname -e 135 and receive a "RPC query failed (6bf)"
error
SCCM server - Windows 2008/Sql 2008 backend
Client - XP Pro SP3
Nothing gets posted to C:\WINDOWS\system32\ccmsetup on the client.
Exert from ccm.log:
======>Begin Processing request: "clientcomputername_domain_COM.domain",
machine name: "clientcomputername" SMS_CLIENT_CONFIG_MANAGER 11/24/2009
5:24:15 AM 5684 (0x1634)
---> Trying the account stored in the CCR (index = 0x0)
SMS_CLIENT_CONFIG_MANAGER 11/24/2009 5:24:15 AM 5684 (0x1634)
---> Attempting to connect to administrative share
'\\clientcomputername.domain.com\admin$' using account 'domain\smsremote'
SMS_CLIENT_CONFIG_MANAGER 11/24/2009 5:24:15 AM 5684 (0x1634)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account
domain\smsremote (00000005) SMS_CLIENT_CONFIG_MANAGER 11/24/2009 5:24:16 AM
5684 (0x1634)
---> Connected to administrative share on machine
clientcomputername.domain.com using account 'domain\smsremote'
SMS_CLIENT_CONFIG_MANAGER 11/24/2009 5:24:16 AM 5684 (0x1634)
---> Attempting to make IPC connection to share
<\\clientcomputername.domain.com\IPC$> SMS_CLIENT_CONFIG_MANAGER 11/24/2009
5:24:16 AM 5684 (0x1634)
---> Searching for SMSClientInstall.* under
'\\clientcomputername.domain.com\admin$\' SMS_CLIENT_CONFIG_MANAGER
11/24/2009 5:24:16 AM 5684 (0x1634)
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706ba
SMS_CLIENT_CONFIG_MANAGER 11/24/2009 5:24:32 AM 6124 (0x17EC)
---> Unable to connect to WMI on remote machine "clientcomputer2", error =
0x800706ba. SMS_CLIENT_CONFIG_MANAGER 11/24/2009 5:24:32 AM 6124 (0x17EC)
---> Deleting SMS Client Install Lock File
'\\clientcomputer2.domain.com\admin$\SMSClientInstall.00A'
SMS_CLIENT_CONFIG_MANAGER 11/24/2009 5:24:32 AM 6124 (0x17EC)
Stored request "clientcomputer2_ESI1_EVOLVING_COM", machine name
"clientcomputer2", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 11/24/2009
5:24:32 AM 6124 (0x17EC)
<======End request: "clientcomputer2_ESI1_EVOLVING_COM", machine name:
"clientcomputer2". SMS_CLIENT_CONFIG_MANAGER 11/24/2009 5:24:32 AM 6124
(0x17EC)
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706ba
SMS_CLIENT_CONFIG_MANAGER 11/24/2009 5:24:37 AM 5684 (0x1634)
---> Unable to connect to WMI on remote machine "clientcomputername", error
= 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 11/24/2009 5:24:37 AM 5684 (0x1634)
---> Deleting SMS Client Install Lock File
'\\clientcomputername.domain.com\admin$\SMSClientInstall.00A'
SMS_CLIENT_CONFIG_MANAGER 11/24/2009 5:24:37 AM 5684 (0x1634)
Stored request "clientcomputername_domain_COM.domain", machine name
"clientcomputername", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 11/24/2009
5:24:37 AM 5684 (0x1634)
<======End request: "clientcomputername_domain_COM.domain", machine name:
"clientcomputername". SMS_CLIENT_CONFIG_MANAGER 11/24/2009 5:24:37 AM 5684
(0x1634)
thanks for your help!
Scott
--
Garth Jones
Chief Architect
www.Enhansoft.com
Enhancing Your Business
.
--
Garth Jones
Chief Architect
www.Enhansoft.com
Enhancing Your Business
.
- Follow-Ups:
- Re: SCCM Client Push Fails
- From: Garth
- Re: SCCM Client Push Fails
- Next by Date: Re: SCCM Client Push Fails
- Next by thread: Re: SCCM Client Push Fails
- Index(es):
Relevant Pages
|
