Send Connector missing

This is the fix -

The send connector has to be given the name shown below in order for it to work:

Windows SBS Internet Send MYSERVERNAME

(MYSERVENAME needs to be the name of your server and all in caps)

If it isn't named like that......it doesn't work and you get the message that the connector is missing in the SBS Console. Fixing the network won't fix this, nothing fixes it except giving it the correct name when you configure a new send connector in Exchange Management.

A very simple fix and why can't Microsoft just say that in their KB articles!!!

> On Saturday, August 22, 2009 2:56 PM Ace Fekay [MCT] wrote:

> Hi Dave,
>
> I would not suggest to change it in the services file, and I recommend and
> suggest to put that back to its default.
>
> Rather you would set your smarthost FQDN in your internet Send connector at
> the Org level, then use PowerShell to set the port number, such as:
>
> Set-SendConnector -Identity "YourConnectorName" -Port 3535
>
> Look at the following link for the command to see what I mean:
> http://social.technet.microsoft.com/...d-8d925d6d8c6f
>
> As for the logs, the logs for the Send and Receive connectors are stored in:
> \Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpSend
> \Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpReceive
>
> FYI, the following link explains all the
>
> Exchange Server 2007: How many logs hath thee?
> http://exchangepedia.com/blog/2007/1...logs-hath.html
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit among
> responding engineers, and to help others benefit from your resolution.
>
> Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.log
> locations for Exchange 2007:
>
> Exchange Server 2007: How many logs hath thee?
> http://exchangepedia.com/blog/2007/1...logs-hath.html


>> On Saturday, August 22, 2009 4:49 PM Andrew Hodgson wrote:

>> Have you tried the wizard for doing this?
>>
>> Andrew.


>>> On Saturday, August 22, 2009 5:34 PM Ace Fekay [MCT] wrote:

>>> Hi Dave,
>>>
>>> You are welcome.
>>>
>>> Regarding that you still cannot send, please post some of the stuff in
>>> the logs where it is failing, if you can find the entries, to see what is
>>> going on, and if you cannot, just post a one page block.
>>>
>>> Also, you may *possibly* need to create an exception in the SBS
>>> firewall for TCP 3535, as well as possibly in your edge
>>> firewall/router, and if there is any 3rd party security/AV installed on
>>> the SBS. For example, I know that McAfee will block that sort of
>>> traffic and would require an exception rule. Each AV/security app is
>>> different.
>>>
>>> Ace
>>>
>>> --
>>> Ace
>>>
>>> This posting is provided "AS-IS" with no warranties or guarantees and
>>> confers no rights.
>>>
>>> Please reply back to the newsgroup or forum for collaboration benefit
>>> among responding engineers, and to help others benefit from your
>>> resolution.
>>>
>>> Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
>>> Microsoft Certified Trainer
>>>
>>> For urgent issues, please contact Microsoft PSS directly. Please check
>>> http://support.microsoft.com for regional support phone numbers.


>>>> On Saturday, August 22, 2009 8:44 PM Ace Fekay [MCT] wrote:

>>>> I assume you have restarted the Hub Transport service after making the
>>>> changes?
>>>>
>>>> What's in the event logs?
>>>>
>>>> Ace


>>>>> On Saturday, August 22, 2009 10:48 PM raiderdav wrote:

>>>>> I am attempting to configure the send connector in SBS 2008 / Exch07 to
>>>>> route outgoing internet mail through GoDaddy's SMTP
>>>>> (smtpout.secureserver.net). I have a DynamicDNS name exposing the SBS
>>>>> to the internet. Here are my Send Connector settings:
>>>>>
>>>>> Protocol Level: Verbose
>>>>> FQDN for HELO: (DynamicDNS name)
>>>>> Address space: smtp, *, 1
>>>>> Network: Smart host (smtpout.secureserver.net), Basic Authentication
>>>>> with my GoDaddy username & pw
>>>>> Source Server: MYSERVERNAME
>>>>>
>>>>> GoDaddy requires SMTP to be sent over port 3535 or port 80, so I
>>>>> modified the %systemroot%\system32\drivers\etc\services file with:
>>>>>
>>>>> smtp 3535/tcp mail #Simple Mail
>>>>> Transfer Protocol
>>>>>
>>>>>
>>>>> I have been unable to send any email outside of the local network.
>>>>> After a while, I get a 'Delivery Delayed' email response, and
>>>>> eventually a 'Delivery Failed'. Where do the log files get stored? I
>>>>> do not see any under C:\Program Files\Microsoft\Exchange Server\Logging
>>>>> even though I set the Send Connector logging to Verbose.
>>>>>
>>>>> What should be my next troubleshooting step? Am I missing something
>>>>> obvious?
>>>>>
>>>>> Thanks
>>>>> Dave


