No connection to Exchange 2013 URGENT!!!

Honered Experts

I need help ASAP :-)

I have just been called to a customer running an Exchange 2013 SP1
The customer complained that they was not able to neither send nor receive external emails.
Futhermore I notice that after closing and starting their Outlook 2010 clients from the pcs all Outlook client gets disconected - HOWEVER - OWA seems to be connecting fine

I have done a close investigation on the Exchange server itself but everything seems to be working as supposed.

- All services is running
- Database is mounted
- Lots of free diskspace
- no change of ip

Also a check from DNSSTUFF came out without no errors.

Now Im REALLY stressed up :-)   Any ideas ?
OhmitAsked:
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.

archinetCommented:
Hello,

Have you perform a "Test-ServiceHealth" in powershell ?

Have you a connection with the AD ?

Can you connect to OWA ?

Regards,

Clément.
0
OhmitAuthor Commented:
I have not tried the test in powershell.

Yes I have full connection with the AD

YES Owa seems to connect but mail flow does not work
0
OhmitAuthor Commented:
Ok Test-ServiceHealth came out with no errors
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Miguel Angel Perez MuñozCommented:
When you said mailflow, are you talking about external email? Maybe your ISP are blocking SMTP traffic to your public IP or something happens with your records on DNS.

Check you have communication 25 TCP port and your MX records are fine, this website let you do this tests: http://mxtoolbox.com/
0
archinetCommented:
Can you send internal email between your internal mailbox ?

In your Firewall the port 25 is opened ? Can you try with telnet connection to connect in your messaging system : telnet o privateip 25

Regards,

Clément.
0
skullnobrainsCommented:
OWA runs fine so the server in itself works, and probably also can send and receive new messages if it was not recently toyed with.

looks like a firewall issue.

MAPI (outlook clients) runs on the imap port 143

as pointed above, smtp operation is on port 25

it is difficult to help further without knowing about the details, but this is most likely where you should start from. note that trying to telnet to the 143 port internally from one of the desktop is likely to produce usefull information such as "router X says no route to host EXCHANGE". to know about the routers along the way, tracert/traceroute is your friend
0
OhmitAuthor Commented:
Ok I got some more information:

You can not connect from local Outlook clients. Just says DISCONNECTED.
You can connect via owa at HTTPS://MAILSERVER/OWA but mail flow does not work. Looks like it sends mails but they are not received.
Also you can send mail from extern to a local recipient but these mails just disappear.
0
OhmitAuthor Commented:
Also I have checked for change of ip of the Exchange server and restarted the Zyxel firewall.
0
archinetCommented:
"Get-Queue" in powershell give some email blocked ? (mail poisoning)

Regards,

Clément.
0
skullnobrainsCommented:
still most likely the traffic does not reach the server which would seem like a network issue.

maybe to see what works first
try to telnet to a well-known smtp server from your exchange
if it does not reach, post message, and run a ping to google.com, and/or try a browser
if none of the above works, check ip settings, gateway, and the likes

if the above does work, we'll need to check if incoming connections reach the server. run a trace either on the firewall or the exchange on port 25
0
OhmitAuthor Commented:
Hello all.

Thank you for your inputs.
It turned out that this error was caused by a malfunction installation of the CU5-update.
I had Microsoft working with this for 4 hours!
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
OhmitAuthor Commented:
problem caused by faulty update.
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
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.