Exchange 2013 Fax email routing

I have an Exchange 2013 server that is already setup and running just fine.  I'm trying to hook up a USB fax machine to it and route faxes through the Exchange server itself.  I have the faxes working, but it's failing when routing to Exchange.  

It has an internal relay connector that's setup, in addition to the standard external connector, that accepts emails from our network copiers.  The standard connector accepts TLS, Basic, Integrated, and Exchange authentication and from Exchange servers, Legacy Exchange servers, and Exchange users.  The internal relay connector accepts only Externally secured authentication from Exchange servers and Anonymous users.  

I've tried setting the Fax authentication to basic and integrated with the admin account and also my own account and the routing keeps failing.  Do I need to add the Exchange server's IP to it's own list of accepted SMTP servers somewhere?  That seems redundant to me since it's basically trying to email itself, but I'm out of ideas.  

Thanks.
LVL 1
jleyseAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
"Externally secured authentication " - you don't need that.
What do you have set as the remote IP address on the receive connector? You do need that.
Have you tried a telnet test from the server back to itself?

It can also give different results depending on whether you are connecting to the server's real IP address, host name or 127.0.0.1. What are you putting in to the software as the email server?

Simon.
0
jleyseAuthor Commented:
I'm using the server's name.
0
Simon Butler (Sembee)ConsultantCommented:
Try changing to the IPv4 address of the server.
Exchange 2013 uses both the IPv6 adn IPv4 address, it may well be that it is trying to connect to itself on IPv6. Therefore switching from the host name to the actual IP address will give you a known conection method.

Simon.
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

jleyseAuthor Commented:
Didn't work.  I tried the IPv4 address with Integrated Windows authentication, basic, and anonymous.  Also tried local host and that didn't work either.
0
Simon Butler (Sembee)ConsultantCommented:
You cannot see what is happening with the application.
Therefore do a telnet test.
http://semb.ee/telnettest

Are you trying to send to internal or external recipients?
If internal, you don't need anything special because you aren't relaying. It is just accepting email. Therefore it could be that the messages are being blocked by AV or antispam.

Simon.
0
jleyseAuthor Commented:
Thanks.  I'll have to check this on Tuesday.  Heading out of town for the long weekend.  I'll let you know what happens.  

It's an internal recipient.  Wouldn't think anything would be blocking it other than if Exchange has a built in spam filter.  

Thanks again.
0
jleyseAuthor Commented:
The Telnet fails with error 4.3.2, Service unavailable.  I've read that this could be due to a custom receive connector.  We do have that internal relay connector for our network copiers so that we can scan from them.  But I've tried all sorts of different ways to get those working and this has been the only way I can get them to work.  

I'll try disabling the Internal relay and try the faxes again.
0
jleyseAuthor Commented:
With our internal relay connector disabled, telnet and faxes both still fail.  

I get an 2 error events when the fax relay fails.  32089 and 32083.
0
Simon Butler (Sembee)ConsultantCommented:
Error codes on their mean nothing.
Something must be blocking the traffic.

Simon.
0
jleyseAuthor Commented:
I couldn't figure out what was blocking it and just moved it to another server and authorized it from there.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jleyseAuthor Commented:
Couldn't find answer
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.