The RPC server is unavailable 0x800706BA

[Babbabooey]

I have an issue with a HP T5730 thin client not being scanned by LanSweeper..

The error is -

The RPC server is unavailable 0x800706BA (hp-1ib7uaowvag1.<mydomain.co.uk>, HP-1IB7UAOWVAG1, <10.1.5.120>)


Using the connection tester I get


DNS test
-----------------------------------------------
Is this the correct remote IP: 10.1.5.120
If not, please check for DNS problems

\root\cimv2 Remote WMI access test FAILED
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

Remote WMI test
-----------------------------------------------
\root\cimv2 Remote WMI access test FAILED
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

Remote Registry test using WMI
-----------------------------------------------
\root\default Remote WMI access test FAILED
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

I have installed the WMI add on from HP, and I can remotely control the machine.

DNS is all correct, and the windows firewall service is disabled, and no other firewall software is present.

Any other ideas?

[Babbabooey]

Sorted!

When I created a fresh build from the image direct from HP and started using it in the deployment console, the names were different comared to the bios, and even when i manually changed the name to match it must have somehow not changed it everywhere.

The solution - while doing the fresh build image from USB stick, delete the old computer from the deployment console, and then when the image build is complete it will populate with a new unique name. Then add the WMI support add on as usual and all works fine.

[Hemoco]

We recommend trying to scan the client with the LsPush agent. More info on LsPush can be found on page 32 of our online documentation.
If the LsPush scan succeeds, WMI is set up correctly.

[rgross]

here is another WMI script I have used in the past, see if this works any better for you:


@echo on
cd /d c:\temp
cd /d %windir%\system32\wbem
net stop winmgmt
winmgmt /kill
if exist Rep_bak rd Rep_bak /s /q
rename Repository Rep_bak
net start winmgmt
goto End

:End

[Babbabooey]

No AV or firewall installed 😞

[rgross]

Make sure your AV is disabled when trying to repair WMI, we use trend and our server prevents WMIMGMT from being stopped so I always have to get the server guys to to allow me to stop that service before it will work.

[Babbabooey]

Thanks for the above, i'd already come across it and it didn't help unfortunately.

It does seem to be WMI related though, as the diag tool complains about a few registry errors.

[rgross]

I have come across computers where the WMI is corrupt. I use this script on the local machine to repair WMI:


@ECHO OFF

NET STOP SharedAccess

NET STOP winmgmt

CD %WINDIR%\System32\Wbem\Repository
DEL /F /Q /S %WINDIR%\System32\Wbem\Repository\*.*
CD %WINDIR%\system32\wbem

REGSVR32 /s %WINDIR%\system32\scecli.dll
REGSVR32 /s %WINDIR%\system32\userenv.dll

MOFCOMP cimwin32.mof
MOFCOMP cimwin32.mfl
MOFCOMP rsop.mof
MOFCOMP rsop.mfl
FOR /f %%s IN ('DIR /b /s *.dll') DO REGSVR32 /s %%s
FOR /f %%s IN ('DIR /b *.mof') DO MOFCOMP %%s
FOR /f %%s IN ('DIR /b *.mfl') DO MOFCOMP %%s
MOFCOMP exwmi.mof
MOFCOMP -n:root\cimv2\applications\exchange wbemcons.mof
MOFCOMP -n:root\cimv2\applications\exchange smtpcons.mof
MOFCOMP exmgmt.mof

rundll32 wbemupgd, UpgradeRepository


NET STOP Cryptsvc
DEL /F /Q /S %WINDIR%\System32\catroot2\*.*
DEL /F /Q C:\WINDOWS\security\logs\*.log
NET START Cryptsvc


msiexec /unregister
msiexec /regserver
REGSVR32 /s msi.dll

NET START winmgmt
NET START SharedAccess