Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2008 06:02 PM
Hi everyone
Having given up on SCE, I've now switched my attention to LANSweeper, I hope it is everything it appears to be :w)
I have got to the stage in the installation where I have done a test with the lsclient "servername" "port"
This tried to connect and comes back with failed. I tried using the testconnection utility, and that hung. I checked my firewall and it was blocking requests on 5001 and 135. I temporarily turned off the firewall and the testconnection was fine. However, even with the firewall off the lsclient still reported a failure.
One other thing that didn't work prior to this was the surfing to http://servername:9524
My configuration of the IIS Server I had to set to 8001 as there is an existing app using the default port 80
Are there any logs I can access to gain an insight?
Having given up on SCE, I've now switched my attention to LANSweeper, I hope it is everything it appears to be :w)
I have got to the stage in the installation where I have done a test with the lsclient "servername" "port"
This tried to connect and comes back with failed. I tried using the testconnection utility, and that hung. I checked my firewall and it was blocking requests on 5001 and 135. I temporarily turned off the firewall and the testconnection was fine. However, even with the firewall off the lsclient still reported a failure.
One other thing that didn't work prior to this was the surfing to http://servername:9524
My configuration of the IIS Server I had to set to 8001 as there is an existing app using the default port 80
Are there any logs I can access to gain an insight?
Labels:
- Labels:
-
Archive
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-12-2008 05:23 AM
What service are you talking about above?
Lsclient connects to the server where the lansweeperpro service is running (typically on port 9524)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-08-2008 10:33 AM
Yes that was it thanks.
Although it was working at some point, but I was having a few problems with access to SQL server so this may have corrupted it maybe.
Anyway, I recreated it and service/access running fine.
Cheers
Ian
Although it was working at some point, but I was having a few problems with access to SQL server so this may have corrupted it maybe.
Anyway, I recreated it and service/access running fine.
Cheers
Ian
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-06-2008 06:07 PM
lsclient connects to the server where the service is running (normally on port 9524)
since you can't surf to http://servername:9524 -> your service isn't running
Make sure that the service is started and listening on port 9524
If there are any errors you can find them in your service folder : "errorlog.txt"
since you can't surf to http://servername:9524 -> your service isn't running
Make sure that the service is started and listening on port 9524
If there are any errors you can find them in your service folder : "errorlog.txt"
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2008 11:05 PM
Lansweeper wrote:
lsclient connects to the server where the service is running (normally on port 9524)
since you can't surf to http://servername:9524 -> your service isn't running
Make sure that the service is started and listening on port 9524
If there are any errors you can find them in your service folder : "errorlog.txt"
I will probabaly sound like an idiot but I really want to get this running so here goes:
What service are you talking about above? Lanserverpro30? If not please tell me what I am missing.
Also please see my post here: http://forum.lansweeper.com/yaf_postst331_Website-wont-connect.aspx
Thanks,
Maureen
