lsservice nor lswinap are opening a listening port

[Michael]

Hi all.

Had a good old time configuring Lansweeper ( I am new to SQL server)

Ive got all that working now. LsWinap.exe logs on OK(well, no errors) and pops up its GUI.

But when I run `netstat -an`, I can not see any listening 9524 port.
Hence lsclient.exe fails to connect from clients.

2k machine on a 2k3/2k domain.
SQL Express 2005

Thanks in advance.

[tboege]

I have got the same problem.

Neither lsservice or lswinap is listening on port 9542. It is strange, because it did work - but it has stopped worked recently (maybe an MS security update on my w2k3 dc).

Any news about a solution (or even better: the new version)?

[Michael]

2 months is nothing.

Something to look forward to!

Cheers

[Hemoco]

If you have patience, the new version of lansweeper will be released in 2 months.

[Michael]

No go.

I shutdown the ls service, and ran lswinap.

It comes up fine, but still there is no port open

Web page seems to be working fine, obviously though it has no computers listed in it.

In DotNet config I ran through Runtime Security Policy and made all code groups FullTrust.
I also tried adding lswinap.exe to the managed applications root.

I would really like to get this working, but maybe its not possible.

Its a 2k member DC. Latest DotNet.

I dunno. Who codes Lansweeper? What other possible reason is there that lswinap.exe can pop up its window fine, but still not have a port open?

[Michael]

Long time! 16 days! ha ha ha 🙂

And here I am another 8 dyas latter.

I will try your suggestion now. Thank you for your brain time.

Michael

[Hemoco]

I thought about this problem for a long time 🙂
Could you check the security settings (net 2.0 framework configuration mmc) to make sure that you application is allowed to open ports.