Add second sourcetransportserver to send connector

I created a send connector to force TLS to a particular email domain. However, for some reason, I need to manually add the second sourcetransportserver. Anyone know the correct PS syntax to add the second sourcetransportserver?
Correct setup showing both -
My send connector with only one -

Hi,
In addition to the above cmdlet, you can set the SourceTransportServers to your send connector via EAC.
EAC -> mail flow -> send connectors -> double click the Send Connector -> scoping -> click "+" underneath Source server
For your reference:
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

Similar Messages

Exchange 2007 Send Connectors

Hello,
I'm relatively new to administering Exchange and I had some questions on Send Connectors. We send mail to a few different domains that usually 75% of the time will generate a message saying:
Delivery is delayed to these recipients or distribution lists:
This message has not yet been delivered. Microsoft Exchange will continue to try delivering the message on your behalf.
Delivery of this message will be attempted until 1/9/2014 9:31:13 AM (GMT-05:00) Eastern Time (US & Canada). Microsoft Exchange will notify you if the message can't be delivered
by that time.
Sometimes messages will make it to the intended recipients and other times not. Most of the time they are just regular emails without any attachments on them. I'm not exactly sure how connectors work, but I'm thinking that I can set one up to tell exchange
that it should route these certain emails to that domain. Is this the correct thought process on how a send connector would work and are there any ramifications I need to worry about if I set up a second or third send connector?
I apologize if this is naïve or doesn't make sense. Please let me know if you need more information. We run Exchange 2007 on Windows SBS 2008.
Thank you.

Hi,
It seems that it could be a reverse DNS lookup issue. I recommend you check if the reverse DNS record is configured correctly.
If it is ok, I suggest you enable logging at your send connector. Then check the log to see if you could find some clues.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Import csv file in Address Spaces in an Exchange 2007 Send Connector

hello , i must put more than 300 domains in the addres space of a Send connector.
is possible have a csv file with the 300 domains and a powershell script to import this file in the address space of one send connector?
example csv file :
cepsa.es
repsol.com
parsi.es
Regards
Thansk in advance
mcse 200x + mesaging 2000 2003 2007 2010

Hi
At First, you CSV should be set as the format like
Name
cepsa.es
repsol.com
parsi.es
If you would like to set a new Send Connector. you can simply do
New-SendConnector -Name ConnectName -AddressSpace ((Import-CSV <PathOfCSV>) | ForEach {$_.Name})
If you would like to add to a Send Connector that already existed, Please run
$al = (Get-SendConnector -Identity <ConnectName>).AddressSpaces
$al += (Import-CSV <PathOfCSV>) | ForEach {$_.Name})
Set-SendConnector -Name ConnectName -AddressSpace $al
Cheers
Zi Feng
Zi Feng
TechNet Community Support
The first script is still working as it should under Exchange 2013 when a send connector is created for the first time.
The second part of adding (or removing) address spaces from an existing send connector was a little bit trickier.
the following script did it:
Get-SendConnector "ConnectorName" | Set-SendConnector -AddressSpace ((Import-CSV <PathOfCSV>) | ForEach {$_.Name})
Watch out! this command also removes domains which are not present in the csv file!

Configure send connector for exchange online protection

Hello Forum members,
I am trying to configure send and receive connectors for Exchange 2010 to route
on-premises mailboxes to Exchange OnLine Protection. The "help" info MS provides
is for Ex 2013 - and the EAC GUI and config does not lend a close fit to using the 2010
Exch Management Console. How can I configure connectors to properly connect to the Exchange Online Protection?
I have seen where the ip addresses are posted, etc. I am unclear how to configure the properties on the SBS 2011/EX 2010 server.
Any tips will help,
Thanks,
Eric H.
Network and Server Installs

