Kaseya Community

Home » Discussion Forums » General Questions and Discussions » "The network path was not found." During Lan Watch Install

Learn more about how AuthAnvil can protect and enhance your Kaseya experience

Similar Posts

Lanwatch Install "Path not Found"

by
on Nov 24, 2007

Client Installation Error - The network path was not found.

by
on Dec 21, 2005

LAN Watch executes network scan, however Install Agents is blank

by
on Apr 10, 2007

LAN Watch by Network 'unnamed' Networks

by
on Aug 21, 2014
  • Not Answered

Lan Watch install of Agent

by
on Sep 8, 2005
Details
  • 5 Replies
  • 0 Subscribers
  • Postedover 11 years ago

"The network path was not found." During Lan Watch Install

  • LegacyPoster
    Posted by
    on Mar 19, 2008 11:08 AM
    Anyone know why I get the error message "The network path was not found." when trying to install to clients on a domain. 2 out of 5 identical computers let the agent install just fine and the others produce "The network path was not found."

    Legacy Forum Name: "The network path was not found." During Lan Watch Install,
    Legacy Posted By Username: Resistance2Fly
  • LegacyPoster
    Posted by
    on Mar 19, 2008 11:14 AM
    Update: Knowledge base says its because of the windows firewall. Ill double check tommorow, but please post if you have any other ideas or experiences with this error.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: Resistance2Fly
  • LegacyPoster
    Posted by
    on Mar 19, 2008 1:14 PM
    I found that this may occur if there are invalid reverse dns records. Check your reverse zone in DNS and delete "orphaned" ptr entries.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: myArch-man
  • LegacyPoster
    Posted by
    on Mar 19, 2008 4:35 PM
    File & Print Sharing must be enabled in the firewall. If you are dealing with Vista workstations, then you need to use the Vista specific firewall MMC snapin. With Vista as well, you may need to run PSEXEC manually and add the -s switch. It should be fixed in 2008, but I've not had the opportunity to test this.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: smbtechnology
  • LegacyPoster
    Posted by
    on Mar 19, 2008 8:12 PM
    Checkpoint secureclient can also cause this, disable the security policy in your client then...

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: Patrick Verbeek
  • LegacyPoster
    Posted by
    on Mar 19, 2008 8:56 PM
    It was the invalid ptr records, thanks!

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: Resistance2Fly