Statistically speaking...

November 03, 2007 05:59AM
> In effect, it will only be online when I want it to be, i.e., when me and my friends need access to it. It won't be 24/7. And when it does get hacked (and I notice), I'd just re-install. It's not my main pc, so that wouldn't be a disaster. <br>> <br>> Thanks for the info, I'll give it a try. <br> <br>If you take a standard windows box you buy from the store (which wouldn't have the most recent patches) and attach it to the internet with no firewall it will be taken over in about 7 minutes. Of course, you're only opening one non-standard port, but you're running IIS and you're not familiar with securing it. Depending on how concerned you are about your other machines, I might unplug them such that they are never connected to the network while your .NET machine is also plugged in. Once someone is past your router/firewall they can/will take over whatever else is on your network eventually. <br> <br>Disclaimer: I tend to be more cautious/paranoid than most people.
Subject Author Views Posted

Getting a server accessible on the internet

Leprechaun 302 November 03, 2007 03:42AM

Port Forwarding and ISP restrictions

Rade 245 November 03, 2007 04:18AM

Oh, also

Rade 241 November 03, 2007 04:21AM

None taken :)

Leprechaun 202 November 03, 2007 05:21AM

Statistically speaking...

Rade 218 November 03, 2007 05:59AM

Yeah me too

Leprechaun 216 November 03, 2007 04:28PM

That's not even vaguely true but ok.

Death_Claw 208 November 06, 2007 04:23AM

The SANS Institute disagrees with you

Rade 299 November 06, 2007 04:33PM

Because, having worked with hundreds of windows machines over a decade...

Death_Claw 250 November 07, 2007 03:49AM

Install Bitdefender, its $60, then use port forwarding.

Death_Claw 260 November 06, 2007 04:34AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 29
Record Number of Users: 59 October 25, 2015
Record Number of Guests: 341 February 12, 2018