cpjitservices Posted May 14, 2015 Author Posted May 14, 2015 I have the following open on my firewall 80TCP, 110TCP, 143TCP, 443TCP, 587TCP, 993TCP and 995TCP Are there anymore I need open ? Thanks
andydis Posted May 14, 2015 Posted May 14, 2015 I personally rate 2010 better than 2013 , any how here goes 1) offsite can you ping autodiscover.yourdomain.com ( thoughts : DNS can take while to replicate or not setup correctly ) Does it resolve to the correct ip? Can you telnet to it on port 443 ? Offsite Can you put it in http://IP/owa Thoughts firewall blocking ? 1
cpjitservices Posted May 15, 2015 Author Posted May 15, 2015 Yeah I prefer 2010 but licensing forces 2013, I cant ping it, firewall shouldnt be blocking it as Ive got all the ports open such as 80,25,110,143 etc. Unless there are more ports I need to open for Autodiscover ? I believe my DNS is set up correctly. I have a CNAME of autodiscover.mydomain.com and an A record of autodiscover pointing to my IP. I can get to my OWA and OWA works fine. I may have to wait for propagation, 123reg aren't having any issues. Its been more than 48 hours now.
pantscat Posted May 15, 2015 Posted May 15, 2015 Still looks like a DNS issue to me - I can't resolve your autodiscover record. I'd nag 123reg and check that there's not an issue somewhere.
cpjitservices Posted May 15, 2015 Author Posted May 15, 2015 Still looks like a DNS issue to me - I can't resolve your autodiscover record. I'd nag 123reg and check that there's not an issue somewhere. Im on with them now, no response from them what so ever. Weird this though, my MX record doesnt exist on the internet (Check it here) https://www.whatsmydns.net/#MX/mail.thejacksonhouse.eu But mail is flowing fine...
cpjitservices Posted May 15, 2015 Author Posted May 15, 2015 Still looks like a DNS issue to me - I can't resolve your autodiscover record. I'd nag 123reg and check that there's not an issue somewhere. Everything seems to be resolving now, but when I try to add my account to Outlook I keep getting password prompt. Have typed it in correctly but no cheese.
pantscat Posted May 15, 2015 Posted May 15, 2015 Yep, I can confirm that - names are resolving properly now. Try the exchange connectivity tester again - it'll help troubleshoot it!
cpjitservices Posted May 15, 2015 Author Posted May 15, 2015 It says it cant contact https://thejacksonhouse.eu:443/Autodiscover/Autodiscover.xml - Its asking for a username and password if you browse to that address. I have typed in every credential I can think of and none of them work. Im guessing If this is figured out itll work.
pantscat Posted May 15, 2015 Posted May 15, 2015 In IIS what authentication mechanism is set for the Autodiscover virtual directory?
cpjitservices Posted May 15, 2015 Author Posted May 15, 2015 (edited) All enabled, except for Digest & Forms based. Trying to add the account to Outlook through Maill app in control panel, type in credentials and fails on searching for the email address. Edited May 15, 2015 by cpjitservices
cpjitservices Posted May 15, 2015 Author Posted May 15, 2015 Hmm... I'm a bit stumped now. I'll have a think. Me too, have just been on exchange and set the OWA to authenticate via Username so that the domain\username doesnt have to be entered. Have just tried adding the account via Outlook, got login screen, tried a number of ways using credentials and it got to the searching screen and failed.
cpjitservices Posted May 15, 2015 Author Posted May 15, 2015 I have tried the /Autodiscover.xml link on the site, It asked for login details so I managed to get in and got the following. 600Invalid Request
pantscat Posted May 15, 2015 Posted May 15, 2015 That's expected accessing it from a web browser. You should get a 600 error. Try using the Test-OutlookWebServices commandlet in PowerShell... that might shed some light on it. 1
cpjitservices Posted May 15, 2015 Author Posted May 15, 2015 Hmmmmmmm heres an error from the above command, Autodiscover returned the error: 603:Active Directory currently not available
pantscat Posted May 15, 2015 Posted May 15, 2015 Hmm... Can you post the output to the following commands: get-AutodiscoverVirtualDirectory | fl get-ClientAccessServer | fl get-webservicesvirtualdirectory |fl get-oabvirtualdirectory | fl get-owavirtualdirectory | fl get-ecpvirtualdirectory | fl get-ActiveSyncVirtualDirectory | fl Also - do you have a proper SAN certificate installed?
AceDaz Posted May 15, 2015 Posted May 15, 2015 You have 2 duplicate autodiscover.xxxxx external DNS entries on 123reg, I would remove the CNAME and have the IP pointing to the same IP that corresponds to your MX records. Also in your EMC -> OWA screen shot you have Forms authentication set but you havent selected Username only, therefore you need to login as DOMAIN\J.Bloggs. I have setup our Exchange 2010 system here, so I have a lot of experience 1
cpjitservices Posted May 15, 2015 Author Posted May 15, 2015 Ahhh well I gave up on Autodiscover as It looks like I need a certificate which would need to be purchased. so I am working via IMAP at the moment and all seems well.
cpjitservices Posted February 5, 2016 Author Posted February 5, 2016 Try the steps mentioned in this article to resolve this error: Fix AutoDiscover Invalid Request Error Code 600 in Exchange Thanks I ended up binning Exchange in the end and opted for the latest implementation of Zimbra.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now