subject:"Relay\?\?\?"

Exchange 2010 relay settings

2013-05-14 Thread Tom Miller

I have two Exchange 2010 SP3  CAS servers.  They are front-ended by several
load balancers.  In front of that we have a spam and a/v appliance that
filters e-mail first for inbound and outbound.

This morning I noticed that Internet mail was going out, but not coming in.
 The load balancers did not report any errors with connectivity.  The spam
appliance reported that it could not send messages to Exchange as no
resources were available on the Exchange side.

Looking at the CAS servers, I saw entries in the app logs:   receive
connected relay server_name rejected an incoming connection from IP address
x.x.x.x.  The maximum number of connections per source (20) for th is
connector has been reached by this source IP address.

I restarted CAS servers and they started to accept mail again, although I
do see that message again.

I know I can change this via the MaxInboundConnectionPerSource and
MaxInboundConnectionPercentagePerSource.  But I'd really like to know how
to properly troubleshoot this.  The relay connectors on the server are
limited to specific IP addresses such as our copiers, notification systems,
and the load balancers.  The App log referred specifically to the IP of the
primary load balancer.  Other than enabling verbose logging on that
connector, how else would one troubleshoot this?

Thanks,
Tom

---
To manage subscriptions click here: 
or send an email to 
with the body: unsubscribe exchangelist

RE: Exchange 2010 relay settings

2013-05-14 Thread Michael B. Smith

Your load balancer is reporting their address instead of the source IP address. 
That might be something you want to change.

Otherwise, I'm not sure why you think you have a problem? It sounds as if you 
are just getting a lot of email.

From: Tom Miller [mailto:tominyorkt...@gmail.com]
Sent: Tuesday, May 14, 2013 1:03 PM
To: MS-Exchange Admin Issues
Subject: Exchange 2010 relay settings

I have two Exchange 2010 SP3  CAS servers.  They are front-ended by several 
load balancers.  In front of that we have a spam and a/v appliance that filters 
e-mail first for inbound and outbound.

This morning I noticed that Internet mail was going out, but not coming in.  
The load balancers did not report any errors with connectivity.  The spam 
appliance reported that it could not send messages to Exchange as no resources 
were available on the Exchange side.

Looking at the CAS servers, I saw entries in the app logs:   receive connected 
relay server_name rejected an incoming connection from IP address x.x.x.x.  The 
maximum number of connections per source (20) for th is connector has been 
reached by this source IP address.

I restarted CAS servers and they started to accept mail again, although I do 
see that message again.

I know I can change this via the MaxInboundConnectionPerSource and 
MaxInboundConnectionPercentagePerSource.  But I'd really like to know how to 
properly troubleshoot this.  The relay connectors on the server are limited 
to specific IP addresses such as our copiers, notification systems, and the 
load balancers.  The App log referred specifically to the IP of the primary 
load balancer.  Other than enabling verbose logging on that connector, how else 
would one troubleshoot this?

Thanks,
Tom

---
To manage subscriptions click here:
or send an email to
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
or send an email to 
with the body: unsubscribe exchangelist

Re: Issue with load balancers, relay, autodiscover

2013-02-20 Thread Alexander Rose

First error message is normal, it is because of the way the test is done,
it first try an autodiscover test with your domain name in the URL. If your
domain is contoso it will try first
Autodiscover to
https://contoso.com/autodiscover/autodiscover.xlmhttps://mycompany.com/autodiscover/autodiscover.xlm

I get the same error myself but autodiscover works fine from outside.

On Wed, Feb 20, 2013 at 12:36 PM, Tom Miller tmil...@sfgtrust.com wrote:

This past weekend I inserted two Barracuda load balancers into my
Exchange 2010 environment. With a few exceptions, they seems to be working
well.

** **

I need some suggestions from the list on a few things:

** **

External autodiscover is failing, then succeeding. In the log when I get
test connection, I see this:

** **

Autodiscover to https://mycompany.com/autodiscover/autodiscover.xlmfailed
(0x800c203)

Autodiscover to
https://autodiscover.mycompany.com/autodiscover/autodiscover.xml starting*
***

GetLastError = 0; httpStatus=200

Autodiscover to
https://autodiscover.mycompany.com/autodiscover/autodiscover.xml succeeded

** **

Any ideas on this one?

** **

The second issue I have is relay. I have a relay for our various
environmental, copiers, BusinessObject systems, and other
equipment/systems. That worked fine with I used Windows NLB on the CAS
servers. Now that I’m using the load balancers, the relay works only for
internal recipients. If a relay is destined for external e-mail addresses,
it fails. This is particularly an issue for our BusinessObjects systems,
which send out reports to non-internal addresses. Any thoughts on this one?

** **

Thanks,

Tom

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

1 2 3 4 >

1 - 100 of 370 matches

Mail list logo