Need some help please - Network path was not found

[ibettison]

Installed lansweeper v3.1 and the first three pcs registered fine. Then they stopped registering for no apparent reason.

I have tested the connection and everything connects ok! The errorlog is fine no error mesages. The lsclient.exe is run through a Group Policy and there are no reports of problems, and I have manually ran lslclient with a message returned of success!! The only error message I am able to see is on the Digital Dashboard when I click on the RED COMPUTER and select errors.

The error shown is

Regerror The network path was not found.

Can you shed some light on this error so that I can get Lansweeper working. It looks like a superb networking tool and will be invaluable to us especially with our future projects.

[Hemoco]

Sometimes when group policies don't work, you need to use the command "gpupdate /force" to make sure that they are applied.
You can also use the command "gpresult" on windows XP to see which group policies are applied.

[ibettison]

I have managed to get most of the computers working through firewall group policies but some still don't register.

To register the non-registering machines I've had to switch off the firewall completely then run lslclient and the switch the firewall back on. i know this is not ideal but many of my machines have rgistered sucessfully only a handful had to be visited. If people are interested I will list the steps I needed to go through to get the majority of the machines to register (including Vista machines), using group policies.

Have a good day everyone.

Ian.

[RonnyAM]

I have had some problems with the "Network path can not be found", that has been tracked down to the DNS server.
The PTR records in the reverse lookup zone may not be correct. In those cases, I get that error message.
Also experienced a couple of computers with remote registry turned of, and those kind of problems.

If you find a wrong PTR record, remember to flush dns on your lansweeper server before you retry the scan.

[Hemoco]

RonnyAM wrote:
I have had some problems with the "Network path can not be found", that has been tracked down to the DNS server.
The PTR records in the reverse lookup zone may not be correct. In those cases, I get that error message.
Also experienced a couple of computers with remote registry turned of, and those kind of problems.
If you find a wrong PTR record, remember to flush dns on your lansweeper server before you retry the scan.

This is indeed a common error, i'm still trying to figure out on how to prevent this error

[ibettison]

Just one other thing that might shed some light...

When I try to connect to the webpage using the port 9524 (http://{servername}:9524

I get the message...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The page cannot be found
The page you are looking for might have been removed, had its name changed, or is temporarily unavailable.
--------------------------------------------------------------------------------

Please try the following:

Make sure that the Web site address displayed in the address bar of your browser is spelled and formatted correctly.
If you reached this page by clicking a link, contact the Web site administrator to alert them that the link is incorrectly formatted.
Click the Back button to try another link.
HTTP Error 404 - File or directory not found.
Internet Information Services (IIS)

--------------------------------------------------------------------------------

Technical Information (for support personnel)

Go to Microsoft Product Support Services and perform a title search for the words HTTP and 404.
Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled Web Site Setup, Common Administrative Tasks, and About Custom Error Messages.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Any help or suggestions welcome.

Ian.

[ibettison]

I have checked all of the firewall settings and yes I am running the settings through Group Policies.
Have checked everything multiple times.

1. Test Connection returns no errors
2. When running lsclient.exe {servername} the message returned is "success".
3. but still there are RED COMPUTERS with the error
Regerror The network path was not found. {Computer Name} ({IP ADDRESS}) 15/07/2008 08:45:36

Is there a checklist of firewall settings required to allow Lansweeper to run?

Sorry for the capitals (i'm not shouting) just highlighting...

[Hemoco]

Most common cause of this problem is indeed the windows firewall (or other firewall) blocking the access.

Are you using a group policy to control the windows firewall?

[Naushad]

Have you checked all hardware and software firewalls? I had the same problem and it turned out to be my VPN firewall setting, which is important but I allowed the lansweeper server access in the firewall setting.