I am going to buy my own server and colocate this at a data center. This server is going to only host one website with Mysql as backend database. I notice there are 3 different Windows 2003 server, Web, Standard and Enterprise. I am leaning toward the Standard version. Can I use Window 2003 Standard Edition to run my the web server?
Im trying to setup FTP on Windows 2003 Standard. Multiple people will need access, the problem Im having is how do I make it to where certain ftp accounts only have access to certain folders and certain ftp accounts have access to the whole root directory of that folder?
For instance under websitefolder you have a folder called bobsfolder. I want bob to login and just be "jailed" to bobsfolder, but when websitefolderadmin logs in they have access to the root of websitefolder and all its subfolders.
I have a Windows VPS with Plesk panel. Windows Server 2008 R2 with plesk panel version 11.5.30.
I tried to change the default plesk panel port (8443) to eg (1234) without any success.
The steps i followed are the following: 1) Firewall -> Inbound rule -> allow for port 1234 2) Firewall, Disable inbound rule for port 8443 3) IIS, PleskControlPanel, Bindings: changed binding from 8443 to 1234.
Now i type on browser: [URL] .... and while its loading after some seconds redirects me to [URL] ...
With Windows 2003 server, there are comprehensive lists of what you need to do to secure the server before use. For Windows 2008, I wonder is there such a list? Or is it true as what I heard from Microsoft that it is already secured out of the box?
Anyone has any resources on the hardening or preparation of 2008 for server hosting uses?
This is my first dedicated and I am plugging away at it.I am running windows server 2003 web edition and I have my database, website, and ftp setup and everything is working so far. Now if you go to 184.108.40.206 my site that I'm working on will show up. My question is my domain and site that I am in the process of moving is hosted on a shared server on 1and1. Now I need that domain to point to that ip. Do I need to set up name servers on the server? If so can someone point me in th right direction.
We have two Windows Server 2003 machines as active directory controllers and DNS servers for our in-house operations. For our purposes, let's say the domain name is example.com.
Both servers have DNS, and example.com is stored in Active Directory to allow us to use the benefits this provides. Our issue is probably simple, but I'm not sure how to fix it.
Let's call server one EX1, and server two EX2. These have local IPs of 192.168.1.111 and 192.168.1.112, respectively.
We want example.com to be resolved to an external IP address (for web hosting), let's say 220.127.116.11. The problem is, the two domain controllers keep registering example.com with their internal IP addresses .111 and .112, so the DNS round-robins between 18.104.22.168 and the two internal servers, which aren't web servers.
Is there a way we can get those DNS controllers to stop registering their internal IPs as example.com?
i am starting up a buisness running my own web servers and the licensing system for windows Server 2003 standard is really confusing and i was wondering if someone could give a simple explaination if possible.
I will be using these servers for Plesk web hosting.
and with CALs if i am renting out Dedicated servers and they use win server 2003 would i pre install CALs on it or would customer do that.
I have a server running Win 2003 server at a data centre.Microsoft has released SP2 but mine is SP1.I have no access to the server physically and I wonder can I install SP2 using remote desktop?Will I get logout halfway?