Re: ICF problems win Win2003
From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 11/22/03
- Next message: Dmitry Korolyov [MVP]: "Re: 2003 - revert back to base security policy"
- Previous message: Jerry Vaz: "RPC_C_IMP_LEVEL_IMPERSONATE does not work beyond machine boudaries"
- In reply to: Vincent Haakmat: "Re: ICF problems win Win2003"
- Next in thread: S. Pidgorny
: "Re: ICF problems win Win2003" - Reply: S. Pidgorny
: "Re: ICF problems win Win2003" - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 22 Nov 2003 05:51:13 -0800
Have you considered Windows Small Business Server 2003? It is a sweet
package that integrates Windows Server 2003, Exchange Server 2003, OWA,
Remote Workplace, and your own AD + Client-side setup, all configured and
ready to go, scaling up to 75 users, and costs less than what you've already
purchased...
If you gave it a server with two NICs, knew the list of client PC names, it
would have done all this configuration automatically with a couple wizards
by now, totally secured.
Personally, I think every company that doesn't have an IT Dept nor budget
should look at Windows Small Business Server 2003 because it packs a lot of
well integrated solutions. Heck, for my own home network I'm using SBS
because it's useful for 2-75 users. :-)
You don't need to take my word for it. Look around technology publications
and you'll see that they've been raving about Windows Small Business Server
2003.
-- //David IIS This posting is provided "AS IS" with no warranties, and confers no rights. // "Vincent Haakmat" <vhaakmat@ipx.nagicosus.com> wrote in message news:%2357cXyDsDHA.2360@TK2MSFTNGP09.phx.gbl... Ok... makes sense... We have a firewall from Netgear, but according to my ISP, I need to get a better one. They recommended CISCO, but it is too expensive for our business (only 50 PCs). Can anyone recommend something better that won't break our wallet? Thanks Vincent "David Wang [Msft]" <someone@online.microsoft.com> wrote in message news:uY0OHGBsDHA.1196@TK2MSFTNGP12.phx.gbl... > If this server is multi-homed, then just enable ICF on the Public NIC and > not on the Private NIC > > If this server has only one NIC and both the server and LAN are not behind a > firewall from the Router/Gateway, what you are trying to do is pretty > insecure and defeats running a firewall on the server. > > There are two general topologies that you can consider for small-time > servers. > 1. The server is dual-homed (i.e. "Gateway") on the broadband connection and > LAN, with a firewall running either on the server's external NIC or on any > local router-device upstream from the web server > 2. The web server is an internal LAN server, and the Gateway must have logic > to either forward requests based on ports, host header, or IP address to and > from this internal LAN server > > Both topologies allow unrestricted access by your LAN clients to the LAN > server's interface, and highly restricted external access to your server's > public interface. > > -- > //David > IIS > This posting is provided "AS IS" with no warranties, and confers no rights. > // > "Vincent Haakmat [393242]" <vhaakmat@nagico.com> wrote in message > news:ewIqSrrrDHA.560@TK2MSFTNGP11.phx.gbl... > I have an exchange server 2003 running on my win2003 server. Because it is > directly connected to the net i wanted to use ICF. But if I do, the other > computers on the LAN can't connect to it. WHich ports (UDP-IP) do I need to > enable so that the can still access normal file and print services from it? > > >
- Next message: Dmitry Korolyov [MVP]: "Re: 2003 - revert back to base security policy"
- Previous message: Jerry Vaz: "RPC_C_IMP_LEVEL_IMPERSONATE does not work beyond machine boudaries"
- In reply to: Vincent Haakmat: "Re: ICF problems win Win2003"
- Next in thread: S. Pidgorny
: "Re: ICF problems win Win2003" - Reply: S. Pidgorny
: "Re: ICF problems win Win2003" - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
