Risks of hosting a public website directly on my network?

Question

I want to configure IIS on the old XP box that I have on our local network so that I can post some Silverlight materials that I use on it, so I show them to others on the Internet. I already have a public IP address that runs directly through my firewall and directly to this machine, and sometimes I use Remote Desktop to log in to this machine and do some different work when I'm at home. It has drive letters mapped to data folders on the server, but the data is not located directly on this computer. I do not want to expose my entire network to risks that I do not understand. So, will it be safe if I allow people to use a public IP address to get into this machine with their web browser?

Answer 1

So, will it be safe if I allow people to resort to a public IP address to get into this machine using their web browser?

You always increase your level of risk by providing access to trusted resources, so “safe” is a relative term. In this case, you risk a dangerous level of risk by placing it in the same place where you would like to conduct safe transactions (for example, logging into your bank account).

However, you can take some expensive low-cost protective measures:

• Since you are behind a router, your router can do double duty and act like a firewall. Make sure that only the appropriate ports are open.
• , . , -.
• , ; .
• .
• , .

Answer 2

. , , . DMZ . , VPN RDC.

Answer 3

:

• , , .
• , DoS-. , , , - , . , () .
• DMZ, , . , IP DNSBL, .

- .

​​ № 3

Answer 4

IIS 5.1 10 , 2 .

IIS 5.1 XP . IIS , XP.

Answer 5

, , , , , "".

Personally, I would suggest getting external hosting, thereby keeping your own network more secure and letting the hosting provider worry about updating the software, keeping attackers and maintaining the network. It is not very expensive and will relieve most of the headache that you have to deal with.