cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
radioalarm
Engaged Sweeper
I have domain on Win2003 server, Lansweeper runs on another Win2008 machine. I started getting these errors on Lansweeper server:

EVENT # 119768
EVENT LOG System
EVENT TYPE Error
SOURCE DCOM
EVENT ID 10009
COMPUTERNAME vsrvsql
TIME 2011.04.21 08:23:50
MESSAGE machine.domain.lan/ <Record#1: Computer=(null);Pid=880;4/21/2011 5:23:50:18;Status=1722;Gencomp=2;Detloc=1710;Flags=0;Params=1;{Param#0:0}><Record#2: Computer=(null);Pid=880;4/21/2011 5:23:50:18;Status=1722;Gencomp=8;Detloc=1442;Flags=0;Params=1;{Param#0:machine.domain.lan}><Record#3: Computer=(null);Pid=880;4/21/2011 5:23:50:18;Status=1237;Gencomp=8;Detloc=313;Flags=0;Params=0;><Record#4: Computer=(null);Pid=880;4/21/2011 5:23:50:18;Status=10060;Gencomp=8;Detloc=311;Flags=0;Params=3;{Param#0:135}{Param#1:0}{Param#2:0x9822a8c000000000}><Record#5: Computer=(null);Pid=880;4/21/2011 5:23:50:18;Status=10060;Gencomp=8;Detloc=318;Flags=0;Params=0;>

This message is followed by 2 identical ones, except that the address it is trying to reach is changed to 'machine', and then to it's IP address.

Now the interesting part is that I get this error for ~7 computers out of ~50. The errors started to appear after client computers installed April 14th Windows updates. It seems that on boot the computer is not accessible for a few minutes, maybe the domain firewall profile is not applied.

The computers run WinXP, but it also seems that it appears only on PCs which were updated manually to SP3 long time ago.

Any ideas?
3 REPLIES 3
radioalarm
Engaged Sweeper
Well, I've found the primary reason why Lansweeper fails here. Domain firewall profile was not applied to the machines, and my policy allows remote connections only in this profile. Now the domain profile was not applied because something erased the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\History\NetworkName value. The determination whether PC is on domain network or other depends on this value. I've put back my domain DNS to this key, and everything worked fine.

Now we just need to find what caused this value removal.
radioalarm
Engaged Sweeper
2008 standard SP2 x64.

I just realized that it is probably not a Lansweeper problem, but something wrong with client DCOM and those recent updates. But still, maybe someone else experiences the same, and will report here.
Hemoco
Lansweeper Alumni
We'll try to reproduce this.
Is the server windows 2008 or windows 2008 R2?