cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
rppalmer
Engaged Sweeper
I know this question has been posted many times but I have been unable to find a solution to my problem. Lansweeper is running on Windows Server 2003 Standard R2 SP2. I configured a GPO that runs a script when the user logs on, it calls the lsclient.exe from the netlogon share. I followed the LanSweeper how to article for this. The firewall is turned on for all client machines, and I also followed the instructions to allow lansweeper to access, however, 65% of the clients are able to be scanned, 35% are not.

I have done the following:
1 . The company requires that Windows firewall be turned on. I have allowed the remote admin rule to allow unsolicited traffic from the Lansweeper server and allowed file and printer sharing.
2. The RPC, WMI and DCOM services are all turned on and set to run automatically
3. I have tested dns by pinging the hostname, fqdn and by doing a reverse lookup (ping -a) and it all resolved to the right hostname and IP address. I checked our forward and reverse lookup zones manually to make sure there were no duplicate hostnames or IP addresses.
4. I've used connection tester with the netbios, fqdn and IP address and they all fail.

Looking at the firewall logs, it's dropping packets destined for port 1103, the port seems to change all the time too.

11/12/2009 15:14:45 DROP TCP 192.168.50.200 192.168.50.56 4674 1103 48 S 1108570760 65535 RECEIVE
11/12/2009 15:14:48 DROP TCP 192.168.50.200 192.168.50.56 4674 1103 48 S 1108570760 65535 RECEIVE
11/12/2009 15:14:54 DROP TCP 192.168.50.200 192.168.50.56 4674 1103 48 S 1108570760 65535 RECEIVE
11/12/2009 15:15:06 DROP TCP 192.168.50.200 192.168.50.56 4679 1103 48 S 1879852743 65535 RECEIVE
11/12/2009 15:15:09 DROP TCP 192.168.50.200 192.168.50.56 4679 1103 48 S 1879852743 65535 RECEIVE
11/12/2009 15:15:15 DROP TCP 192.168.50.200 192.168.50.56 4679 1103 48 S 1879852743 65535 RECEIVE
11/12/2009 15:15:27 DROP TCP 192.168.50.200 192.168.50.56 4682 1103 48 S 16637848 65535 RECEIVE
11/12/2009 15:15:30 DROP TCP 192.168.50.200 192.168.50.56 4682 1103 48 S 16637848 65535 RECEIVE
11/12/2009 15:15:36 DROP TCP 192.168.50.200 192.168.50.56 4682 1103 48 S 16637848 65535 RECEIVE
11/12/2009 15:15:48 DROP TCP 192.168.50.200 192.168.50.56 4684 1103 48 S 312664118 65535 RECEIVE
11/12/2009 15:15:51 DROP TCP 192.168.50.200 192.168.50.56 4684 1103 48 S 312664118 65535 RECEIVE
11/12/2009 15:15:57 DROP TCP 192.168.50.200 192.168.50.56 4684 1103 48 S 312664118 65535 RECEIVE


Here is the information I received from Connection Tester:
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)

The thing is, when I stop the firewall service on that computer to test, the Connection Tester is able to connect and reports a success.

Is there a range of ports that LanSweeper users? I am not sure why the computer is dropping the connection since I explicitly allowed the remote access to all clients from the lansweeper server. Does anyone have any other suggestions? Please let me know if I have left out any troubleshooting steps.

Ryan
1 REPLY 1
rppalmer
Engaged Sweeper
It appears I have fixed it. For the Remote Administration Exception I had 4 or 5 servers listed (one of which was the lansweeper server) so out of curiosity I temporarily changed it to allow the whole subnet (192.168.50.0/24) instead and now it's working. Go figure. I hope this helps someone else!

Ryan