Comparing MeshCentral 2 to ScreenConnect
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
No proxy in front of it, right?
No proxy.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
Have you tried it with no RedirPort setting at all? I have nothing set and it works fine. 80 is the default.
You mean, try like this?
"_RedirPort": 80,Either way, I get the same error.
-
@StuartJordan Self hosted SC is not horribly priced. Not as good as it used to be. But still a viable price.
Hosted is similar to other hosted solutions I believe. And is certainly higher than I would prefer.
I have legacy pricing for SC self hosted, so really hard to get better.
MC2 seems to actually do it.
-
Email works for now using Ubuntu Server 18.10 live installer. Does nodemailer requires packages that is not included with a minimal install of Fedora?
-
@black3dynamite said in Comparing MeshCentral 2 to ScreenConnect:
Email works for now using Ubuntu Server 18.10 live installer. Does nodemailer requires packages that is not included with a minimal install of Fedora?
Not sure, but unlikely.
-
Don't have the invite link on my install, I'm using the latest version apparently as well, any ideas?
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
Have you tried it with no RedirPort setting at all? I have nothing set and it works fine. 80 is the default.
I forgot to mention, my setup is using mongodb, not sure if that is related to the error!
-
@FATeknollogee When a port is busy, MeshCentral tries to bind to the next available port. So, since port 80 was busy, 81 was used. If you are on Windows, it's likely IIS is using port 80 already.
-
@StuartJordan said in Comparing MeshCentral 2 to ScreenConnect:
Don't have the invite link on my install, I'm using the latest version apparently as well, any ideas?
Is your SMTP set up?
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee When a port is busy, MeshCentral tries to bind to the next available port. So, since port 80 was busy, 81 was used. If you are on Windows, it's likely IIS is using port 80 already.
I've tried this on 2 separate installs & both times I get the same error.
Install is Ubuntu 18.10 -
@FATeknollogee said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee When a port is busy, MeshCentral tries to bind to the next available port. So, since port 80 was busy, 81 was used. If you are on Windows, it's likely IIS is using port 80 already.
I've tried this on 2 separate installs & both times I get the same error.
Install is Ubuntu 18.10netstat -tulpn | grep 80 -
@Ylian - Just curious is the "_" necessary in the config settings?
Ex: "_RedirPort" vs "RedirPort"
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee When a port is busy, MeshCentral tries to bind to the next available port. So, since port 80 was busy, 81 was used. If you are on Windows, it's likely IIS is using port 80 already.
I've tried this on 2 separate installs & both times I get the same error.
Install is Ubuntu 18.10netstat -tulpn | grep 80tcp6 0 0 :::80 :::* LISTEN 7566/node -
@syko24 said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian - Just curious is the "_" necessary in the config settings?
Ex: "_RedirPort" vs "RedirPort"
Any text after _ is ignored.
-
@black3dynamite said in Comparing MeshCentral 2 to ScreenConnect:
@syko24 said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian - Just curious is the "_" necessary in the config settings?
Ex: "_RedirPort" vs "RedirPort"
Any text after _ is ignored.
Ah so like an on off switch basically. Good to know. Thanks
-
@FATeknollogee said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee When a port is busy, MeshCentral tries to bind to the next available port. So, since port 80 was busy, 81 was used. If you are on Windows, it's likely IIS is using port 80 already.
I've tried this on 2 separate installs & both times I get the same error.
Install is Ubuntu 18.10@Ylian Any thing else I can try?
-
Just listing some additional differences between MC and SC:
ScreenConnect offers 2 factor authentication
(Email & SMS
Google Authenticator
YubiKey
Microsoft Authenticator
LinOTP
Duo Security "push" alerts)ScreenConnect has a lockout mechanism to prevent brute force attacks.
I have not seen these options in MC yet but possible feature requests.
-
@syko24 Yes, lockout and two-factor and both good ideas! Bit busy now, but that we certainly on the list.
-
@FATeknollogee Well, if port 80 is busy and MeshCentral is using 81 instead, try going to port 80 with a browser to see what is using it. You could also use a router and port map port 80 of your public IP address to port 81. That should work and you can ignore the warning. Not sure how much I can help with the freeing up of port 80
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@FATeknollogee Well, if port 80 is busy and MeshCentral is using 81 instead, try going to port 80 with a browser to see what is using it. You could also use a router and port map port 80 of your public IP address to port 81. That should work and you can ignore the warning. Not sure how much I can help with the freeing up of port 80
There doesn't seem to be anything using port 80
root@control:~# netstat -tulpn | grep 80 tcp6 0 0 :::80 :::* LISTEN 7566/node
