I am wondering if anything has any ideas, I'm at a dead end Link to comment Share on other sites More sharing options How is the server configured RAM-wise, boot. Posted January 29, Posted January 31, Create an account or sign in to comment You need to be a member in order to leave a comment Create an account Sign up for a new account in our community. Register a new account. Sign in Already have an account?
Sign In Now. My question is, my server is secure from attackers? If not, what can i do to secure the server. Rich Rumble. Most Points The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics.
Join our community to see this answer! Unlock 1 Answer and 7 Comments. Andrew Hancock - VMware vExpert. See if this solution works for you by signing up for a 7 day free trial.
If you need help with this, please see our KnowledgeBase article Using telnet. Installing, configuring, and troubleshooting third-party applications is outside the scope of support provided by Media Temple.
Please take a moment to review the Statement of Support. You can use this same technique to check if Port is blocked as well. I am a programmer in an argument with our sys admin.
Currently on our webserver not in a dmz we have port 80 blocked and the https port i believe unblocked. The admins reasoning is that it secures the server. Thank you very much. There is much more to securing a server than just blocking a few ports. Typically on a server, you implement a "default deny" policy that blocks traffic to all ports and then you exempt only the specific ports that you need.
So if you don't need ports 80 and , then by all means, they should be blocked. You are most likely correct in saying that there are no known vulnerabilities directly against port What you need to ask yourself is whether or not there are any vulnerabilities in whatever application is listening on those ports.
That is where security issues happen It sounds like your aim is to force users of your application to only use the HTTPS channel via port Rather than outright blocking port 80, I would highly suggest opening that port up and just doing a redirect to HTTPS for any clients that connect there.
That way, users can type in "example. This is not a necessity, but it is generally a good practice to improve UX. It is a lot more about the services listening on that port than the port itself.
Even Skype can listen on port 80 caused a lot of headaches setting up WampServer before I found out what was using the port! It's a good idea not to open any ports that aren't needed. If there aren't any exploits for IIS out right now and I doubt it , there might be in the future.
0コメント