Re: Recommendations for Installing Exchange
From: Evan (yeah_at_right.com)
Date: 08/21/04
- Next message: Evan: "DNS Record(s) Needed for OWA?"
- Previous message: Omer maydan: "Re: ADC and migration"
- In reply to: Lanwench [MVP - Exchange]: "Re: Recommendations for Installing Exchange"
- Next in thread: Lanwench [MVP - Exchange]: "Re: Recommendations for Installing Exchange"
- Reply: Lanwench [MVP - Exchange]: "Re: Recommendations for Installing Exchange"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 21 Aug 2004 13:37:03 -0700
Ok, you've convinced me :). Exchange 2003 is required for
Outlook Web Access, right? Where can I find some good
information on how to set OWA up? Thanks for all of your
help.
>-----Original Message-----
>Evan wrote:
>> Where can I learn more about outlook web access? I would
>> like for these accounts to be accessable from outside of
>> the network as well. That is why I decided on POP3. It
is
>> more widely used.
>
>More widely used than a web browser?
>
>> As far as the relay restrictions you
>> mentioned, with Exchange 2003 will I be able to allow
>> users outside of my network who authenticate to send
mail?
>
>They wouldn't need it if they used OWA. If you decided to
let them use POP,
>they could use their own ISP's SMTP server for outbound
mail so you wouldn't
>even have to allow for authenticated relay (enabled by
default, but can be
>exploited by spammers if you don't have very good
password policies in place
>or enable guest, whatnot)
>
>> Will setting it up like that interfere with receiving
mail
>> from other mail servers? I had SMTP Virtual Server and
>> POP3 Services installed on Windows 2003, but I couldn't
>> get it to require authentication when accepting mail
from
>> users outside the network and at the same time allow
other
>> mail servers to deliver mail to my server. I was hoping
>> that would be a little easier to set up in Exchange.
>> Inside my network I want to be able to send and receive
>> mail both to and from outside the network (of course...)
>> without requiring integrated windows authentication,
>
>Not sure what you mean. Internal users will be
authenticated when they log
>into the domain - in Outlook, the only thing they should
have is the
>Exchange server and the Outlook Address Book services -
no POP, no PST.
>
>> but
>> it's not really a huge problem if I have to enable
>> authentication for inside the network as well. And then
>> when outside the network (at home or something) I want
to
>> be able to send and receive mail, but have it require
>> authentication. I couldn't seem to manage this with just
>> the standard POP3 and SMTP services included with w2k3.
>
>Again, why not OWA? Much better option. Implement SSL so
it's
>secured/encrypted.
>>
>>> -----Original Message-----
>>> On Fri, 20 Aug 2004 19:41:33 -0700, "Evan"
<yeah@right.com> wrote:
>>>
>>>> On my network I have 1 PDC w/ a few other services
running
>>>> such as Software Update Services and Symantec
Antivirus
>>>> Corp. I also have a Secondary DC that runs a
restricted
>>>> ftp/web server. Both servers are running Windows
Server
>>>> 2003. There are a little over 30 client machines all
>>>> running XP Pro. All clients and servers are behind a
>>>> FreeBSD based firewall connected to the internet
through a
>>>> business DSL line. I would not like anyone be able to
>>>> easily gain access to any of my systems or
information.
>>>> However, there is no sensitive information, and so if
they
>>>> did it would not be a HUGE problem.
>>>> My question is this... I've heard that mail servers
can be
>>>> very insecure. I am thinking about installed Exchange
>>>> 2003. I just wanted to get some input on where I
should
>>>> deploy it. I would really like to put it on my
primary DC,
>>>> but if it is going to be a big security risk I can
put it
>>>> on my secondary. If even putting it on my secondary
isn't
>>>> recommended, I can get a third computer to run it off
of,
>>>> but I'd really like to not do that unless it will
>>>> compromise the network too much to do otherwise.
Another
>>>> question I had is whether or not the computer I
install it
>>>> on can stay behind the firewall (with ports 110 and 25
>>>> forwarded of course), if I need to put it in the DMZ,
or
>>>> if it needs to go in front of the firewall altogether.
>>>> I have never really used exchange before, and I'm
sort of
>>>> looking forward to it, but I wanted to make sure
about all
>>>> of this first. I would really like to do this tonight
so
>>>> that it can be up and running by tomorrow, so if
anyone
>>>> can quickly respond I would very much appreciate it.
Thank
>>>> you for your help and your time.
>>>
>>>
>>> Exchange isn't insecure.
>>> Exchange is "best practice" placed on a member server
but can go on a
>>> DC if you're pushed. For the few numbers you're
talking about (unless
>>> they all have huge mailboxes & your server is small)
you shouldn't
>>> have a problem.
>>> Exchange does not go in a DMZ
>>> Yes with the TCP 25 forwarded to the Exchange box
(which is relay
>>> secure by default so don't mess unless you're sure
what you're doing)
>>> Why 110? Are you giving POP access? Outlook Web Access
on E2K3 is an
>>> excellent solution, and you get ActiveSync for your
iPAQ users as
>>> well.
>>> .
>
>
>.
>
- Next message: Evan: "DNS Record(s) Needed for OWA?"
- Previous message: Omer maydan: "Re: ADC and migration"
- In reply to: Lanwench [MVP - Exchange]: "Re: Recommendations for Installing Exchange"
- Next in thread: Lanwench [MVP - Exchange]: "Re: Recommendations for Installing Exchange"
- Reply: Lanwench [MVP - Exchange]: "Re: Recommendations for Installing Exchange"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
