
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-08-2005 09:53 AM
Hi!
The server is not seeing the hardware inventory of my test client pc. I checked tsyserrors table and found out these 2 errors:
1. The RPC is unavailable (this is majority of the erorrs)
2. The network path was not found (About 6)
When I run lsclient <serverIPaddr> it is ok.
I need to open default.aspx on my browser to see hardware inventory right?
Please help! Thanks!
Allan
===
Here's my setup:
Windows 2000 SP4
SQL 2000 SP4
domain\lsscanner user who is member of domain admin
lsuser who is an sql account with full access to lansweeper database
This is my web.config configuration file
<configuration>
<appSettings>
<add key="MM_CONNECTION_HANDLER_Lansweeper" value="sqlserver.htm" />
<add key="MM_CONNECTION_STRING_Lansweeper" value="Persist Security Info=False;Data Source=127.0.0.1;Initial Catalog=Lansweeper;User ID=lsuser;Password=<password>" />
<add key="MM_CONNECTION_DATABASETYPE_Lansweeper" value="SQLServer" />
<add key="MM_CONNECTION_SCHEMA_Lansweeper" value="" />
<add key="MM_CONNECTION_CATALOG_Lansweeper" value="" />
</appSettings>
</configuration>
This is my LSwinap.exe.config configuration file
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<!-- User application and configured property settings go here.-->
<!-- Example: <add key="settingName" value="settingValue"/> -->
<add key="ConnectionString" value="integrated security=SSPI;data source="127.0.0.1";persist security info=False;initial catalog=Lansweeper" />
<add key="ConcurrentThreads" value="20" />
</appSettings>
</configuration>
The server is not seeing the hardware inventory of my test client pc. I checked tsyserrors table and found out these 2 errors:
1. The RPC is unavailable (this is majority of the erorrs)
2. The network path was not found (About 6)
When I run lsclient <serverIPaddr> it is ok.
I need to open default.aspx on my browser to see hardware inventory right?
Please help! Thanks!
Allan
===
Here's my setup:
Windows 2000 SP4
SQL 2000 SP4
domain\lsscanner user who is member of domain admin
lsuser who is an sql account with full access to lansweeper database
This is my web.config configuration file
<configuration>
<appSettings>
<add key="MM_CONNECTION_HANDLER_Lansweeper" value="sqlserver.htm" />
<add key="MM_CONNECTION_STRING_Lansweeper" value="Persist Security Info=False;Data Source=127.0.0.1;Initial Catalog=Lansweeper;User ID=lsuser;Password=<password>" />
<add key="MM_CONNECTION_DATABASETYPE_Lansweeper" value="SQLServer" />
<add key="MM_CONNECTION_SCHEMA_Lansweeper" value="" />
<add key="MM_CONNECTION_CATALOG_Lansweeper" value="" />
</appSettings>
</configuration>
This is my LSwinap.exe.config configuration file
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<!-- User application and configured property settings go here.-->
<!-- Example: <add key="settingName" value="settingValue"/> -->
<add key="ConnectionString" value="integrated security=SSPI;data source="127.0.0.1";persist security info=False;initial catalog=Lansweeper" />
<add key="ConcurrentThreads" value="20" />
</appSettings>
</configuration>
Labels:
- Labels:
-
Archive
6 REPLIES 6

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-10-2005 12:42 PM
You should run the lsclient from a domain users that is logged in.
Information that is passed to the server contains the adsi path for the user and the computer.
Information that is passed to the server contains the adsi path for the user and the computer.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-09-2005 12:44 PM
i think i found the reason why i wasnt able to send hardware inventory to the server... i modified the workstation so that the domain admins is not member of the local administrators group. now its working!
thanks!:)
thanks!:)

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-09-2005 05:00 AM
yes, we have Windows 2000 Active Directory. Lansweeper is running on a member server.
I logged on to the test workstation using local user account (ie. not domain user account). then I ran lsclient <serverIPaddress) from the command-line manually.
I logged on to the test workstation using local user account (ie. not domain user account). then I ran lsclient <serverIPaddress) from the command-line manually.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-08-2005 01:53 PM
Do you have an active directory network?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-08-2005 12:21 PM
Hi!
This is the output of the tblComputers table...
LAN888 5.0.2195 LAN888 administrator LAN888 administrator LAN888 7/8/2005 12:23:31 PM 7/4/2005 4:11:13 PM
Yes I am running lswinap.exe using lsscanner or administrator user accounts which are both member of domain admins group.
Are my configuration files correct?
Thanks!
This is the output of the tblComputers table...
LAN888 5.0.2195 LAN888 administrator LAN888 administrator LAN888 7/8/2005 12:23:31 PM 7/4/2005 4:11:13 PM
Yes I am running lswinap.exe using lsscanner or administrator user accounts which are both member of domain admins group.
Are my configuration files correct?
Thanks!

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-08-2005 11:13 AM
You can open the table tblcomputers, this should be filled in correctly.
Could you check this and maybe post the output.
This problem is mostly caused by firewalls on the client (XP SP2), but since you have Win2000 clients there must be another reason.
Are you running the lswinap.exe with an account that has administrative rights on the clients?
Could you check this and maybe post the output.
This problem is mostly caused by firewalls on the client (XP SP2), but since you have Win2000 clients there must be another reason.
Are you running the lswinap.exe with an account that has administrative rights on the clients?
