Remote WMI access test FAILED Out of idea's

[Alientje]

Hey, I get the following error when i use Connection Tester tool on only 1 computer (this is a windows xp sp3). Im not sure yet what it's running but it's not used as normal workstation but running some services. Im a bit new to the company (3 weeks) and im working here for my training period of College.

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

This is the only computer im not getting to work with lansweeper, the rest worked fine after doing some adjustments to firewall etc.
I have checked the following solved topic tho there was no real solution there only that you at the end did a remote connection.
http://www.lansweeper.com/forum/yaf_postst1140p2_Picking-up-but-not-scanning.aspx

What i have done/checked:
- Ping <ip> and ping -a <ip>
- Checked Dcomcnfg
- Connection tester gives at all 3 tests (ip fqdn and hostname) the same error as show above.
- The WMI service is running

WMIDIAG:
20337 09:51:25 (0) ** WMIDiag v2.0 started on Thursday, March 05, 2009 at 09:45.
20338 09:51:25 (0) **
20339 09:51:25 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
20340 09:51:25 (0) **
20341 09:51:25 (0) ** This script is not supported under any Microsoft standard support program or service.
20342 09:51:25 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
20343 09:51:25 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
20344 09:51:25 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
20345 09:51:25 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
20346 09:51:25 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
20347 09:51:25 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
20348 09:51:25 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
20349 09:51:25 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
20350 09:51:25 (0) ** of the possibility of such damages.
20351 09:51:25 (0) **
20352 09:51:25 (0) **
20353 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20354 09:51:25 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
20355 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20356 09:51:25 (0) **
20357 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20358 09:51:25 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'EUROSCAN\ADMINISTRATOR' on computer 'WKS-NL-11'.
20359 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20360 09:51:25 (0) ** Environment: ........................................................................................................ OK..
20361 09:51:25 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #0).
20362 09:51:25 (0) ** Drive type: ......................................................................................................... IDE (ST380011A).
20363 09:51:25 (0) ** There are no missing WMI system files: .............................................................................. OK.
20364 09:51:25 (0) ** There are no missing WMI repository files: .......................................................................... OK.
20365 09:51:25 (0) ** WMI repository state: ............................................................................................... N/A.
20366 09:51:25 (0) ** BEFORE running WMIDiag:
20367 09:51:25 (0) ** The WMI repository has a size of: ................................................................................... 8 MB.
20368 09:51:25 (0) ** - Disk free space on 'C:': .......................................................................................... 67911 MB.
20369 09:51:25 (0) ** - INDEX.BTR, 1351680 bytes, 3/4/2009 11:20:16 PM
20370 09:51:25 (0) ** - INDEX.MAP, 700 bytes, 3/4/2009 11:20:16 PM
20371 09:51:25 (0) ** - OBJECTS.DATA, 6971392 bytes, 3/4/2009 11:20:16 PM
20372 09:51:25 (0) ** - OBJECTS.MAP, 3456 bytes, 3/4/2009 11:20:16 PM
20373 09:51:25 (0) ** AFTER running WMIDiag:
20374 09:51:25 (0) ** The WMI repository has a size of: ................................................................................... 8 MB.
20375 09:51:25 (0) ** - Disk free space on 'C:': .......................................................................................... 67909 MB.
20376 09:51:25 (0) ** - INDEX.BTR, 1351680 bytes, 3/5/2009 9:46:32 AM
20377 09:51:25 (0) ** - INDEX.MAP, 700 bytes, 3/5/2009 9:46:32 AM
20378 09:51:25 (0) ** - OBJECTS.DATA, 6971392 bytes, 3/5/2009 9:46:32 AM
20379 09:51:25 (0) ** - OBJECTS.MAP, 3456 bytes, 3/5/2009 9:46:32 AM
20380 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20381 09:51:25 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
20382 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20383 09:51:25 (0) ** DCOM Status: ........................................................................................................ OK.
20384 09:51:25 (0) ** WMI registry setup: ................................................................................................. OK.
20385 09:51:25 (0) ** WMI Service has no dependents: ...................................................................................... OK.
20386 09:51:25 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
20387 09:51:25 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
20388 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20389 09:51:25 (0) ** WMI service DCOM setup: ............................................................................................. OK.
20390 09:51:25 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
20391 09:51:25 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
20392 09:51:25 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
20393 09:51:25 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
20394 09:51:25 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
20395 09:51:25 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
20396 09:51:25 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
20397 09:51:25 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
20398 09:51:25 (0) ** fail depending on the operation requested.
20399 09:51:25 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
20400 09:51:25 (0) **
20401 09:51:25 (0) ** WMI ProgID registrations: ........................................................................................... OK.
20402 09:51:25 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
20403 09:51:25 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
20404 09:51:25 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
20405 09:51:25 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
20406 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20407 09:51:25 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
20408 09:51:25 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
20409 09:51:25 (0) ** - REMOVED ACE:
20410 09:51:25 (0) ** ACEType: &h0
20411 09:51:25 (0) ** ACCESS_ALLOWED_ACE_TYPE
20412 09:51:25 (0) ** ACEFlags: &h0
20413 09:51:25 (0) ** ACEMask: &h1
20414 09:51:25 (0) ** DCOM_RIGHT_EXECUTE
20415 09:51:25 (0) **
20416 09:51:25 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
20417 09:51:25 (0) ** Removing default security will cause some operations to fail!
20418 09:51:25 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
20419 09:51:25 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
20420 09:51:25 (0) **
20421 09:51:25 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
20422 09:51:25 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
20423 09:51:25 (0) ** - REMOVED ACE:
20424 09:51:25 (0) ** ACEType: &h0
20425 09:51:25 (0) ** ACCESS_ALLOWED_ACE_TYPE
20426 09:51:25 (0) ** ACEFlags: &h0
20427 09:51:25 (0) ** ACEMask: &h1
20428 09:51:25 (0) ** DCOM_RIGHT_EXECUTE
20429 09:51:25 (0) **
20430 09:51:25 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
20431 09:51:25 (0) ** Removing default security will cause some operations to fail!
20432 09:51:25 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
20433 09:51:25 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
20434 09:51:25 (0) **
20435 09:51:25 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
20436 09:51:25 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
20437 09:51:25 (0) ** - REMOVED ACE:
20438 09:51:25 (0) ** ACEType: &h0
20439 09:51:25 (0) ** ACCESS_ALLOWED_ACE_TYPE
20440 09:51:25 (0) ** ACEFlags: &h0
20441 09:51:25 (0) ** ACEMask: &h1
20442 09:51:25 (0) ** DCOM_RIGHT_EXECUTE
20443 09:51:25 (0) **
20444 09:51:25 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
20445 09:51:25 (0) ** Removing default security will cause some operations to fail!
20446 09:51:25 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
20447 09:51:25 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
20448 09:51:25 (0) **
20449 09:51:25 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
20450 09:51:25 (1) !! ERROR: Actual trustee 'NT AUTHORITY\NETWORK SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
20451 09:51:25 (0) ** - ACTUAL ACE:
20452 09:51:25 (0) ** ACEType: &h0
20453 09:51:25 (0) ** ACCESS_ALLOWED_ACE_TYPE
20454 09:51:25 (0) ** ACEFlags: &h2
20455 09:51:25 (0) ** CONTAINER_INHERIT_ACE
20456 09:51:25 (0) ** ACEMask: &h1
20457 09:51:25 (0) ** WBEM_ENABLE
20458 09:51:25 (0) ** - EXPECTED ACE:
20459 09:51:25 (0) ** ACEType: &h0
20460 09:51:25 (0) ** ACCESS_ALLOWED_ACE_TYPE
20461 09:51:25 (0) ** ACEFlags: &h12
20462 09:51:25 (0) ** CONTAINER_INHERIT_ACE
20463 09:51:25 (0) ** INHERITED_ACE
20464 09:51:25 (0) ** ACEMask: &h13
20465 09:51:25 (0) ** WBEM_ENABLE
20466 09:51:25 (0) ** WBEM_METHOD_EXECUTE
20467 09:51:25 (0) ** WBEM_WRITE_PROVIDER
20468 09:51:25 (0) **
20469 09:51:25 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
20470 09:51:25 (0) ** This will cause some operations to fail!
20471 09:51:25 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
20472 09:51:25 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
20473 09:51:25 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
20474 09:51:25 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
20475 09:51:25 (0) ** A specific WMI application can always require a security setup different
20476 09:51:25 (0) ** than the WMI security defaults.
20477 09:51:25 (0) **
20478 09:51:25 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
20479 09:51:25 (1) !! ERROR: Actual trustee 'NT AUTHORITY\LOCAL SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
20480 09:51:25 (0) ** - ACTUAL ACE:
20481 09:51:25 (0) ** ACEType: &h0
20482 09:51:25 (0) ** ACCESS_ALLOWED_ACE_TYPE
20483 09:51:25 (0) ** ACEFlags: &h2
20484 09:51:25 (0) ** CONTAINER_INHERIT_ACE
20485 09:51:25 (0) ** ACEMask: &h1
20486 09:51:25 (0) ** WBEM_ENABLE
20487 09:51:25 (0) ** - EXPECTED ACE:
20488 09:51:25 (0) ** ACEType: &h0
20489 09:51:25 (0) ** ACCESS_ALLOWED_ACE_TYPE
20490 09:51:25 (0) ** ACEFlags: &h12
20491 09:51:25 (0) ** CONTAINER_INHERIT_ACE
20492 09:51:25 (0) ** INHERITED_ACE
20493 09:51:25 (0) ** ACEMask: &h13
20494 09:51:25 (0) ** WBEM_ENABLE
20495 09:51:25 (0) ** WBEM_METHOD_EXECUTE
20496 09:51:25 (0) ** WBEM_WRITE_PROVIDER
20497 09:51:25 (0) **
20498 09:51:25 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
20499 09:51:25 (0) ** This will cause some operations to fail!
20500 09:51:25 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
20501 09:51:25 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
20502 09:51:25 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
20503 09:51:25 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
20504 09:51:25 (0) ** A specific WMI application can always require a security setup different
20505 09:51:25 (0) ** than the WMI security defaults.
20506 09:51:25 (0) **
20507 09:51:25 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
20508 09:51:25 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
20509 09:51:25 (0) ** - REMOVED ACE:
20510 09:51:25 (0) ** ACEType: &h0
20511 09:51:25 (0) ** ACCESS_ALLOWED_ACE_TYPE
20512 09:51:25 (0) ** ACEFlags: &h12
20513 09:51:25 (0) ** CONTAINER_INHERIT_ACE
20514 09:51:25 (0) ** INHERITED_ACE
20515 09:51:25 (0) ** ACEMask: &h13
20516 09:51:25 (0) ** WBEM_ENABLE
20517 09:51:25 (0) ** WBEM_METHOD_EXECUTE
20518 09:51:25 (0) ** WBEM_WRITE_PROVIDER
20519 09:51:25 (0) **
20520 09:51:25 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
20521 09:51:25 (0) ** Removing default security will cause some operations to fail!
20522 09:51:25 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
20523 09:51:25 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
20524 09:51:25 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
20525 09:51:25 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
20526 09:51:25 (0) ** A specific WMI application can always require a security setup different
20527 09:51:25 (0) ** than the WMI security defaults.
20528 09:51:25 (0) **
20529 09:51:25 (0) **
20530 09:51:25 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
20531 09:51:25 (0) ** DCOM security error(s) detected: .................................................................................... 3.
20532 09:51:25 (0) ** WMI security warning(s) detected: ................................................................................... 0.
20533 09:51:25 (0) ** WMI security error(s) detected: ..................................................................................... 3.
20534 09:51:25 (0) **
20535 09:51:25 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
20536 09:51:25 (1) !! ERROR: Overall WMI security status: ................................................................................. ERROR!
20537 09:51:25 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
20538 09:51:25 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
20539 09:51:25 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario Control".
20540 09:51:25 (0) ** 'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
20541 09:51:25 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
20542 09:51:25 (0) ** 'select * from MSFT_SCMEventLogEvent'
20543 09:51:25 (0) **
20544 09:51:25 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
20545 09:51:25 (0) ** WMI ADAP status: .................................................................................................... OK.
20546 09:51:25 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 1 NAMESPACE(S)!
20547 09:51:25 (0) ** - ROOT/SERVICEMODEL.
20548 09:51:25 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
20549 09:51:25 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
20550 09:51:25 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
20551 09:51:25 (0) ** i.e. 'WMIC.EXE /NODE:"WKS-NL-11" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
20552 09:51:25 (0) **
20553 09:51:25 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
20554 09:51:25 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
20555 09:51:25 (0) ** WMI GET operations: ................................................................................................. OK.
20556 09:51:25 (0) ** WMI MOF representations: ............................................................................................ OK.
20557 09:51:25 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
20558 09:51:25 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
20559 09:51:25 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
20560 09:51:25 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
20561 09:51:25 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
20562 09:51:25 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
20563 09:51:25 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
20564 09:51:25 (0) ** WMI static instances retrieved: ..................................................................................... 873.
20565 09:51:25 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
20566 09:51:25 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
20567 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20568 09:51:25 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
20569 09:51:25 (0) ** DCOM: ............................................................................................................. 0.
20570 09:51:25 (0) ** WINMGMT: .......................................................................................................... 0.
20571 09:51:25 (0) ** WMIADAPTER: ....................................................................................................... 0.
20572 09:51:25 (0) **
20573 09:51:25 (0) ** # of additional Event Log events AFTER WMIDiag execution:
20574 09:51:25 (0) ** DCOM: ............................................................................................................. 0.
20575 09:51:25 (0) ** WINMGMT: .......................................................................................................... 0.
20576 09:51:25 (0) ** WMIADAPTER: ....................................................................................................... 0.
20577 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20578 09:51:25 (0) ** WMI Registry key setup: ............................................................................................. OK.
20579 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20580 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20581 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20582 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20583 09:51:25 (0) **
20584 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20585 09:51:25 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
20586 09:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20587 09:51:25 (0) **
20588 09:51:25 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_WKS-NL-11_2009.03.05_09.45.22.LOG' for details.
20589 09:51:25 (0) **
20590 09:51:25 (0) ** WMIDiag v2.0 ended on Thursday, March 05, 2009 at 09:51 (W:65 E:22 S:1).

Hope you can help me because i got no clue anymore.
Alientje

[Alientje]

Lansweeper wrote:
Could you start wmimgmt.msc, go to security and post screenshots of the security settings of root, default and cimv2

Seems i cant work on the workstation today because someone is working on it, will try it monday and let you know. Tho i think it's getting in right direction because i can't remotely connect to the wmimgmt.msc of that workstation because i get a win32 access denied message, but i can to other workstations. Anyway will check it out monday have a nice weekend.

[Hemoco]

Check the ForceGuest registry value in this key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Make sure it is set to 0

[Alientje]

Lansweeper wrote:
Check the ForceGuest registry value in this key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Make sure it is set to 0

Already checked that , it was and is set to 0.

[Hemoco]

Could you try running this repair utility : http://www.lansweeper.com/repairwmi.zip

[Alientje]

Lansweeper wrote:
Could you try running this repair utility : http://www.lansweeper.com/repairwmi.zip

I ran the fix, when it was done and services started again. Tried connection tester but still same problem :(\
ty for fast reply btw