Link to home
Start Free TrialLog in
Avatar of frdbadf
frdbadf

asked on

SBS 2011 Exchange Server 2010-Cannot send EMails

I was trying to assist the phone vendor in sending voicemail message via email.  Clients are using Outlook, they have an Exchange mailbox and pop3 email account which was set as default.  They used ISPs outgoing mail server.  Everything was working fine for almost 3 weeks until today.

I ran the Set up your Internet Address wizard and now the Outgoing mail is not working either through the ISPs SMTP server or the Exchange Server.

The website/email is hosted by a third party vendor.  Our ISP is Cbeyond.

 Can the effects of the Wizard be undone?
Avatar of vSolutionsIT
vSolutionsIT
Flag of India image

They must be getting stucked in the queue right? What does the error says in the exchange queue?

Enable diagnostic logging for Msexchange Transport /smtpsend ,categorizer and connection, restart exchange transport service and check what warning /error it reports in application event logs.
Avatar of frdbadf
frdbadf

ASKER

One other thing, if you send using the POP3 account ISP SMTP server (which did work) the Outlook clients now generate a Send test e-mail message:  The operation timed out waiting for a response from the sending (SMTP) server.  If I change to send using Exchange Server then they are stuck in Queue,  Working on diagnostics.
Re-run the Smart host wizard in the SBS console.

If this does not fix the problem then run the Fix my Network wizard and advise on warnings / errros.
Avatar of frdbadf

ASKER

Fix My Network results.

Could not configure the router
DNS is using a DNS forwarder

both of which cannot be fixed.
Both of those are ok and not really problems.

Are the messages still gathering in the queue? Which queue are they stuck in?

Have you restarted the Exchange Transport service?
After running the wizard you have, SBS will block internal IP addresses from sending email to the server. You need to create a new Receive Connector for the phone system.

http://semb.ee/apprelay

Simon.
Avatar of frdbadf

ASKER

Sembee,

I think this is a DNS issue now.  Since I ran the Internet Address wizard we have had problems.  The outlook clients could no longer send email via the ISP SMTP server and if I send via Exchange the outgoing message fill up the queues.

thanks
What do the messages in the queues say?
Outlook should only be sending via Exchange and then get Exchange to send either directly by MX records or via the ISPs SMTP server. However you need to look in the queues and post the error.

Simon.
Avatar of frdbadf

ASKER

I have run a session with Microsoft tech support and they said nothing is wrong with their server, however email continues to stack up in the outgoing queue.  MS said port 25 was blocked but I have port 25 open via the SonicWall, I called the ISP Cbeyond said they are not blocking necessary ports, 25, 80, 443 and 987.  MXTools SMTP test fails.

Error message in queue, 451 4.4.0 Primary target IP address responded with 421 4.4.2 connection dropped due to time out.  Attempted failover to altername host, but that did not succeed.  Either there are no alternate hosts or delivery failed.

telnet localhost 25 reponds server.domain Microsoft ESMTP Service is ready.

Microsoft tech had disabled the Sonicwall rules, you can telnet to the public IP address on port 25.  Port 25 is not blocked.  Upon re-enabling the rules the email queue cleared out.

There is one message in queue now sent at 12:02 pm today, 400 4.4.7 Message delayed.
What does your send connector say? Is it set to send via DNS or via a smart host? Has it had the "Use the External DNS settings on the transport server" box ticked?
ASKER CERTIFIED SOLUTION
Avatar of frdbadf
frdbadf

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of frdbadf

ASKER

It was a hardware issue.  I had several sessions with Sonicwall technical support during which the issue was not found.  It was only by using another Sonicwall to test that the issue was discovered.