The ideal setup would have a firewall located between the machines and
router.  If you lock down the ports on the machine and just use it as a dumb
server you should be alright. The firewall comes in handy for blocking IP
spoofing and if your doing packet filtering for web (port 80)
vunerabilities.

Steve

----- Original Message -----
From: "Mark Stewart" <[EMAIL PROTECTED]>
To: "CF-Server" <[EMAIL PROTECTED]>
Sent: Thursday, December 13, 2001 11:00 AM
Subject: RE: Web Server location


> That's a good idea. Would a "good" configuration be behind a firewall
> anyway? I'm wondering how hosting companies do this.
>
> Mark
>
>
>
> -----Original Message-----
> From: Steve [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 13, 2001 10:35 AM
> To: CF-Server
> Subject: Re: Web Server location
>
>
> Try taking the firewall down and testing. Even though your firewall is
> probably configured correctly it can slow down a single T1 greatly.
> Instead
> of a firewall you can just lock down the ports on the machine and
> multihone
> it if it needs domain access.
>
> Steve
>
> ----- Original Message -----
> From: "Mark Stewart" <[EMAIL PROTECTED]>
> To: "CF-Server" <[EMAIL PROTECTED]>
> Sent: Thursday, December 13, 2001 10:28 AM
> Subject: Web Server location
>
>
> > Good Morning All,
> >
> > I've got a couple odd problems and I'm all out of ideas as to where
> the
> > problem might lay.
> >
> > Set-up: Win2K, IIS 5, 1/2 gig RAM, 60 gig HD, CF5, PIII 800Mhz - The
> Web
> > Server is connected by a full T-1 to the Internet and is physically
> > located behind a Cisco Rounter and a Firewall
> >
> > Traffic: Maybe 100 people per day. The app is a medium sized Extranet.
> > The Extranet is used for viewing documents (text, html and pdf's) Very
> > simple stuff. We do use session variables, but all are locked
> > appropriately. We use SQL Server 2000 which is located on a DB Server,
> > not the Web Server. About 98% of the queries are stored procedures.
> >
> > Problem: Clients complain that the Extranet is slow. We, of course,
> > don't see this problem when viewing internally since we're connected
> to
> > the Web Server through a full T-3. I also experience lag when viewing
> > the Extranet from home (I have IDSL 144K). One thing, in particular,
> > that I notice is that the blue status bar (when using IE) seems to
> hang
> > for about 2-3 seconds after the page has loaded. It doesn't matter
> what
> > page I'm viewing either. For example - I view a page with a lot of
> > content and then view a page with just a login form on it and the blue
> > status bar still hangs for the 2-3 seconds no matter what page I'm
> > viewing. Also, I keep receiving NT error 232 in the Web Server logs
> and
> > I can't seem to figure out where they're coming from.
> >
> > Are there any settings in either IIS or CF Admin that I should be
> paying
> > attention to? As for the 232 error - What should I look at to fix
> this.
> >
> > These problems are very frustrating because the powers that be here
> tend
> > to point their fingers at Windows, IIS and CF as the problem. I don't
> > feel that those things are the problem. If anything, they're not
> set-up
> > properly.
> >
> > Thanks in advance for all your help.
> >
> > Mark Stewart
> > Programmer/Analyst
> > CC3
> > Phone: 215.672.6900 x1332
> > http://www.cc3.com
> >
> >
> >
> >
> >
> >
> >
>
> 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. http://www.fusionauthority.com/ads.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with 
'unsubscribe' in the body or visit the list page at www.houseoffusion.com

Reply via email to