Everything looks cool to me, although why not just use the IIS ftp, since
you are using it for the web server? One less thing to go wrong...
Make sure you kill all the default security holes for him (frontpage,
+.htr...), or he will call in a panic one day.
512 Megs is probably overkill too. Stick
This doesn't make much sense. He's willing to spend thousands of dollars on
hardware and software, then connect the system to the Internet via a shared
connection over a single T1 through a neighboring office??? If he can
afford occasional outages for minutes or hours at a time, this might be
ac
At 8:05 AM -0800 1/22/01, Terry Troxel wrote:
>I have a client who is planning on putting up his own server for his website
>and I would like some advice.
>
>His site is a private site for affiliates to compile & share various
>information on and will not be using ecommerce and will probably
>neve
Terry, I only have one suggestion. Security. Don't leave the most important
aspect to someone else. If something happens you can guarantee that the
response he will get from the other group who handles the firewall will be
"well, we never had any problems" (IE: It is not our problem). Get a
Watchg
4 matches
Mail list logo
