STILL RPC issues

[jcorso11]

Still having trouble with RPC Unavailable... I have the remote admin on, with IP of Lansweeper server. It works on half or so just fine. The others, the same GPO with those firewall settings. Firewalls on those which are active seen in netsh show state seem fine... then I turn off the firewall completley and the machine scans. Why is it that the same settings work fine on some, and not others. Same IP is set for the scanning server

[ifm]

I also get RPC Unavailable on 50 out of 400 computers, all with the same GPO.
On some of the computers I get a proper scan if I use psexec to manually run "LSClient.exe server"

Question:
If a laptop is started with the network cable and the user remove the cable just after login, will the scanner mark the computer as "RPC Unavailable" because it can not connect to the computer, or will that give another error?

[Hemoco]

ifm wrote:
If a laptop is started with the network cable and the user remove the cable just after login, will the scanner mark the computer as "RPC Unavailable" because it can not connect to the computer, or will that give another error?

At the time of scanning the service tries to connect to port 135 on the machines, if this fails at that time the machine will be reported as "RPC unavailable"

I suggest to try out the 3.5.1 beta version, it solves some RPC/active scanning issues.
http://www.lansweeper.com/forum/yaf_postst1514_Lansweeper-Service-351-update-1-beta.aspx

[Hemoco]

jcorso11 wrote:
then I turn off the firewall completley and the machine scans.

This must mean that there is a problem with your GPO configuration (not being enforced?)