Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-29-2009 10:35 PM
I cannot get tsclient to connect to lansweeper server. I posted a message yesterday but it seems that it is not active now and some one closed it off. I don't know why though... Anyway...
Here it goes again.
I'm using lansweeper 3.5.
There is NO firewall active on the server or the client workstation I'm testing from.
Neither the server or the client can connect using tsclient servername port.
I'm using the default port 9524 on the server and using tsclient with or without the port still returns a fail.
I can connect via the webconsole to lansweeper from the workstation AND the server itself even when I use the loopback.
Here it goes again.
I'm using lansweeper 3.5.
There is NO firewall active on the server or the client workstation I'm testing from.
Neither the server or the client can connect using tsclient servername port.
I'm using the default port 9524 on the server and using tsclient with or without the port still returns a fail.
I can connect via the webconsole to lansweeper from the workstation AND the server itself even when I use the loopback.
Kevin
Labels:
- Labels:
-
Archive
11 REPLIES 11
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-01-2009 12:11 AM
This particular computer runs another program which has a web server component also. That program uses port 80. Your install, correctly detected that IIS was not installed and happily installed it for me. But it failed to check for a port conflict which occurred between this other web server software and IIS. IIS installs by default on port 80.
My confusion came in because the only mention of ports had to do with the lsclient and it's default of 9524, and I confused that port as the http port that lansweeper web console would use as well. I now realize it does not. So when I couldn't attach to the web console I changed the port in IIS to the same as the lsclient port. That is why the lsclient couldn't communicate and the web console worked.
So for the installer I'd recomend a routine that check's if IIS's port is available - IF - IIS needs to be installed or is otherwise disabled. It should be OK otherwise. But if it needs to be installed, knowing that it install's on port 80 do a quick check of port 80. If it's in use then the install can simply give a warning to the user that they need to change IIS's port to something else and not the same port as the lsclient.
It wouldn't hurt to have a KB article explaining how:
The lsclient.exe communicates
The web console communicates
Lansweeper obtains info about computers
The differences between the freeware and premium versions with respect to the above items.
Had those been available I'd have figured it out pretty quickly. Of course if I'd remembered I had another web server running on the machine I should have figured it pretty quickly to.
Also a flow chart to follow that would lead a user on a step by step series of diagnostic checks.
The install document was fairly sparse on pretty much everything to do with IIS and the ports in use and how the pieces fit together.
My confusion came in because the only mention of ports had to do with the lsclient and it's default of 9524, and I confused that port as the http port that lansweeper web console would use as well. I now realize it does not. So when I couldn't attach to the web console I changed the port in IIS to the same as the lsclient port. That is why the lsclient couldn't communicate and the web console worked.
So for the installer I'd recomend a routine that check's if IIS's port is available - IF - IIS needs to be installed or is otherwise disabled. It should be OK otherwise. But if it needs to be installed, knowing that it install's on port 80 do a quick check of port 80. If it's in use then the install can simply give a warning to the user that they need to change IIS's port to something else and not the same port as the lsclient.
It wouldn't hurt to have a KB article explaining how:
The lsclient.exe communicates
The web console communicates
Lansweeper obtains info about computers
The differences between the freeware and premium versions with respect to the above items.
Had those been available I'd have figured it out pretty quickly. Of course if I'd remembered I had another web server running on the machine I should have figured it pretty quickly to.
Also a flow chart to follow that would lead a user on a step by step series of diagnostic checks.
The install document was fairly sparse on pretty much everything to do with IIS and the ports in use and how the pieces fit together.
Kevin
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2009 11:30 PM
Great debugging!
Could you post some more details so we can try to have the installer detect this.
Could you post some more details so we can try to have the installer detect this.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2009 10:10 PM
I got it. The problem was a port conflict between IIS and another webserver on the machine. I now have all the pieces working together. you can move this to old/solved now.
Kevin
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2009 10:00 PM
I've done further testing. It seems the problem is with IIS's port and a conflict with lansweeper. The only way for me to connect to the web console is to have IIS configured to run on port 9524. With it running on 9524 the lsclient cannot connect, but I can open the web console. When I switch IIS to any other port, the lsclient can connect but then I cannot connect to the web console. I can access the gui console in both configurations.
Kevin
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2009 07:47 PM
No firewall, no security software.
It is something to do with the IIS configuration though. I'll look at the config of IIS and see if I can spot the problem and correct it.
Non the less here is a packet capture of lsclient at work which clearly shows IIS's involvement:
GET /normal?comp=P3-343KG-01&domain=AD&userdomain=AD&user=XXXX&site=PG&ip=ME.XXX.XXX.XXX HTTP/1.1
Host: MYSERVER:9524
Accept: text/html, */*
Accept-Encoding: identity
User-Agent: Mozilla/3.0 (compatible; Indy Library)
HTTP/1.1 401 Unauthorized
Content-Length: 1656
Content-Type: text/html
Server: Microsoft-IIS/6.0
WWW-Authenticate: Negotiate
WWW-Authenticate: NTLM
X-Powered-By: ASP.NET
Date: Thu, 30 Apr 2009 15:29:25 GMT
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>You are not authorized to view this page</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=Windows-1252">
<STYLE type="text/css">
BODY { font: 8pt/12pt verdana }
H1 { font: 13pt/15pt verdana }
H2 { font: 8pt/12pt verdana }
A:link { color: red }
A:visited { color: maroon }
</STYLE>
</HEAD><BODY><TABLE width=500 border=0 cellspacing=10><TR><TD>
<h1>You are not authorized to view this page</h1>
You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept.
<hr>
<p>Please try the following:</p>
<ul>
<li>Contact the Web site administrator if you believe you should be able to view this directory or page.</li>
<li>Click the <a href="javascript:location.reload()">Refresh</a> button to try again with different credentials.</li>
</ul>
<h2>HTTP Error 401.2 - Unauthorized: Access is denied due to server configuration.<br>Internet Information Services (IIS)</h2>
<hr>
<p>Technical Information (for support personnel)</p>
<ul>
<li>Go to <a href="http://go.microsoft.com/fwlink/?linkid=8180">Microsoft Product Support Services</a> and perform a title search for the words <b>HTTP</b> and <b>401</b>.</li>
<li>Open <b>IIS Help</b>, which is accessible in IIS Manager (inetmgr),
and search for topics titled <b>About Security</b>, <b>Authentication</b>, and <b>About Custom Error Messages</b>.</li>
</ul>
</TD></TR></TABLE></BODY></HTML>
It is something to do with the IIS configuration though. I'll look at the config of IIS and see if I can spot the problem and correct it.
Non the less here is a packet capture of lsclient at work which clearly shows IIS's involvement:
GET /normal?comp=P3-343KG-01&domain=AD&userdomain=AD&user=XXXX&site=PG&ip=ME.XXX.XXX.XXX HTTP/1.1
Host: MYSERVER:9524
Accept: text/html, */*
Accept-Encoding: identity
User-Agent: Mozilla/3.0 (compatible; Indy Library)
HTTP/1.1 401 Unauthorized
Content-Length: 1656
Content-Type: text/html
Server: Microsoft-IIS/6.0
WWW-Authenticate: Negotiate
WWW-Authenticate: NTLM
X-Powered-By: ASP.NET
Date: Thu, 30 Apr 2009 15:29:25 GMT
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>You are not authorized to view this page</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=Windows-1252">
<STYLE type="text/css">
BODY { font: 8pt/12pt verdana }
H1 { font: 13pt/15pt verdana }
H2 { font: 8pt/12pt verdana }
A:link { color: red }
A:visited { color: maroon }
</STYLE>
</HEAD><BODY><TABLE width=500 border=0 cellspacing=10><TR><TD>
<h1>You are not authorized to view this page</h1>
You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept.
<hr>
<p>Please try the following:</p>
<ul>
<li>Contact the Web site administrator if you believe you should be able to view this directory or page.</li>
<li>Click the <a href="javascript:location.reload()">Refresh</a> button to try again with different credentials.</li>
</ul>
<h2>HTTP Error 401.2 - Unauthorized: Access is denied due to server configuration.<br>Internet Information Services (IIS)</h2>
<hr>
<p>Technical Information (for support personnel)</p>
<ul>
<li>Go to <a href="http://go.microsoft.com/fwlink/?linkid=8180">Microsoft Product Support Services</a> and perform a title search for the words <b>HTTP</b> and <b>401</b>.</li>
<li>Open <b>IIS Help</b>, which is accessible in IIS Manager (inetmgr),
and search for topics titled <b>About Security</b>, <b>Authentication</b>, and <b>About Custom Error Messages</b>.</li>
</ul>
</TD></TR></TABLE></BODY></HTML>
Kevin
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2009 10:05 AM
Could it be that some sort of local firewall or security program on the client is blocking lsclient from sending traffic?
The connection obviously works if you can telnet.
The connection obviously works if you can telnet.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2009 01:31 AM
Tcpview from sysinternals show these connections are available on the server...
Lansweeperservice.exe:6276 UDP myserver:23184 *:*
Lansweeperservice.exe:6276 TCP myserver:23307 sqlserver:ms-sql-s ESTABLISHED
Lansweeperservice.exe:6276 TCP myserver:23306 sqlserver:ms-sql-s ESTABLISHED
System:4 TCP myserver:9524 epo:0 LISTENING
The errorlog.txt file contains only these entries:
4/27/2009 1:06:30 PM: Database connection successful, starting up service
4/27/2009 2:38:23 PM: Stopping service
4/27/2009 2:38:27 PM: Database connection successful, starting up service
4/29/2009 1:58:57 PM: Stopping service
4/29/2009 1:59:29 PM: Database connection successful, starting up service
4/29/2009 2:03:20 PM: Stopping service
4/29/2009 2:03:26 PM: Database connection successful, starting up service
4/29/2009 2:05:19 PM: Stopping service
4/29/2009 2:05:23 PM: Database connection successful, starting up service
The connection tester (testconnection.exe) is always successful connecting to the server from the server, the client from the server and the server from the client. No problems connecting with that.
Still the lsclient.exe always gives this:
C:\Program Files\lansweeper\Client>lsclient MYSERVER
Lansweeper client
-----------------
Connecting...
Failed
C:\Program Files\lansweeper\Client>lsclient MYSERVER.FQDN
Lansweeper client
-----------------
Connecting...
Failed
C:\Program Files\lansweeper\Client>lsclient XXX.XXX.XXX.XXX
Lansweeper client
-----------------
Connecting...
Failed
C:\Program Files\lansweeper\Client>lsclient MYSERVER 9524
Lansweeper client
-----------------
Connecting...
Failed
C:\Program Files\lansweeper\Client>lsclient MYSERVER.FQDN 9524
Lansweeper client
-----------------
Connecting...
Failed
C:\Program Files\lansweeper\Client>lsclient XXX.XXX.XXX.XXX 9524
Lansweeper client
-----------------
Connecting...
Failed
Lansweeperservice.exe:6276 UDP myserver:23184 *:*
Lansweeperservice.exe:6276 TCP myserver:23307 sqlserver:ms-sql-s ESTABLISHED
Lansweeperservice.exe:6276 TCP myserver:23306 sqlserver:ms-sql-s ESTABLISHED
System:4 TCP myserver:9524 epo:0 LISTENING
The errorlog.txt file contains only these entries:
4/27/2009 1:06:30 PM: Database connection successful, starting up service
4/27/2009 2:38:23 PM: Stopping service
4/27/2009 2:38:27 PM: Database connection successful, starting up service
4/29/2009 1:58:57 PM: Stopping service
4/29/2009 1:59:29 PM: Database connection successful, starting up service
4/29/2009 2:03:20 PM: Stopping service
4/29/2009 2:03:26 PM: Database connection successful, starting up service
4/29/2009 2:05:19 PM: Stopping service
4/29/2009 2:05:23 PM: Database connection successful, starting up service
The connection tester (testconnection.exe) is always successful connecting to the server from the server, the client from the server and the server from the client. No problems connecting with that.
Still the lsclient.exe always gives this:
C:\Program Files\lansweeper\Client>lsclient MYSERVER
Lansweeper client
-----------------
Connecting...
Failed
C:\Program Files\lansweeper\Client>lsclient MYSERVER.FQDN
Lansweeper client
-----------------
Connecting...
Failed
C:\Program Files\lansweeper\Client>lsclient XXX.XXX.XXX.XXX
Lansweeper client
-----------------
Connecting...
Failed
C:\Program Files\lansweeper\Client>lsclient MYSERVER 9524
Lansweeper client
-----------------
Connecting...
Failed
C:\Program Files\lansweeper\Client>lsclient MYSERVER.FQDN 9524
Lansweeper client
-----------------
Connecting...
Failed
C:\Program Files\lansweeper\Client>lsclient XXX.XXX.XXX.XXX 9524
Lansweeper client
-----------------
Connecting...
Failed
Kevin
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2009 12:48 AM
Yes.
Kevin
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2009 12:01 AM
are you able to do this from another machine
telnet servername 9524
You should see a blank command screen with a blinking cursor.
telnet servername 9524
You should see a blank command screen with a blinking cursor.