Hello Wesleyhe,
You cannot use AD anything with EOP - if you mean exchange on-line protection.
you have to set a smart host on the SBS server to connect to EOP, you may need to add the EOP server ips to your network config
on the SBS server. the smart host line (for the send connector on SBS server) is something like: yourdomainname-com.mail.protection.outlook.com.
Then you need to configure the outside ip for your SBS server access in the EOP admin area.
Hope this helps.
eholz
Network and Server Installs

Multiple Smart Hosts within a send connector issue

Our organization has 2 smart hosts that our hub transport can use for outbound e-mail. We have created a send-connector that lists both IPs. As expected, if one is unavailable it just uses the other. What I have noticed is that as long
as both Smart hosts are online Exchange uses a round-robin format with the 2 smart hosts for anything going out that send connector. What I am looking for is to somehow disable the round-robin feature. I would like all mail going out this send
connector to always use just 1 of the 2 smart hosts and ONLY use the second if the first is unavailable for some reason. Is this possible?

Our organization has 2 smart hosts that our hub transport can use for outbound e-mail. We have created a send-connector that lists both IPs. As expected, if one is unavailable it just uses the other. What I have noticed is that
as long as both Smart hosts are online Exchange uses a round-robin format with the 2 smart hosts for anything going out that send connector. What I am looking for is to somehow disable the round-robin feature. I would like all mail going out this
send connector to always use just 1 of the 2 smart hosts and ONLY use the second if the first is unavailable for some reason. Is this possible?
Not really possible with the native Exchange capabilities, no.
If you have a load balancer, you might be able to leverage that and have Exchange send to single namespace that is handled by the balancer.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Is send connectors fault tolerant for source servers?

Hi!
I am in the process of applying SP3 on our Exchange 2010 environment. I have two Hubs that are both specified as source servers in our send connector to the internet. I just want to double check that when I'm applying SP3 to one of the server, that the other
server is taking care of sending all emails.
My fear is that it is only load balancing so every other email will fail to be sent because on of the hubs are down.
So can I safely update one of the servers and mail will be still sent from the other? Or should I just remove it as a source server from the send connector?
I will of course redirect incoming emails to the hub that are up at the moment.
Thanks!

Hi ,
Based on my knowledge while doing service pack upgradation on the hub transport severs there is no need to remove that particular server from source server list on the send connectors.
In addition to that mail flow will load balanced across both the hub transport servers listed on the source server list .So on such case if anyone of the server in send connector's source server list is not funtional for the particular point of time then
it will prefer the second funtional server to send emails to internet.Finally i would like to say that there wouldn't be an loss in emails.
Thanks & Regards S.Nithyanandham

Send Connector, Removing one Source Server

I have one send connector. I have two exchange servers not in HA, when I attempt to remove one of the source servers, email backs up in the que and I get this error
451.4.4.0 Primary target IP address responded with 451.5.7.3 cannot achieve exchange server authentication
I then have to add the other server back for email to go out again. Both servers are listed as source servers on the send connector. But leaving the one I want, its not routing email through that server. Do I have to restart any of the services after making
this change?

Here is the output
PS] C:\Users\administrator.PHDMI\Desktop>Get-SendConnector | FL
AddressSpaces : {SMTP:*;1}
AuthenticationCredential :
Comment :
ConnectedDomains : {}
ConnectionInactivityTimeOut : 00:10:00
DNSRoutingEnabled : False
DomainSecureEnabled : False
Enabled : True
ErrorPolicies : Default
ForceHELO : False
Fqdn : owa.xxx.com
HomeMTA : Microsoft MTA
HomeMtaServerId : xxxEXCH
Identity : XXX
IgnoreSTARTTLS : False
IsScopedConnector : False
IsSmtpConnector : True
LinkedReceiveConnector :
MaxMessageSize : 10 MB (10,485,760 bytes)
Name : xxx
Port : 25
ProtocolLoggingLevel : None
RequireOorg : False
RequireTLS : False
SmartHostAuthMechanism : None
SmartHosts : {outbounds6.obsmtp.com}
SmartHostsString : outbounds6.obsmtp.com
SmtpMaxMessagesPerConnection : 20
SourceIPAddress : 0.0.0.0
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {xxxEXCH0, xxxEXCH}
TlsAuthLevel :
TlsDomain :
UseExternalDNSServersEnabled : False
I added the xxx to remove our company name. I am trying to remove xxxEXCH0, but when I do email gets stuck in the que for outgoing. Now I didnt restart any services after removing EXCH0 as a source server.

