We’re currently experiencing a high volume of support requests, which may result in longer response times — Thank you for your patience and understanding.
Community FAQ
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
jbarnes
Engaged Sweeper
I've installed the latest version on a Windows Server 2003 server with the database on a backend database server. the script is:

Set WshShell = CreateObject("WScript.Shell")

WshShell.run "%logonserver%\netlogon\lansweeper\lsclient.exe servername",0

When run on my pc(I have domain admin), my pc showed up.
When run on a system admin through grouop policy, after a reboot, the wscript ran and his pc added.
When run on a normal user without admin privileges, nothing shows up. The script shows up under gpresult so it is being applied.

This was previously on a VMware server and it worked fine on there without making any changes.

Are there any special ports that need to be opened up to users or access given to any folders? As a domain admin, we have carte blanche to everything but running monitoring on the ip address of the normal computer and just trying to run the script itself only shows it trying to use port 80 to get to the server which is leaving me at a loss. It feels like a permissions issue somehow but I can't see who or what would need to change. Any help would be greatly appreciated.

also, this script is the exact same as from the vm server. all I did was change the servername.
4 REPLIES 4
Hemoco
Lansweeper Alumni
Take a look at this Microsoft articles :

http://msdn.microsoft.com/en-us/library/bb219447(VS.85).aspx
http://support.microsoft.com/kb/875605

jbarnes
Engaged Sweeper
We opened it up to all ports and it worked. We limited the ports to 135 and 1665(ports we saw it using) and it stopped working again. Are there set ports that need to be opened up or does it seem to just choose ports at random?
jbarnes
Engaged Sweeper
yes. We monitor it with Cisco ADSM on the firewall and see it connecting to port 80 with no failures. We've narrowed it down to a networking issue, which would be ports because we have a user that is on a system admin network, but doesn't have domain admin rights and it worked on his computer. The sys admin network has carte blanche on all ports on all subnets.
Hemoco
Lansweeper Alumni
If I understand correctly you see that the script is running and trying to connect to servername:80 right?

Archive

This board contains archived posts from the retired Lansweeper Forum and Insiders Community.

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now