Re: Joining web server to SBS domain - any pre-cautions?
- From: Leythos <void@xxxxxxxxxxx>
- Date: Fri, 11 Jul 2008 18:50:37 -0400
In article <Orqdb534IHA.776@xxxxxxxxxxxxxxxxxxxx>, "Mike" <none> says...
Hi All,
We are running SBS 2003 Standard SP2 with exchange.
I'm trying to plan for joining our web server (Server 2003 Std. installed)
to our SBS domain. The web server is live and hosting our website at the
moment.
I don't know enough about IIS to foresee any prolems that may arise with the
account profile changeover. Any thoughts to consider or suggestions would be
much appreciated. Thanks so much in advance.
Putting ANY webserver on the same network as your company files is a
very bad idea and is a very good way to get hacked and then compromised.
You should have a REAL FIREWALL APPLIANCE, not just a NAT Router.
Real firewalls provide multiple physical networks that are isolated from
each other and only permit traffic by user created rules.
A single public IP can provide HTTP access for the DMZ Network and also
provide HTTPS access to the LAN without the outsiders knowing the
difference.
If you firewall has a DMZ and it's in the same Subnet as the LAN, then
it's not a firewall.
A typical LAN would be 192.168.3.1/24 with
a typical DMZ being 192.168.8.1/24
They are isolated from each other by default.
The only rule would be:
Allow HTTP LAN > DMZ (web erver IP)
Disallow ANY DMZ > LAN
--
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@xxxxxxxxxx (remove 999 for proper email address)
.
- Follow-Ups:
- References:
- Prev by Date: Re: Question about SMB2k3 and Exchange server
- Next by Date: NTBACKUP Error
- Previous by thread: Re: Joining web server to SBS domain - any pre-cautions?
- Next by thread: Re: Joining web server to SBS domain - any pre-cautions?
- Index(es):
Relevant Pages
|
