Xampp in windows server 2008

The video you directed me to in your first link was no help im afraid, it only shows how to install it on the server, which i have already done. The second link was to a website i had already looked at, and as i stated in the orignal post, i've already tried adding in the Listen thing in the config file. All i know is that IIS wouldnt have been turned on if its default is off, as the server is only used for data currently.

Also try this link. I cant seem to find IIS on the server, but i did find some security configuration wizard which im going to see if that will allow me to open the port up to listen on :D. Didnt even think of that angle as you would think the port would already be opened on a server OS :. Server will have the Windows Firewall enabled by default and unless you add the web server role, port 80 will stay closed. You will most likely need to open the proper port on the Windows Firewall. Search In.

Share More sharing options Followers 0. Let me move this to the EC2 forum to see if you can get a better response than what I can provide. Re: xampp configuration in windows server r2 instance Posted on: Mar 20, AM.

I haven't used Windows in a few years, and I've never used it as a server. So no, I haven't. Maybe there's something in one of these searches that might help?

If you could double-check your Security Group settings that the EC2 instance is running under, it should look something like the image I've attached to this post. Re: xampp configuration in windows server r2 instance Posted on: Mar 31, AM. Re: xampp configuration in windows server r2 instance Posted on: Apr 3, PM. Have you opened port 80 for 0. Have you tried to disable windows firewall? Re: xampp configuration in windows server r2 instance Posted on: Apr 22, AM.

Hi guys, has anyone figured this out.. I have the same issue.. I looked apache log and couldn't see any error I forgot to disable windows firewall for public profile and apparently that seems to be the default one it's using! Edited by: Firen on Apr 22, AM. If you access localhost from inside the browser on the remote machine, what happens? It's always directing me to localhost :S Can't figure out, what i'm doing wrong :S Apache httpd.

It contains the configuration directives that give the server its instructions. Do NOT simply read the instructions in here without understanding what they do. They're here only as hints or reminders. If you are unsure consult the online docs. You have been warned.

NOTE: Where filenames are specified, you must use forward slashes instead of backslashes e. If a drive letter is omitted, the drive on which httpd. It is recommended that you always supply an explicit drive letter in absolute paths to avoid confusion. ServerRoot: The top of the directory tree under which the server's configuration, error, and log files are kept. Do not add a slash at the end of the directory path.

If you point ServerRoot at a non-local disk, be sure to specify a local disk on the Mutex directive, if file-based mutexes are used. If you wish to share the same ServerRoot for multiple httpd daemons, you will need to change at least PidFile. Change this to Listen on specific IP addresses as shown below to prevent Apache from glomming onto all bound IP addresses.

Listen It is usually good practice to create a dedicated user and group for running httpd, as with most system services. ServerAdmin: Your address, where problems with the server should be e-mailed. This address appears on some server-generated pages, such as error documents. This can often be determined automatically, but we recommend you specify it explicitly to prevent problems during startup. ServerName localhost Deny access to the entirety of your server's filesystem.

DocumentRoot: The directory out of which you will serve your documents. By default, all requests are taken from this directory, but symbolic links and aliases may be used to point to other locations. The Options directive is both complicated and important. Possible values include: debug, info, notice, warn, error, crit, alert, emerg. The client will make a new request for the document at its new location.

ScriptAlias: This controls which directories contain server scripts. ScriptAliases are essentially the same as Aliases, except that documents in the target directory are treated as applications and run by the server when requested rather than as documents sent to the client.