>>>>>> On Saturday, August 22, 2009 10:48 PM raiderdav wrote:

>>>>>> Thanks for the replies everyone.
>>>>>>
>>>>>> Andrew - yeah, I tried the wizard first. The wizard set up the smart
>>>>>> host and I have only been adjusting parameters from there once things
>>>>>> did not work.
>>>>>>
>>>>>> Ace - thanks for the set-sendconnector info. I just came across that
>>>>>> in the Exchange Management shell before I checked back here. I have
>>>>>> modified the services file back to default and added the set-
>>>>>> sendconnector port information, but I am still not routing external
>>>>>> email. Now that I know where the logs are stored, I will dig deeper and
>>>>>> see if I can figure out what is going on.
>>>>>>
>>>>>> Anyone have any other things to check?
>>>>>>
>>>>>> Thanks
>>>>>> dave


>>>>>>> On Saturday, August 22, 2009 10:48 PM raiderdav wrote:

>>>>>>> Ace -
>>>>>>> Unfortunately I have already added in exceptions in the firewall for
>>>>>>> port 3535 and 25, and the \Exchange Server\TransportRoles\Logs
>>>>>>> \ProtocolLog\SmtpSend folder is empty. I am not sure how that is
>>>>>>> possible since I have verbose logging set on the connector (but it
>>>>>>> does probably mean the connector is never firing). My Send Connector
>>>>>>> is set to Enabled - is there another place that needs to be enabled
>>>>>>> too?
>>>>>>>
>>>>>>> In Services, I see that Exchange Service Host and Exchange Transport
>>>>>>> are both Started/Auto.
>>>>>>>
>>>>>>> dave


>>>>>>>> On Sunday, August 23, 2009 2:59 AM Ace Fekay [MCT] wrote:

>>>>>>>> If you open a telnet prompt, does it respond on that port? If so, what is
>>>>>>>> the response? Even though this is the receive connector, it tells us that
>>>>>>>> the Transport service (SMTP) is running.
>>>>>>>>
>>>>>>>> To run telnet, go into a CMD prompt, type in telnet, hit enter. The command
>>>>>>>> window changes to the telnet command prompt. Then type in the telnet prompt:
>>>>>>>> open yourServerName 3535 <enter>
>>>>>>>>
>>>>>>>> If telnet does not run or says it cannot be found (or something similar to
>>>>>>>> that), go to Server Manager, in the left pane, click on Features, then in
>>>>>>>> the right pane, click on Add Features, and add the Telnet Client (not the
>>>>>>>> telnet server). No restart necessary. Once installed, run the command above.
>>>>>>>>
>>>>>>>> Also, do you remember any other changes, updates, apps added, windows
>>>>>>>> update, etc, that were made other than the services file in the
>>>>>>>> system32\drivers\etc folder?
>>>>>>>>
>>>>>>>> Which Exchange Rollup do you have installed?
>>>>>>>>
>>>>>>>> One other test, is to set the SMTP port back to default with the PowerShell
>>>>>>>> command, set it back to "Use DNS..." (make sure Enabel Domain Security is
>>>>>>>> not checked), then send yourself an email to your personal email address.
>>>>>>>> Check your junk folder, just in case it gets flagged as junk. Check the
>>>>>>>> Transport logs, too. If that works, then the problem is in the smart host
>>>>>>>> setup.
>>>>>>>>
>>>>>>>> Ace


>>>>>>>>> On Monday, August 24, 2009 1:01 AM Ace Fekay [MCT] wrote:

