wmi error and eventlog error

[Tobbe]

I get this error: Wmierror The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) COMPUTERNAME (192.168.23.103)
when i try to run lsclient on a client computer. And on the Server where Lansweeper is installed i get the followin error message in the eventlogg:


Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 4
Date: 2008-06-03
Time: 11:01:36
User: N/A
Computer: INTRANET
Description:
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server COMPUTERNAME$. The target name used was RPCSS/COMPUTERNAME. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (<AD NAME>), and the client realm. Please contact your system administrator.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

i have about 20 computer that hasn´t been scanned. and 40 computer that has been scanned.
The firewall has been disabled on every computer.

/Tobias

[Tobbe]

I had some problem with lingering objects on the DC which had stopped the net logon service.
after resolving that i had no problem there after.

/Tobias

[Hemoco]

Tobbe, what were the exact active directory problems.

Other people are also experiencing this problem.

[Tobbe]

I think i have solved the problem i had some Active directory errors that i sorted out.

thanks for all the help.

[dayron]

I was having issues like this. WMI would fail on the lansweeper connection tester on the laptops that we keep the XP firewall running on. If I fully disabled the XP firewall on the laptops the PCs would register correctly. I resolved the issue by using group policy to allow WMI and other remote management type requests to come through the firewall from my LAN's subnet. Here is the MS KB link:

http://support.microsoft.com/kb/840634/en-us

I used method 3 which is group policy as mentioned above to save myself from walking around to MANY workstations. I rolled out that GP yesterday. This morning when all the laptops booted up they registered in lansweeper correctly.

[Jon]

Tobbe - I was suffering the same problem a little persistance later discovered this

On the client machine

Open DCOMCNFG
Click on the COM Security
Click Edit Default
Add your main domain Administrator to the list
Check remote access
Reboot Client machine

Voila - it all worked ok from this point, now got to go round the rest of the machines.

[Tobbe]

No cloning here just ordinary workstations added to the domain.

The time is the same on all computers and servers.

[Hemoco]

Did you by any chance clone/image these pc's without doing a sysprep first.
Is the time the same on the computers as on the domain controller?

[Tobbe]

C:\>ping 23-arb1

Pinging 23-arb1.ad.svpant.se [192.168.23.103] with 32 bytes of data:

Reply from 192.168.23.103: bytes=32 time=6ms TTL=126
Reply from 192.168.23.103: bytes=32 time=6ms TTL=126
Reply from 192.168.23.103: bytes=32 time=6ms TTL=126
Reply from 192.168.23.103: bytes=32 time=47ms TTL=126

Ping statistics for 192.168.23.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 47ms, Average = 16ms

C:\>ping -a 192.168.23.103

Pinging 23-arb1.ad.svpant.se [192.168.23.103] with 32 bytes of data:

Reply from 192.168.23.103: bytes=32 time=6ms TTL=126
Reply from 192.168.23.103: bytes=32 time=10ms TTL=126
Reply from 192.168.23.103: bytes=32 time=6ms TTL=126
Reply from 192.168.23.103: bytes=32 time=17ms TTL=126

Ping statistics for 192.168.23.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 17ms, Average = 9ms

C:\>

[Hemoco]

Could you post your ping results please
"ping computername"
"ping -a ipaddress"