No scans on other subnets

[Lanman]

Hello all-

Been fighting this issue for 3 days now and could use some help. All the pcs and servers are seen by Lansweeper on all subnets. I can remote control, take remote screen shots etc. but i cannot scan pcs that are not on the same subnet as the Lansweeper service. I get "The RPC server is unavailable" error in Lansweeper console and the corresponding "DCOM was unable to communicate with......using any of teh configured protocols" in the event viewer. I have checked the DCOM settings, disabled all firewalls on both server and workstation, confirmed that all traffic can pass through the router. I have followed both KB articles for both errors.



Any ideas?

[Hemoco]

Lanman wrote:

The Connection Tester works fine for all all pcs on the same subnet as teh lansweeper server.

When you do it to the other subnet, what happens?

[Hemoco]

Please take a look at the version of the service.
When you try the connection tester to a computer in this subnet what happens?
You could also manually try to telnet to port 135 on a computer to see what happens.

Lstrigger only works for clients already in the database.
lstrigger response "success" means that the message to the server to trigger scanning succeeded (it doesn't mean that the actual scanning worked)

[Lanman]

Hi admin-

Thanks for helping out Love the product. I have uploaded the error message screenshots. I am on version 3.5.1.13

Another bit of info: When i "trigger scan", the command propmpt box appears and says "Lansweeper Trigger Client........connecting..........success!" and then dissappears. On the client side, i am monitoring with TCPview and i see it opening 5 ports in teh 62400 range. They do not close. If i run it again, it just adds 5 more open ports.

[Hemoco]

Could you post a screenshot of the exact errors in the errorscreen please.
Are you using version 3.5.1?