>>>>>>>>> I am confused by your description regarding telnet. Did you install the
>>>>>>>>> Telnet Service? If so, you do not need Telnet Server service installed, and
>>>>>>>>> it is not required. Telnet is a tool, using the telnet client, used to test
>>>>>>>>> connectivity to an Exchange server, but the Telnet Service is NOT required.
>>>>>>>>> My instructions were for adding only the Telnet Client. I suggest removing
>>>>>>>>> the Telnet Service from the listof features if it is installed.You do not
>>>>>>>>> need it, and it can be a security risk.
>>>>>>>>>
>>>>>>>>> Curious, under Organization, Hub Transport, Edge Subscription tab, are there
>>>>>>>>> any entries? if so, then there is an Edge Transport, and the way it works,
>>>>>>>>> is all outbound email will go to that server, to be sent onward to the
>>>>>>>>> outside. If there is an Edge, telnet to that server as I previously
>>>>>>>>> suggested. Let us know if it responds.
>>>>>>>>>
>>>>>>>>> If there is no Edge Transport, then it appears there definitely is a basic
>>>>>>>>> configuration problem if the server is not responding to a telnet
>>>>>>>>> connection. If it truly did not respond, it would time out. If it did, you
>>>>>>>>> would either get a garbled response or the header with the server name. If
>>>>>>>>> either of those came up, that is a good sign, but if it timed out, that is
>>>>>>>>> not a good sign.
>>>>>>>>>
>>>>>>>>> I am happy to hear you put the services file back to default. I assume that
>>>>>>>>> when you put Exxhange back to the default port settings, that you did it by
>>>>>>>>> running the command in the Exchange Management Shell back to port 25. So
>>>>>>>>> when you ran the following, were there any errors reported, either in the
>>>>>>>>> command shell or in the event viewer?
>>>>>>>>>
>>>>>>>>> Set-SendConnector -Identity "YourConnectorName" -Port 25
>>>>>>>>>
>>>>>>>>> Otherwise, there is obviously something up with the transport service. Being
>>>>>>>>> Exchange 2007 (the version installed in SBS 2008), I could walk you through
>>>>>>>>> to do it manually, but since it is SBS, I would not want to do it that way,
>>>>>>>>> and I highly recommend to re-run the SBS wizard if I were you. For the mail
>>>>>>>>> portion, just set it up to send email directly to the internet and do not
>>>>>>>>> select there is an Edge Transport Server. One of the other folks who are
>>>>>>>>> more familiar with SBS 2008 and it is wizard can better help in that area.
>>>>>>>>>
>>>>>>>>> And nothing in the Event viewer?
>>>>>>>>>
>>>>>>>>> Ace


>>>>>>>>>> On Monday, August 24, 2009 4:35 AM raiderdav wrote:

>>>>>>>>>> Yes - I have even rebooted the server in case I missed a service that
>>>>>>>>>> needed to be restarted. I am not seeing anything exchange related in
>>>>>>>>>> the Event Viewer - is there a specific location that I should check?
>>>>>>>>>> Still nothing appearing in the ProtoLog/SmtpSend folder either.
>>>>>>>>>>
>>>>>>>>>> d


>>>>>>>>>>> On Monday, August 24, 2009 4:36 AM raiderdav wrote:

>>>>>>>>>>> It is not responding to a Telnet to port 3535 - I have tried on the
>>>>>>>>>>> server and from another PC on the same network. Telnet services are
>>>>>>>>>>> installed and responding on the server. The services file is in its
>>>>>>>>>>> default state - I only commented out the one line for port 25 and
>>>>>>>>>>> copied it to be 3535 previously. That is back to normal.
>>>>>>>>>>>
>>>>>>>>>>> I have all the most recent updates installed - only updates lacking
>>>>>>>>>>> are Silverlight and Malicious Removal, so that should not be an issue.
>>>>>>>>>>>
>>>>>>>>>>> I was also never able to send an email prior to setting up the smart
>>>>>>>>>>> host - I am not sure how to set the SMTP to Use DNS and route email on
>>>>>>>>>>> its own. I will keep trying to see if I can get it to send something,
>>>>>>>>>>> but so far nothing has ever sent since I installed SBS2008.
>>>>>>>>>>>
>>>>>>>>>>> Thanks so much for all the help Ace
>>>>>>>>>>> dave


>>>>>>>>>>>> On Tuesday, August 25, 2009 5:37 PM Ace Fekay [MCT] wrote:

