Using Connection tester

[TWC]

I typed in the PC's name and got this result

Ping test OK
-----------------------------------------------
Remote registry test OK
-----------------------------------------------
Remote WMI access test FAILED
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
-----------------------------------------------
Remote \\titus-04\c$ access test OK

Used its IP and got this result

Ping test OK
-----------------------------------------------
Remote registry test FAILED
The network path was not found.

-----------------------------------------------
Remote WMI access test FAILED
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
-----------------------------------------------
Remote \\10.0.0.24\c$ access test FAILED

I have just started using lansweeper, any ideas as to what my problem might be.

[TWC]

I have checked everything that has been suggersted above and nothing made a difference.

What did work however if running a windows repair on it, all problems now gone.

Its a bit more work but problem is solved.
🙂

[bulldog]

Of course...many thanks.

[Hemoco]

Just right click on the connection tester and choose "runas"

[bulldog]

Slightly unrelated, but not really. Is it possible to change the account that Connection Tester runs using? If I'm logged on to the server as Administrator it will run with that account, whereas, I really need the connection to be tested with the account name that the service runs as. If not possible with the current version (short of logging on as the lansweeper service account and THEN running it), could I suggest this for inclusion in the next version of Connection Tester? Cheers.

[Hemoco]

To compare WMI security.
start/run/dcomcnfg
Component services/computers/right click "my computer"/properties
Check the default properties and com+ security.


Open dcom config/right click "windows management and instrumentation"

[Hemoco]

No, the problem is related to access permissions on the client.
The remote registry works so the problem is only the WMI security.

[TWC]

Both machines have DCOM started and "Windows Management Instrumentation" service is set to automatic and started.

we are installing Service Pack 3 on titus-5 as a test.

Any Other ideas??

[TWC]

Just spotted something.
titus-04 is the one with the problem, and it has service pack 3
titus-05 works fine and is running service pack 2

Could that be the problem?

[Hemoco]

In the windows services make sure that the "Windows Management Instrumentation" service is set to automatic and started.
Make sure that dcom is enabled on the computer.