Home Office Network structure query

May 24, 2010 at 08:40:00
Specs: Windows Server 2003

I currently have 3 servers in my home office. One is my domain controller and IIS running 2 websites. One is a database server and also host a remote backup server on port 8080 and 433 for SSL. (I intentionally change the port from 443 to 433 to avoid conflicts).
I also have another server (currently offline) which will host a website on port 80 when it is finished.
Basically, what I am trying to achieve is having separate servers for each function. (I have 5 spare servers too). I currently rely on my router to forward traffic to the relevant machine based on TCP/UDP port numbers but I would like to know if this is possible using some software on my domain controller.
I do not know much about MS Proxy server but someone said this might work.
Can someone please tell me how I would go about doing this? I would like to have the software running on my domain controller and then distribute traffice accordingly but it must take in to account that I will have up to 5 websites each using port 80. I currently split these using host headers in IIS but my router obviously doesnt support this.

I would really appreciate any help/suggestions people may have.

Many thanks in advance.


See More: Home Office Network structure query

Report •

May 24, 2010 at 09:17:55
I'm a firm believer in using a router for a router, not a server for a router. My suggestion is to buy a router that supports the type of traffic you need.

How do you know when a politician is lying? His mouth is moving.

Report •

May 25, 2010 at 08:09:46
I agree with guapo 100%

Moving routing from a router to a server is not logical. Moving it from a router to a DC is just silly!

Sorry, I don't mean to be rude but, when it comes to DC's, you should be offloading any/all services you can off of them. For instance, you're running websites on your DC. If it were me, and I had 5 other servers kicking around, the ONLY thing the DC would be doing, is acting as a domain controller and running DNS.

I would move DHCP and IIS (and all web pages) off of it and on to a member server.

All websites should be on the same server running IIS. All incoming port 80 traffic should be sent to this machine. Then IIS can take care of directing which traffic goes to which web site.

I'm curious, since you have 5 spare servers kicking around, do you have a second, redundant DC ready to take over should your first DC fail? If not, you should do that too.

Report •

May 26, 2010 at 01:29:57
Many thanks to both of you for your replies.
I run a business from my garage and has only been running for 12 months and I am just working out a way of improving everything. I agree with you about the DC but as I am not serving an office full of users, the impact of the services all being on one machine at the moment is pretty low.
I will take your comments in to account and redesign.

Thanks again.

Report •

Related Solutions

May 26, 2010 at 07:23:40
One must always plan for growth. Doing so from the begining means less hassles in the future.

Should your business take off, you may find you're happy you did plan, and deploy, appropriately at the begining.

No matter what else you do, you need to get all your website's on one server. Unless you're clustering for redundancy and load balancing on multiples.

Report •

Ask Question