New Exchange 2013 incoming mails stuck in Q

Just started up a new exchange server and while testing I discovered incoming email is often delivered up to 90 mins after it was sent. looking around I discovered it stuck in the delivery q and going nowhere. Any ideas why the q traps some email?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Muhammad BurhanManager I.T.Commented:
please verify the Exchange's A record entry in your local DNS zone, hope this works.

or consider

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
8fort8Author Commented:
The server is a vm on the domain controller and its name appears as an a record pointing to the correct ip. There's also a ptr. no mx.
Muhammad BurhanManager I.T.Commented:
so what you found in event logs regarding this ?
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

8fort8Author Commented:
The dns is fine The ms exchange  logs show event 6 cmdlet failing  claiming unknown ecp and administrator. I'm completely unsure why that is.

Cmdlet failed. Cmdlet Get-Notification, parameters {Summary=True}.

- EventData

- EventData

   {ErrorAction=SilentlyContinue, Identity=VMEXCHANGE2013}
   Local-Exchange Management Console-Unknown
   2684 ExSetupUI.exe
   View Entire Forest: 'True',  
   Microsoft.Exchange.Data.Directory.ADInvalidCredentialException: Active Directory operation failed on . The supplied credential for 'Server2013\Administrator' is invalid. ---> System.DirectoryServices.Protocols.LdapException: The supplied credential is invalid. at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential) at Microsoft.Exchange.Data.Directory.PooledLdapConnection.BindWithLogging() at Microsoft.Exchange.Data.Directory.PooledLdapConnection.BindWithRetry(Int32 maxRetries)
8fort8Author Commented:
Found issue and solution
  The errors are other separate issues but the Q problem is explained in detail on the link and worked instantly.
8fort8Author Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for 8fort8's comment #a41182168

for the following reason:

I found the answer in long after I posted the question and thought it may be of use to others.  But thanks to everyone who had suggestions.
8fort8Author Commented:
The link Mohammad provided did not solve the issue I was trying to solve however, it correctly identified a very common related issue that was misleading my efforts to solve the lesser issue I wrote about.
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
Email Servers

From novice to tech pro — start learning today.