Re: Exchange Front-end/Back-end question

Ah, I will user different drive letters then...Thank you.

"Ben Winzenz [Exchange MVP]" wrote:

EVS2 would either need different drive letters, or I believe that you can
also use mount points instead of drive letters.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Alex" <Alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4C0024C1-D403-443B-822A-442C0ADA0BE6@xxxxxxxxxxxxxxxx
I have one last dumb question for you.
I am creating 3 node back end clusters (AAP)
One thing I can't find any information from any where is drive letters...

This is my settings
Node1, Node3 are prepered owner of EVS1, EVS1 has Drive Q,G,H, and I
Node2, Node3 are prepered owner of EVS2, EVS2 has Drive Q and 3 more disks
(Q is the quorum disk, of course)

Can I assign EVS2's data drive's letter as G,H and I (same as EVS1) or
should I choose different direve letters so it won't conflict with EVS1?
for
example J,K and L ???

Thank you.


"Ben Winzenz [Exchange MVP]" wrote:

You should be fine to run R2 as your back-end cluster as long as the
Exchange Service pack version is not greater than on your FE.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Alex" <Alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:97E34A8B-53ED-47CA-9996-FA554394670D@xxxxxxxxxxxxxxxx
I created front end server as you suggested, and it is working just
fine.

I have one more question for you.

My front ends are windows 2003 STD+ SP1, is it ok to create back ends
clusters with W2k3 R2 ENT? or should I use W2k3 ENT ?

Thank you.

"Ben Winzenz [Exchange MVP]" wrote:

Creative routing :-)

So what you might want to do is actually the opposite.

Set the default gateway on your 192.168.x.x NIC (so that it knows how
to
get
out to the Internet). That takes care of outbound mail.

Then, create a static route to make sure that the server knows how to
get
to
the 10.10.x.x network.

Something like:
route add 10.10.0.0 mask 255.255.0.0 10.10.0.1 IF 10.10.x.x

This command says that for the 10.10.0.0 network with a subnet mask of
255.255.0.0, use a gateway of 10.10.0.1 (or whatever your gateway is
on
that
network) and use the Interface 10.10.x.x (the IP of the other NIC).

Try it and see if that does what you want.

Then again, I could be totally off base with this!

If it doesn't work, I'd suggest also posting this in one of the
network
newsgroups to see if anyone there has thoughts around this.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Alex" <Alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:994A83F4-25ED-41A0-94C1-01E38AD43E89@xxxxxxxxxxxxxxxx
Yes that is right
192.168. is NBL

what I want is

For OWA: Internet -> firewal -> 192.168 -> 10.10 -> 192.168. ->
firewall ->
internet
For RPC: Internet -> firewal -> 192.168 -> 10.10 -> 192.168. ->
firewall ->
internet
Outgoin email: 10.10 -> firewall -> internet
Incoming email: Internet -> firewal -> 192.168 -> 10.10

I don't think it is really possible, is it?


"Ben Winzenz [Exchange MVP]" wrote:

It makes things confusing because you are talking about 2 separate
private
IP ranges. After re-reading, it sounds like this is the way things
are
designed. Let me know if Iam off-base.

Internet -> Firewall -> 192.168.x.x (VLAN for NLB) -> 10.10.x.x
(Internal
Network)

Is that right?

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Alex" <Alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:25D49FB9-B3CC-4E24-9237-3D5B2C5CA742@xxxxxxxxxxxxxxxx
Oh I thought OWA will work through the 192.168.x.x, and 10.10.x.x
will
work
for RDP and traffic between FE and BE. Do I need an extra
firewall
or
something?


"Ben Winzenz [Exchange MVP]" wrote:

Well, it means that 192.168.x.x won't know how to get to
anything
that
isn't
in it's local subnet, so yes, that should mean that the OWA
requestsshould
be sent out through the 10.10.x.x network. Isn't that what you
wanted?

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Alex" <Alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BB7ECD91-C39C-476A-AB72-93C97F4AB760@xxxxxxxxxxxxxxxx
It means 192.168.x.x will not be able to send any outgoing
traffics,
only
10.10.x.x can..
It that right? so even the OWA request will be sent out
through
the
10.10.x.x. network?

Thank you.

"Ben Winzenz [Exchange MVP]" wrote:

That should be handled by the default gateway. The NIC with
the
10.10.x.x
adress should have a default gateway defined. The other
(private)
NIC
should not. This should take care of both scenarios.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Alex" <Alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1D863734-F220-43A5-ADE4-6282D3481FAD@xxxxxxxxxxxxxxxx
Hello
I have a question about the NBL FE and clustered BE
exchange.

I am currently setting up 2 FE (NLB) and 3 node cludtered
BE
exchange.
I understand all your replies to Jermaine, however there is
something I
still don't understand.
Here are my 2 questions.

1. Each Exchagne FE servers has 2 NICs, the first nic is
setup
for
Unicast
NLB (using VLAN, to prevent port flooding -> 192.168.x.x),
and
second
NIC
has
internal network's IP(10.10.x.x).
VLAN can communicate to the internal netowork and vice
versa.
What I don't understand is how to make sure EXFE (each nlb
node)
to
talk
to
EXBE via internal IP only and not using VLAN ip? Will DNS
have
2
IPs(
+PTR
record) for each EXFE nodes? and make everything so
disoriented?

2. My EXFE has SMTP connector and it is set to bridgehead,
which
IP
will
it
use to send email to internet? VLAN IP(192.168.x.x) or the
internal
IP
(10.10.x.x)? or both?

Thank you.
"Ben Winzenz [Exchange MVP]" wrote:

Most likely.

Do you have any SMTP Connectors defined? If your Front
end
server
is
not
defined as the Bridgehead (on the SMTP connector), then
your
cluster
mailbox
server will happily send e-mail directly out to the
internet.

The only potential upside of creating an smtp connector
and
having
outbound
traffic route through your Front end would be if you are
experiencing
mail
delivery issues due to a failed Reverse dns lookup. Since
your
Mailbox
server cluster is not published to the Internet, it will
never
pass
a
rDNS
lookup. Routing through your FE server would allow you to
create a
PTR
record that matches the name of the MX record.

I'm not sure how to answer the other question. Can you
explain
what
you
mean by OWA being designated on FE and not BE? ALL
Exchange
2003
servers
have OWA enabled by default. The distinction that a FE
server
.

Relevant Pages

  • Re: Exchange Front-end/Back-end question
    ... Ben Winzenz ... Read my blog! ... out to the Internet). ... create a static route to make sure that the server knows how to ...
    (microsoft.public.exchange.admin)
  • Re: Exchange Front-end/Back-end question
    ... You should be fine to run R2 as your back-end cluster as long as the ... Ben Winzenz ... out to the Internet). ... create a static route to make sure that the server knows how to get ...
    (microsoft.public.exchange.admin)
  • Re: OMA server name???
    ... Ben Winzenz ... Read my blog! ... so, do you have a Front-end server, or just a Back-end server? ... OMA, OWA, and everything is usually the same address, although from ...
    (microsoft.public.exchange.admin)
  • Re: backup exchange server
    ... Read my blog! ... Ben Winzenz wrote: ... /disasterrecovery switch requires that the server have the same name. ... Exchange org allowed per forest. ...
    (microsoft.public.exchange.admin)
  • Re: Logon Change
    ... Ben Winzenz ... Read my blog! ... Under the Exchange Virtual Server, ... Exchange 2000 was installed on a Windows 2000 server. ...
    (microsoft.public.exchange.admin)
Quantcast