Two Send Connectors

Hi,
We have one MS-Exchange 2010 server and we have two hosted domains name it as abc.com and xyz.com (these domains are hosted at different ISPs) now i have configured SMTP connection to forwards all emails from exchange to abc.com and to forward emails from
Exchange to abc.com requires Basic Authentication so i have configured it in send connector and all abc.com users are able to send their emails to other recipients.
But the xyz.com users in our exchange server are not able to send their emails to external recipients because send connect is trying to authenticate to abc.com and mails are getting bounce. so i want to create second connector to forward xyz.com emails from
my exchange server to xyz.com domain for authentication purpose and forward it further.
In this case how exchange will recognize that xyz.com send connector is this and abc.com send connector is that ?
Please provide me some solution on this?
Arjun V.

Create the two send connectors with different name spaces.
one should be the catch all, for all email, with the * namespace. The other is for the specific domain xyz.com.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2010 - Send Connector High Availability

Hi All,
I performed a successful migration a few years back from a single node Exchange 2003 server to a two node Exchange 2010 organisation with a DAG and Kemp load balanced CAS array. The solution works well and when we simulate a site failure
I am able to get the second node to handle all mail functions.
The one problem I have though is that I have to manually disable the send connector on the primary server in order for the one on the secondary server to be in use. I should explain that I have two send connectors as I do not want the secondary server
to be used unless the primary server is down or the route is unavailable. I realise that Exchange 2010 does not know whether the SMTP route is down or not so will just continue trying to use the send connector from the primary server (until I tell it
not to by disabling it).
My question is how do I get this to happen automatically? Does anyone else have an example of how this could be done or use a PowerShell script to achieve this? I guess a script could check the route and disable the send connector on the primary
server if necessary, but how would one do this?
Any help greatly appreciated.
Rob

Hi,
According to your description, your secondary send connector cannot be automatically used when the first one is down. If I misunderstand your meaning, please feel free to let me know.
If yes, I’d like to confirm if the settings of the secondary one is same with the first one and we can check the connectivity logs including diagnostic information for Healthy Server Selector.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/ff634392(v=exchg.141).aspx
Thanks,
Angela Shi
TechNet Community Support

TS4268 i cant add second email on face time

hello,
i can't add second email adress on face time on my iphone 5s and on my apple mc book,and ipad

Hi bogdan1974,
Thanks for using Apple Support Communities. This article explains how to view the list of addresses useable by FaceTime:
iOS and OS X: Link your phone number and Apple ID for use with FaceTime and iMessage
http://support.apple.com/kb/HT5538
On iOS devices, find out which addresses are enabled with FaceTime and iMessage by tapping:
Settings > Messages > Send & Receive > You can be reached by iMessage at:
Settings > FaceTime > You can be reached by FaceTime at:
On OS X, find out which addresses are enabled:
In Messages, choose Messages > Preferences > Accounts. Select iMessage in the left column. Your contact preferences should appear under "You can be reached for messages at:."
In FaceTime, choose FaceTime > Preferences. Your contact preferences should appear under "You can be reached for calls at:."
If you're unable to add an email address for use from there, please reply and let me know any error messages you are receiving or at what step exactly you are unable to continue.
Cheers,
- Ari

Send connector from exchange 2007

Currently since I have both environments up, I see that Exchange 2013 is using the send connector that was created in my exchange 2007 environment. Will this send connector go away once I bring down my exchange 2007 environment? Shoould I create
a new one for Exchange 2013?

Hi
From what i have seen running ex2010 and upgrading to 2013 it stayed (exchange 2013 is clever :-)). you can just modify your send connector and make sure that the settings are for your exchange 2013 server.

How to send email to a SMTP server over a secure channel using STARTTLS setting of a send connector (Exchange and SMTP server are in the same domain)

I’m trying to send email using exchange send connector STARTTLS setting to the SMTP server. I have read multiple documents on configuring TLS for send connector, but they talks about outbound connections to internet facing servers. My Exchange 2013 and SMTP
server is in the same domain (let’s say A.com) and I’m creating dummy domains on my SMTP server (e.g.
[email protected],
[email protected] ) and their respective send connectors on the exchange server end. In the smart host section added the IP address of the SMTP server and in the scoping section added the SMTP domain address (e.g. dummy1.local ). In the FQDN field, added
the FQDN of the exchange server 2013 which certificate is enabled with SMTP service.
Could you tell me a step by step procedure, where I’m going wrong or any extra settings needs to added?
Presently, it is giving me an error that 530 5.5.1 TLS encrypted connection is required.
Note: I’ve created the Microsoft CA certificates for the SMTP and exchange servers and imported them in the personal certificate container. In which, the exchange certificate is created with FQDN name of the server and enabled for the SMTP service.
I’m using OPENSSL certificate for making the SMTP server TLS enabled. (let me know, if I need to import the OPENSSL certificate anywhere on the exchange end)?
Thanks!

-IgnoreSTARTTLS is set to false on the send connector properties.
I'm trying to established a HTTP over TLS connection. I'm not using mutual TLS between these two server.
The send connector protocol logging is attached as below,
2014-09-22T20:09:45.468Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,2,10.219.3.74:24939,10.219.3.73:25,<,220 SMTP.A.local Welcome (MTA version),
2014-09-22T20:09:45.546Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,3,10.219.3.74:24939,10.219.3.73:25,>,EHLO Exchange.A.local,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,4,10.219.3.74:24939,10.219.3.73:25,<,250-SMTP.A.local Exchange.A.local OK,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,5,10.219.3.74:24939,10.219.3.73:25,<,250-SIZE,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,6,10.219.3.74:24939,10.219.3.73:25,<,250-8BITMIME,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,7,10.219.3.74:24939,10.219.3.73:25,<,250-BINARYMIME,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,8,10.219.3.74:24939,10.219.3.73:25,<,250-PIPELINING,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,9,10.219.3.74:24939,10.219.3.73:25,<,250-HELP,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,10,10.219.3.74:24939,10.219.3.73:25,<,250-DSN,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,11,10.219.3.74:24939,10.219.3.73:25,<,250-CHUNKING,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,12,10.219.3.74:24939,10.219.3.73:25,<,250-AUTH SCRAM-SHA-1 GSS-SPNEGO DIGEST-MD5 CRAM-MD5 NTLM,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,13,10.219.3.74:24939,10.219.3.73:25,<,250-AUTH=SCRAM-SHA-1 GSS-SPNEGO DIGEST-MD5 CRAM-MD5 NTLM,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,14,10.219.3.74:24939,10.219.3.73:25,<,250-STARTTLS,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,15,10.219.3.74:24939,10.219.3.73:25,<,250-DELIVERBY,
2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,16,10.219.3.74:24939,10.219.3.73:25,<,250-MT-PRIORITY,
2014-09-22T20:09:45.640Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,17,10.219.3.74:24939,10.219.3.73:25,<,250 ENHANCEDSTATUSCODES,
2014-09-22T20:09:45.655Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,18,10.219.3.74:24939,10.219.3.73:25,>,STARTTLS,
2014-09-22T20:09:45.671Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,19,10.219.3.74:24939,10.219.3.73:25,<,220 2.7.0 Ready to start TLS,
2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,20,10.219.3.74:24939,10.219.3.73:25,*,,Sending certificate
2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,21,10.219.3.74:24939,10.219.3.73:25,*,CN=Exchange.A.local,Certificate subject
2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,22,10.219.3.74:24939,10.219.3.73:25,*,"CN=DC-CA, DC=A, DC=local",Certificate issuer name
2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,23,10.219.3.74:24939,10.219.3.73:25,*,63E7E70100000000000B,Certificate serial number
2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,24,10.219.3.74:24939,10.219.3.73:25,*,CAEB1200CDF49715E5F2E4B8315EFDDC01F8F945,Certificate thumbprint
2014-09-22T20:09:45.780Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,25,10.219.3.74:24939,10.219.3.73:25,*,Exchange.A.local,Certificate alternate names
2014-09-22T20:09:46.654Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,26,10.219.3.74:24939,10.219.3.73:25,-,,Local
2014-09-22T20:09:46.669Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,0,,10.219.3.73:25,*,,attempting to connect
2014-09-22T20:09:46.685Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,1,10.219.3.74:24940,10.219.3.73:25,+,,
2014-09-22T20:09:46.701Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,2,10.219.3.74:24940,10.219.3.73:25,<,220 SMTP.A.local Welcome (MTA version),
2014-09-22T20:09:46.701Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,3,10.219.3.74:24940,10.219.3.73:25,>,EHLO Exchange.A.local,
2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,4,10.219.3.74:24940,10.219.3.73:25,<,250-SMTP.A.local Exchange.A.local OK,
2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,5,10.219.3.74:24940,10.219.3.73:25,<,250-SIZE,
2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,6,10.219.3.74:24940,10.219.3.73:25,<,250-8BITMIME,
2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,7,10.219.3.74:24940,10.219.3.73:25,<,250-BINARYMIME,
2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,8,10.219.3.74:24940,10.219.3.73:25,<,250-PIPELINING,
2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,9,10.219.3.74:24940,10.219.3.73:25,<,250-HELP,
2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,10,10.219.3.74:24940,10.219.3.73:25,<,250-DSN,
2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,11,10.219.3.74:24940,10.219.3.73:25,<,250-CHUNKING,
2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,12,10.219.3.74:24940,10.219.3.73:25,<,250-AUTH SCRAM-SHA-1 GSS-SPNEGO DIGEST-MD5 CRAM-MD5 NTLM,
2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,13,10.219.3.74:24940,10.219.3.73:25,<,250-AUTH=SCRAM-SHA-1 GSS-SPNEGO DIGEST-MD5 CRAM-MD5 NTLM,
2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,14,10.219.3.74:24940,10.219.3.73:25,<,250-STARTTLS,
2014-09-22T20:09:46.732Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,15,10.219.3.74:24940,10.219.3.73:25,<,250-DELIVERBY,
2014-09-22T20:09:46.732Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,16,10.219.3.74:24940,10.219.3.73:25,<,250-MT-PRIORITY,
2014-09-22T20:09:46.732Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,17,10.219.3.74:24940,10.219.3.73:25,<,250 ENHANCEDSTATUSCODES,
2014-09-22T20:09:46.810Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,18,10.219.3.74:24940,10.219.3.73:25,*,,sending message with RecordId 52652004081667 and InternetMessageId <[email protected]>
2014-09-22T20:09:46.810Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,19,10.219.3.74:24940,10.219.3.73:25,>,MAIL FROM:<> SIZE=7653 BODY=BINARYMIME,
2014-09-22T20:09:46.810Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,20,10.219.3.74:24940,10.219.3.73:25,>,RCPT TO:<[email protected]>,
2014-09-22T20:09:46.825Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,21,10.219.3.74:24940,10.219.3.73:25,<,530 5.5.1 A TLS-encrypted connection is required,
2014-09-22T20:09:46.950Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,22,10.219.3.74:24940,10.219.3.73:25,<,503 5.5.1 unexpected RCPT command,
2014-09-22T20:09:46.981Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,23,10.219.3.74:24940,10.219.3.73:25,>,RSET,

How do I Add second monitor to ALL in One ENVY23 that has a HDMI port