>>>>>>>>>>>> Dave,
>>>>>>>>>>>>
>>>>>>>>>>>> You could, but I do not think you want to lose all of your mailboxes. it is
>>>>>>>>>>>> probably just a simple configuration issue that I am overlooking.
>>>>>>>>>>>>
>>>>>>>>>>>> Check these settings, please:
>>>>>>>>>>>> ===
>>>>>>>>>>>> Org\Hub\Edge Subscriptions, should be blank.
>>>>>>>>>>>> Org\Hub\Remote Domains, should be one entry with an asterisk.
>>>>>>>>>>>> Org\Hub\Send Connectors - One connector, general tab:
>>>>>>>>>>>> FQDN = public FQDN (such as mail.yourDomain.com)
>>>>>>>>>>>> Address Space = *
>>>>>>>>>>>> Cost = 1
>>>>>>>>>>>> Network = DNS
>>>>>>>>>>>> Select "Use External DNS lookup"
>>>>>>>>>>>> Source = yourServerName
>>>>>>>>>>>> Org\Hub\Accepted Domains = yourPublicDomain.com
>>>>>>>>>>>> Org\Hub\global Settings, Transport settings = default (leave it alone)
>>>>>>>>>>>>
>>>>>>>>>>>> Server Config\Hub\ Top Window= yourServerName
>>>>>>>>>>>> Right Click Servername, properties
>>>>>>>>>>>> General - Info only
>>>>>>>>>>>> System Settings = Should be your SBS server
>>>>>>>>>>>> External DNS = Use NIC settings
>>>>>>>>>>>> Log Settings = Check what you like in here
>>>>>>>>>>>> Limits = Leave Default
>>>>>>>>>>>> Internal DNS Settings = Use NIC settings
>>>>>>>>>>>> Bottom - Default Receive connector
>>>>>>>>>>>> General tab
>>>>>>>>>>>> Default connector = FQDN = public mail FQDN
>>>>>>>>>>>> Network Tab = Leave Default.
>>>>>>>>>>>> The top should show IPv4 and IPv6 both with port 25
>>>>>>>>>>>> Bottom (Remote Servers) shows complete IP range, IPv4 and IPv6
>>>>>>>>>>>> Authentication tab
>>>>>>>>>>>> TLS
>>>>>>>>>>>> Basic
>>>>>>>>>>>> Offer Basic only after TLS
>>>>>>>>>>>> Integrated Windows
>>>>>>>>>>>> Permissions group tab
>>>>>>>>>>>> Check Everything
>>>>>>>>>>>> Bottom - Client Receive Connector
>>>>>>>>>>>> General tab
>>>>>>>>>>>> Default connector = FQDN = public mail FQDN
>>>>>>>>>>>> Network Tab = Leave Default.
>>>>>>>>>>>> The top should show IPv4 and IPv6 both with port 587
>>>>>>>>>>>> Bottom (Remote Servers) shows complete IP range, IPv4 and IPv6
>>>>>>>>>>>> Authentication tab
>>>>>>>>>>>> TLS
>>>>>>>>>>>> Basic
>>>>>>>>>>>> Offer Basic only after TLS
>>>>>>>>>>>> Integrated Windows
>>>>>>>>>>>> Permissions group tab
>>>>>>>>>>>> Check Anonymous and Exchange only
>>>>>>>>>>>> ======
>>>>>>>>>>>>
>>>>>>>>>>>> Now click on Toolbox, run the Best Practice Analyzer
>>>>>>>>>>>>
>>>>>>>>>>>> Also, can you send an email to another internal user?
>>>>>>>>>>>>
>>>>>>>>>>>> Ace


>>>>>>>>>>>>> On Wednesday, August 26, 2009 12:39 PM Ace Fekay [MCT] wrote:

>>>>>>>>>>>>> Ok, hold off on the wizard for the time being. And good the BPA is clean.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Who is your ISP? Do they block inbound/outbound port 25, or even any other
>>>>>>>>>>>>> port such as 3535?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Ace


>>>>>>>>>>>>>> On Wednesday, August 26, 2009 5:10 PM Ace Fekay [MCT] wrote:

