
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
‎04-29-2009 11:54 PM
Yes I can connect to 127.0.0.1:9524.
Yes netstat -a shows a service running on 9524.
No, there are no errors in the errorlog.txt file.
Lansweeper console shows a service parameter of Listenport being 9524, so that is correct.
Again there is no firewall running on this machine - which makes it really odd that tsclient cannot connect even to 127.0.0.1 9524.
Yes netstat -a shows a service running on 9524.
No, there are no errors in the errorlog.txt file.
Lansweeper console shows a service parameter of Listenport being 9524, so that is correct.
Again there is no firewall running on this machine - which makes it really odd that tsclient cannot connect even to 127.0.0.1 9524.
Kevin

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-29-2009 11:14 PM
Are you able to connect on the server to http://127.0.0.1:9524?
When you type in "netstat -a" on the server, so you see the service listening on port 9524?
Are there any errors in errorlog.txt file?
When you type in "netstat -a" on the server, so you see the service listening on port 9524?
Are there any errors in errorlog.txt file?
