In the first part we got the remote server VPS up and operating. It is a windows 2012 64 bit operating system, so try and load 64 bit programmes into it.
The next part is seeing that we can connect to the server through our browser, rather than Remote Desktop Connection.
Aside for Setting up a Web Site on the Server
Note: If you are going to do a web page setup then you would need to do a web setup on the remote server- look to YouTube for examples of that. This is a good video to start with for installing relevant programmes:
For the website setup you will also need a domain name. If you go to FREENOM you can get a free domain name, it ends with .tk, .ml, .cf, .ga, .gq but they are free. See this Post Free Domains from FREENOM.
Back to the Setup
The first thing, because of the security settings that we used on the previous example, lets us , through the ICMP rule that will allow ECHO reply, so we can PING the server from our PC on the command line.
And you see the ping works
Next, lets just drop the firewall in windows, turn it off completely to begin with (we will change this later)
This part of Specific setup for OpenMAINT
In this example I am looking to set it up for a remote openMAINTinstance. I use these for testing (as well as ones on my localhost).
openMAINT is an open source application for the management of building, installations, movable assets and related maintenance activities. I have a number of posts on setting it up , see this LINK. It has poor documentation and I have been writing posts on how to set it up.
We need tomcat up and running on that server, so that we can test the connection.( Tomcat is a virtual server on the server, it runs the programmes for OpenMAINT (All a bit confusing, I still haven’t figured it out, but it works- See Wiki on the subject))
Next, we need to copy the Java SDK files and Apache Tomcat files across (see blog on setting up OpenMAINT on local server) from PC C drive to Server C: drive
Then run the Java files and move the Tomcat files to C:\
Then we need to add CATALINA_HOME, JAVA_HOME & JRE_HOME to environmental variables in control panel.
Then fire up Tomcat. I use shortcut icons on desktop for the startup/shutdown batch files. Once Tomcat server is running, we can then look to see it in the browser from our PC
So we are now talking to our server through our web browser.
We now have to go and re-instate the firewall and allow rules to only let stuff in on the 8080 port. We need to create rules for incoming and outgoing for this port.
Now that you have firewall on, go back to browser and refresh link to IP$:8080 and see if Tomcat page comes up again, if it does then that is great.
You can now load all the files up to the VPS to run.
This is how you would do it using the C:/ drive on your PC to C:/ Drive on the server. This is the process you’d use to get the link to your personal PC. Note, it is better to put all the files I want to copy in one directory and then copy that across. I have found it tends to be faster than individual files at a time. Also you can walk away and have a cup of coffee while it is doing that, as transferring files in this way can be quite SLOW. You also need your computer to be on all the time while the file transfer is taking place.
Sometimes it is easier to open the Browser and directly download programmes to the Server.
An alternative method is to use FILEZILLA to copy files between your PC & Server.
You need to setup an FTP (File Transfer Protocol) connection on your site. See:
I have found issues with getting FILEZILLA to link to the AWS instance, here is a video on setting it up: