Bad idea to run File server as Exchange server, too?

Posted on 2002-05-28
Last Modified: 2010-03-05
Our company is contemplating moving to an Exchange server.  (We currently use POP mail from the host of ouwebsites.)  The consultants who are helping us with the project have suggested getting a new server that will run Exchange (with OWA) for our corporate email, while also serving as the file server.  Any issues with this?  It's been suggested by someone else in the company that this constitutes a serious security risk, given that it will be publicly accessible (in order to provide remote access to email via the Web).  

We will most likely put the Exchange/file server behind a (Cisco PIX) firewall, if that makes any difference.  We won't run websites on it, and it will only serve one other application, a payroll database (small company, 35 employees).  We hope to go ahead and start purchasing hardware and software by Friday, so that's more or less my deadline.  Thanks in advance for your comments.  
Question by:jonathanv_00
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
  • 2
  • +3
LVL 23

Expert Comment

ID: 7041623
The firewall is a plus.  If you have the firewall configured properly and haven't missed anything, you should be okay.  I wouldn't want to stake my job (and possibly freedom) on that, though.  If someone skirts around the firewall or it is not configured to block them as it should, they will have access to your payroll information.  That could possibly send the installer and company higher-ups to jail.  I would go for a separate, non-connected server for the payroll app.
LVL 28

Expert Comment

ID: 7041796

Expert Comment

ID: 7042028
I agree with slink9 on this one. Although you are a small business, storing company sensitive information like payroll, on your Exchange server, to save money on hardware, may only cause you problems in the future.

As for the comment about not running any websites on it, where is OWA going to be installed? Typically this will run on your exchange server, and will require the installation of IIS. So your E\xchnage server will expose (by default) ports for the following services HTML,POP3,IMPA4, and NNTP, not to mention the standard NT ports that are used.

Depending on the firewall you use, it is recommended to statically assign a forwarding for ONLY those ports you want to have access to to your exchange server, in your case port 80.
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 7042234
Ah, thanks, folks.  Good point about the OWA - I wasn't even thinking of that as a website, but obviously you have to have something to host the site if you're going to give folks web access.  (I'm a bit slow in the mornings.)  

Thinking out loud, or in print . . . we will have an extra server when this gets done - the old NT 4.0 file server.  Could that be configured to be the OWA server (it has IIS on it already)?  Or would it be a better idea just to leave the payroll app on that machine, separate from the Exchange/file server?  I had thought of using it to host an Intranet for the company after we move to Win2K and Exchange.

Thanks very much -- there will be points for each of you when we're finished.
LVL 23

Expert Comment

ID: 7042242
Separate.  The intranet isn't a bad idea.  
LVL 55

Expert Comment

ID: 7042442
You could apply an extra level of security above the normal OWA username/password by securing the webserver with Secure Computing's SafeWord. A hacker would have to guess the one-time pseudo-random password the token generates from the users PIN as well as their username and password.

See if you can access my OWA account at

Expert Comment

ID: 7042863
What version of exchange are you going to?  If it is Exchange 2000 to install the web access on a different server you have to install another copy of exchange on the server.  Here is a white paper on doing this.

With many of our clients we put the owa on a port different from 80.  We do this mainly to stop worms that work on port 80 from entering the server.

It looks like you would be a good fit for Small Business Server 2000 unless you have more that 50 connections.  This is much cheaper that buying one copy of exchange and of copy w2k plus the licences.


Accepted Solution

MCummings111400 earned 200 total points
ID: 7042876
I would leave your payroll on the NT4 box, you could also host an intranet on there as well. (The optimizations for a fileserver and web server are pretty much the same) Exhcnage and OWA on thier own box. And if you really need it a sepreate fileserver machine. Exchange Servers and fileservers do not optimize the same way. So I would see 2-3 servers in your case.

1) FileServer - Coporate files and Payroll DB
2) Exchange Server
3) Web Server - OWA and Intranet

Author Comment

ID: 7057625
Thanks to all for your replies.  Look for some separate point questions going out to a few of you.

We're going to stick with the consultants' plan as far as putting Exchange and the file server on the same machine. We just upped the processor and improved the RAM quite a bit over the Dell machine that they spec'd for us; we'll be getting a white box that's much more powerful for about 2/3 the cost.  That should make up for some of the Exchange licenses, too -- unfortunately, there's something about SBS that doesn't like multiple sites (we have three offices).

But I do like the different port idea, Steinmoto. 100 points consolation for that.  AndyAlder - you always have very good advice, so I'll look into that security solution.  Thanks again to all.

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question