How do I Add second monitor to my ALL in One ENVY23 that has a HDMI port the computer has Win 8 Model #: 23se-d494
Product #: F3D93AA#ABA
Serial #: [edited Serial Number by Moderator]
Software Build #: 14AM1HRA601#SABA#DABA
Service ID #: 20140521
PCBRAND #: HP

Here are the specs for your HP ENVY TouchSmart 23se-d494 All-in-One Desktop Computer. Based the specs, the HDMI port on the side of your computer is an INPUT only. This model doesn't have a video output of any kind.
1 - Controls 2 - HDMI In port (model dependent)
You will need to purchase and use a USB-to-video adapter such as the EVGA UV Plus+ UV39 (or any of the many other adapters on the market) to connect an external display to your computer. I personally use and recommend the EVGA UV Plus+ UV39.
If you have any further questions, please don't hesitate to ask.
Please click the White KUDOS "Thumbs Up" to show your appreciation
Frank
{------------ Please click the "White Kudos" Thumbs Up to say THANKS for helping.
Please click the "Accept As Solution" on my post, if my assistance has solved your issue. ------------V
This is a user supported forum. I am a volunteer and I don't work for HP.
HP 15t-j100 (on loan from HP)
HP 13 Split x2 (on loan from HP)
HP Slate8 Pro (on loan from HP)
HP a1632x - Windows 7, 4GB RAM, AMD Radeon HD 6450
HP p6130y - Windows 7, 8GB RAM, AMD Radeon HD 6450
HP p6320y - Windows 7, 8GB RAM, NVIDIA GT 240
HP p7-1026 - Windows 7, 6GB RAM, AMD Radeon HD 6450
HP p6787c - Windows 7, 8GB RAM, NVIDIA GT 240

What are the correct Send Connectors settings in Exchange 2013

Hi
I'm new to exchange, successfully setup a lab with 2 cashub roles and 2 mailbox roles. I am trying to set the send connectors settings, because I've not been able to send nor receive external email via owa. Since I'm separating the exchange roles, my mailbox
servers only use internal IP settings and cannot resolve external DNS. I'm thinking I need to tick, proxy through CAS for it to work? any suggestions?

Hi
Can you please let us know what version of Exchange that you are using
"I'm new to exchange, successfully setup a lab with 2 cashub roles and 2 mailbox roles"
- Because Exchange 2013 does not hold hub role.
" I am trying to set the send connectors settings, because I've not been able to send
nor receive external email via owa."
It would be great if you could answer few questions so that people can help you out here
Are you able to send emails internally without any issues with Outlook ? If not can you paste the errors.
What error you are getting while trying to send emails through owa . Can you paste the errors.
If you are looking for steps to create new send connector please follow below technet article
http://technet.microsoft.com/en-us/library/aa998936(v=exchg.150).aspxFeel free to post your comments/errors you received to proceed
further
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

How to create send connectors for multiple sites in the same domain?

Current Scenario:
We have 2 offices, 1 in London and 1 in India. Both are in the same domain and are connected via VPN. Both have their own separate Exchange 2003 server. Each location sends out their mail via the Default SMTP Virtual Server on their exchange server through
their local ISP. There are no Send connectors created currently.
We have now installed an additional Exchange 2010 server with Hub, CAS and Mailbox roles at the London site. Internal mail flow between the sites seems to be working fine.
I believe the Exchange 2010 needs a Send connector to send out mail to the internet. However as soon as we create a Send connector on Exchange 2010, mail from the older 2003 servers at both sites start to flow out from the exchange 2010 server. This is not
optimal for our India site since their outgoing mail now has to flow via the VPN to London and out via the new server.
How can we configure it so that each server sends outgoing mail independently?
Thanks

Hi,
In India site, you can create a SMTP connector which point to the local ISP.
Thanks.
Niko Cheng
TechNet Community Support

Add second sourcetransportserver to send connector

Similar Messages

Maybe you are looking for