Screenconnect needs VPS?

mrapoc

Well-Known Member
Reaction score
105
Location
Shropshire
Hi all

I'm right in thinking that screenconnect will not install on my shared web hosting and I will need a VPS at least?

If that's the case, I'll be having a go at hosting myself at home - Got 76mb/20mb connection at home anyway.

Thanks
 
I host it on my SBS 2012E R2 box, but I had it on my W7 machine for quite some time and had zero problems. Excellent program and excellent support.

It doesn't take too much bandwidth, you'll have more than enough.
 
Save the money and host it yourself; your connection is plenty fast. I host in my home office and use dyndns to keep the host name the same even when my IP changes.
 
2 seconds on Google: http://help.screenconnect.com/System_requirements
System requirements
ScreenConnect is a self-hosted web application that can be installed on a computer, server, virtual machine (VM), or virtual private server (VPS). It is quite flexible and works well on a variety of operating systems. There are three pieces to the ScreenConnect application:

The Server - The central web application which establishes the connections between the Guest (Customer) and Host (Technician). This is the application you are downloading from the ScreenConnect site.
The Host Client - The host client is deployed on-demand to the person Host connecting to the session or meeting, and will contain features like screen recording, toolbox, chat and more.
The Guest Client - In a remote support situation this is the client software deployed to the computer that will be controlled by the Host. For meetings this will be the client that allows the participant to see the Host screen.

Server requirements
Supported Operating Systems

Windows
Windows XP SP2+
Windows Vista
Windows 7
Windows Server 2003
Windows Server 2008
Windows Server 2012
It's not been updated recently but I have no problems with 8 or 8.1.
 
Cheers all - I just assumed by server it would run on my web hosting. Nether-the-less will be another thing learnt :)
 
Bang it into s w7 box and I'll run fine, get w static IP or dnydns and setup a sub domain of your website to it.

Mine runs from my shop with a 7/1 connection without an issue

Dom
 
I have a windows VPS running Plesk and to make it work on remote.allstarit.com.au i installed screenconnect on port 8040 but to get it to load i put a portforward in iis from remote.allstarit.com.au:8040 to port 80. However if i were to put port 8040 on any website on my server it would also load the screen connect. So far its ok and its easy to change screen connect port if need be.
I feel vps runs better and has better uptime than if i had it at home or in office.
 
Got mine on a dell W7, 2gb of ram dual core machine I had spare. Using no-ip to give my dynamic ip a hostname, then using configuration I have a subdomain pointing to that hostname :)
 
Got mine on a dell W7, 2gb of ram dual core machine I had spare. Using no-ip to give my dynamic ip a hostname, then using configuration I have a subdomain pointing to that hostname :)

That's essentially what I did initially, then I purchased a nice .support domain to go with it :)

(in case you missed it, the .support TLD was made available a month or two ago, so you can now have something nice and easy for EUs to remember like mycompany.support).
 
Last edited:
I have mine on an HP microserver Win7 "NAS" I use for media at home.

I'll be honest - it's not ideal IMO. I need remote functionality when on holiday abroad and if there is a connection or server problem caused by my router or Windows box then there's no way of fixing it.

I'd prefer it if the service was hosted by the suppliers really - like Logmein or TeamViewer etc.

I also find ScreenConnect just a bit buggy. I find I sometimes lose connections to permanent connections I've set up and when I get on those machines to find out why, I discover the SC service has just stopped. I've improved the situation by going into Services and setting the service restart options manually but obviously that's not ideal and doesn't solve it 100% of the time.

Overall it's a good app but it's still not quite as slick and reliable as the big names IMO.
 
I also find ScreenConnect just a bit buggy. I find I sometimes lose connections to permanent connections I've set up and when I get on those machines to find out why, I discover the SC service has just stopped. I've improved the situation by going into Services and setting the service restart options manually but obviously that's not ideal and doesn't solve it 100% of the time.

Same here. Though I find that the problem affects XP machines mainly, so I'm not too concerned, since the number of those that I support is quickly diminishing.
 
I'm sure I've seen several posts before about setting the restart parameters for the service after installing it for a permanent connection in an attempt to stop the service timing out on the client PCs.

It's mentioned here by the look of it: http://www.technibble.com/forums/showthread.php?t=48933&page=3

I've had it happen quite a few times - machines that I've installed a perm connection on stop connecting from the client end. I've reset my server etc and it doesn't make any difference. When I've got around to going to the clients I can see that the SC client simply isn't running anymore.

I'll report the next one but it seems to be quite specific to the PC it's installed on.
 
Last edited:
Hate to bring a thread back from the dead. But I'm giving screen connect a shot .

My first thought was throw it on a 5 dollar a month Digital Ocean VPS. I got my VPS provisioned and SSHed in, threw new updates at it and started the install. It Installed fine, but then I got an error message and saw that this was an ASP app and was running on Mono. I have a lot of respect for the Mono Project, but this still feels like a bit of a hack to me. And If I am going to do this the right way with a VPS, I want to do everything right.

I went back to the drawing board. Ended up setting up a Windows Server 2012 R2 T2.micro instance with AWS. it's free for the first year. The only gotcha is you have to make sure you open up the proper inbound ports in the Instance Security policy.

Just for kicks and testing purposes I've got a session running right now from my Desktop computer to a Windows 8 Tablet that is sitting on desk that I am setting up for a client. So far so good.
 
Last edited:
I've got it running on a CentOS 6 VPS with a small provider (soon to be moving it to Linode VPS that I've been testing). No dependency issues. Installed and works fine. I've upgraded it a couple of times without any major issue either. One minor issue was that after upgrading from 4.2.x to 4.4.x, the installer script didn't restart ScreenConnect (had an error message, can't remember), but I restarted the service and it came up okay.
 
Back
Top