AoN

The server didn't error this time, but, http://us.defranks.net/ didn't work. Sorry if this is frustrating for you, but, I am trying to make it work, and I am glad to be getting your support in it. ^^

I'm using the same one I've been using since I first made this thread, Quick 'n Easy FTP Server. I have tired his suggestion, and it errored with a timeout error everytime. As for the port in the program, I have already confirmed that it is there.

Sure, but, last time I tried to put in a full VHost listing like that, it errored the server everytime it started (Remember when I couldn't get it to start and stay started, yea, that was the problem...). I'll give it a try though, when I can to my home PC to do it... I wish I could get that FTP thing working, so I can do this stuff from anywhere! ^^'

I'm using IE because it is basic, and it rarely errors out on me.

Yea, the problem is, the domain is on another host, and they won't transfer.

I have already made the exemptions in the firewalls, and I have put it in the URL in IE. It either times out or says it can not connect.

Alright, thank you fro all your help so far. ^^

Okay, I finally got my own sub-domain to work, but Cox does block almost all the standard ports (they want me to pay them to host my own files...damn them). Due to this, I now my a sub-domain URL, but I am still required to include a port number. Can anyone provide me with the means of keeping my sub-domain, but getting it to work without a redirect, frameset, or the port number included? http://us.defranks.net:81/ This is just a temp. domain until I can get it to work, then I'll put the same settings on my full-time domain. After having done research, and forcefully attempting to make it work, I've realized I wasted my time trying to make an A Record work with a port, hence the port in the sub-domain.

Pardon my language, but that would seriously suck. Edit: I just contacted my ISP, and they block port 80, and all ports related to FTP in anyway...DAMN THEM! Because of this, I have attempt using a port that I see no reason for them to block, 90, and it still isn't working.

I have disabled my firealls, and just as a precaution, I've put in port forwarding on them, and port forwarding on my router.

It is what makes sense to me, as it is only posts I've made before the last down-time that I can't edit.

I think it has something to do with the weekly maintance you do.

I tried making it work with port 21, but it wouldn't connect.

No, there isn't anything I want to change, it is just bugging me that I can't seem to edit my old posts. <-- Likes having the edit option.

I figured out what was wrong! I added in a VirtualHost incorrectly and it was conflicting with the default one. ^^' Also, why can't I edit my previous posts?

Well, as soon as I fix this issue with it opening an then closing, I'll try it. ^^ Edit: Well, I fixed the server issue, and now that I'm back behind a router, I'm having issues. My guess is that it is just me having screwed up on the port forwarding, so, I screenshot the Router Admin and the FTP Admin pages. FTP_Port_Help.bmp

So I have to set-up the ports and all again?

How would that file just appear? The server was running flawlessly for nearly a week when this started happening... Either way, the file does not exist on my PC, other than in the UniServer folders.

Does noone have any clue as to how to fix this?

Chances are, that your connection is through a router located somewhere in a restricted area of the school, or something...and I highly doubt that you will be permitted to change it, nor do I believe they will do it for you.

You are probably behind a router, if you at college, and you have to set the router to forward the port. I suggest changing the access port to 81 in the W:/usr/local/apache2/conf/httpd.conf Instead of having it read Listen 80 make it read List 81. If you have port forwarded it, then restart the server, and test it out. If there is still a problem, then explain it in a little more detail. If you switch to another port, it doesn't have to be 81, the new access address would be http://xxxx:(Port)/xxxx/

Maybe no, I might yet have a problem. ^^' It all depends on if it will run with port forwarding on my router, and if it'll run after the web server actually starts and stays started.

Sweet, but, pointless right now. I have another problem, a little bigger...the server shut-down the moment it is started. I don't know why, and I don't think I screwed up any of the config files, as all the editing was based off the instructions given. I've tried the Disk Start.vbs and the Server_Start.bat, both give the same results. Sorry for have so many problems. ^^'

lol, They can put stuff in there, it is just a dummy server, for now, and I have back-ups everywhere, so, it wouldn't be too big of a deal. Thanks again for the help. ^^

No, that account is pointed FAR from the webroot, and it was a temp account to test it. ^^ Thank you very much for your help, and I just hope it'll still work with my router, when I get home...in a few days... Edit: lol, that is so funny!