>>>>>>>>>>>>>> Well there you have it. Port 25 is blocked.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> btw - SMTP mail traffic does not go across port 80. That is http or web
>>>>>>>>>>>>>> traffic. If you mean you can check, receive and send mail through a web
>>>>>>>>>>>>>> browser, that is different. You're using their web mail for that. Web mail is
>>>>>>>>>>>>>> just an interface to their mail server, like OWA.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> When you call them, if you only need port 3535 to use your offsite SMTP
>>>>>>>>>>>>>> gateway, then that will be all that is needed. However, I would also want to
>>>>>>>>>>>>>> have 25 open.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> AT&T Uverse sounds like a home/residential service, not a business service.
>>>>>>>>>>>>>> They may not open those ports. If not, you will need to get a business line.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Ace


>>>>>>>>>>>>>>> On Wednesday, August 26, 2009 10:44 PM raiderdav wrote:

>>>>>>>>>>>>>>> Hi Ace - thanks for the continued help.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Rather than keep attempting to troubleshoot things from an unknown
>>>>>>>>>>>>>>> state, is there an easy way to get all of Exchange back to the initial
>>>>>>>>>>>>>>> state? If I removed all Exchange Roles from the server, reboot, and
>>>>>>>>>>>>>>> then add the Roles back in, will that give us a clean slate to work
>>>>>>>>>>>>>>> from? I am not making much progress at this point and I think getting
>>>>>>>>>>>>>>> everything back to a known point would be the best place to try to get
>>>>>>>>>>>>>>> things working.


>>>>>>>>>>>>>>>> On Wednesday, August 26, 2009 10:45 PM raiderdav wrote:

>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> 25
>>>>>>>>>>>>>>>> IPv4 and IPv6
>>>>>>>>>>>>>>>> 587
>>>>>>>>>>>>>>>> IPv4 and IPv6
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Ok - making progress finally. I set up everything as you outlined
>>>>>>>>>>>>>>>> above and now I have SMTP log messages being generated. I can send
>>>>>>>>>>>>>>>> emails internally (that worked the whole time). I still cannot send
>>>>>>>>>>>>>>>> emails out to the internet, but here is the error message I get now:
>>>>>>>>>>>>>>>> 2009-08-26T16:15:32.635Z,Default,
>>>>>>>>>>>>>>>> 08CBF47DC72F40B0,1,,209.85.135.114:25,*,,"Failed to connect. Error
>>>>>>>>>>>>>>>> Code: 10060, Error Message: A connection attempt failed because the
>>>>>>>>>>>>>>>> connected party did not properly respond after a period of time, or
>>>>>>>>>>>>>>>> established connection failed because connected host has failed to
>>>>>>>>>>>>>>>> respond 209.85.135.114:25"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The 209.85.x IP address is for gmail, which is the domain I was
>>>>>>>>>>>>>>>> sending email to.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Should my next step be to attempt the Wizard again for a smart host,
>>>>>>>>>>>>>>>> or do I need to get DNS based SMTP working first?


>>>>>>>>>>>>>>>>> On Wednesday, August 26, 2009 10:45 PM raiderdav wrote:

>>>>>>>>>>>>>>>>> Also - best practices analyzer came back with Exchange is running as
>>>>>>>>>>>>>>>>> Standard.


>>>>>>>>>>>>>>>>>> On Wednesday, August 26, 2009 10:45 PM raiderdav wrote:

>>>>>>>>>>>>>>>>>> r
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> The ISP is AT&T Uverse, and I have been able to send email via Outlook
>>>>>>>>>>>>>>>>>> SMTP through GoDaddy both on port 80 and 3535. It looks like outgoing
>>>>>>>>>>>>>>>>>> traffice on port 25 is blocked by AT&T: http://belkadan.com/blog/2007/07/Po=
>>>>>>>>>>>>>>>>>> rt-25-Blocked/
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I will call and see if they can open up that port - but either way, my
>>>>>>>>>>>>>>>>>> end goal is to send via 3535 or 80 via GoDaddy's SMTP.


>>>>>>>>>>>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>>>>>>>>>>>>> Why GUIDs are not a good idea for SQL Server Primary Keys
>>>>>>>>>>>>>>>>>> http://www.eggheadcafe.com/tutorials...mary-keys.aspx

Forgive the last post.......that's a fix for a different issue.

GoDaddy:

Put in the IP adress of the smtpout relay server...don't use the smtpout.relay-secureserver.net name.

It then works.

Submitted via EggHeadCafe - Software Developer Portal of Choice
MongoDb vs SQL Server Basic Speed Tests
http://www.eggheadcafe.com/tutorials...eed-tests.aspx