→ 🚀What's New? Explore Lansweeper's Fall 2024 Updates! Fall Launch Blog !

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
laminblake
Engaged Sweeper
So far this is only happening to windows 8.1 machines that aren't joined to my domain. I can ping them locally from my computer but lansweeper says it can't ping them. It has the correct ip address for them but it states it can't ping. Firewall is turned off and remote registry is turned on. I did notice the machines are running an older version of LS push but i can't upgrade them if lansweeper keeps saying it cant ping them. any ideas?
1 ACCEPTED SOLUTION
Susan_A
Lansweeper Alumni
Ping failures point to a DNS or firewall issue, not a Lansweeper issue. A ping request performed by Lansweeper is the same as a ping request performed from the command line. If you are seeing a difference in the results from these ping requests, then either:
  • You are pinging from a different machine, not the Lansweeper server.
  • You are pinging a different parameter. The computer's Lansweeper webpage should state what Lansweeper tried to ping: the machine's IP, NetBIOS or FQDN.
  • The ping failure you are seeing on the computer's Lansweeper webpage is old. Rescan the machine to see whether the ping request is still failing.

View solution in original post

1 REPLY 1
Susan_A
Lansweeper Alumni
Ping failures point to a DNS or firewall issue, not a Lansweeper issue. A ping request performed by Lansweeper is the same as a ping request performed from the command line. If you are seeing a difference in the results from these ping requests, then either:
  • You are pinging from a different machine, not the Lansweeper server.
  • You are pinging a different parameter. The computer's Lansweeper webpage should state what Lansweeper tried to ping: the machine's IP, NetBIOS or FQDN.
  • The ping failure you are seeing on the computer's Lansweeper webpage is old. Rescan the machine to see whether the ping request is still failing.