local-lad-steve

Sukh, i have PM'd you.

we configure their DNS records through our DNS provider, conexim.com.au. i ran the ssl test. for our domain, it passed fine which is expected and mail.ourdomain.com.au is what the client should be using. but then i tried testing ssl for mail.clientdomain.com.au and it failed stating: "certificate name mismatch. Try these other domain names (extracted from the certificates): autodiscover.ourdomain.com.au, mail.ourdomain.com.au, www.mailourdomain.com.au." and the IP that it connects to is for our domain. this to me is normal. it is stating that it has found that for the client domain, it is going to our exchange server. Except when we set this up through outlook anywhere, it somehow gets a different certificate.

i guess all other clients use our internal dns for autdiscover which points to the ip of the exchange server and it works. this is an assumption. but if this works for them, i still dont understand where this other company are getting this alternate cert from as they have identical settings within outlook clients.

i dont see where this would be configured. from the internet i have configured the http setting to point at mail.ourdomain.com.au. We host their dns where the mx records point to message labs, but there is no autoD record and we havent had the need to set that up for any other client that all work fine.

yes, we host exchange for many companies. our cert specifies our domain only, which works for outlook anywhere so long as you enter mail.ourdomain.com.au and put in the clients email address for the mailbox/username. just this one seems to be picking up a cert from somewhere else and i have no idea where.

Hi All, after having been looking into some other work i have been put back on this task of resolving this issue. i looked at it again today and started fresh, created a new mailbox on my exchange server and changed the primary smtp address to be the clients address: [email protected]. thought this is sitting on our exchange server. i set up outlook to use http(outlook anywhere) and set the address to ourdomain.com.au. the exchange server it is pointing at is exchangeserver.ourdomain.com.au. the user/mailbox name is [email protected]. When we open outlook, it loads fine, then about 30 seconds later it pops up with the cert error and it appears that it is getting a certificate for clientdomain.com.au instead of ourdomain.com.au. i have tested this with other clients that we host email for and it works fine, there is no error and they must get the correct öurdomain.com.au cert. i cant understand why this particular client is receiving a different cert, if they are accessing our server, in our domain, accessing the mailbox on our exchange server. any thoughts how this could be happening. to me it is clearly a DNS problem - just not sure where. i have done a whois and confirmed the DNS settings appear to be correct. im stumped. any ideas are greatly appreciated.

The settings specify my domain. the exch server specified is within my domain, the https setting points to mail.mydomain.com. then the user/mailbox specifies their email address. i.e. [email protected] - so their email address IS the only thing that is different. it is still coming up with the error that the site name is different to that on the cert.

thanks i did try this by adding a service locator record in and pointing to autodiscover.ourdomain.com.au. but this didnt work. but you suggest changing the autodiscover.ourdomain.com.au to our public facing ip?

we are hosting their email yes. their mailboxes are on our mail server and their exchange settings within outlook point at our exchange server, as mentioned above this connects thru http. i was not the person who set this up so am not entirely sure how they got this working, but they left it in a way that autodiscover is throwing up this error each time the users open outlook. we have a certificate deployed for our exchange server in our domain, which again, their mailboxes reside on. i guess this is why it is moaning about the fact that the certificate doesnt match the name of the site. But its the correct server that outlook is connecting to so how do we establish a connection for AutoD to work?

i have just discovered that Out of Office cant be set up from the outlook client either, all users have to log into OWA to configure their OOO. Im sure this is all related, and im 95% certain this is a DNS configuration that is missing....

Hi All, looking for some help with Autodiscover and hopefully this will be a quick resolution as i think it will be a DNS configuration but my DNS knowledge is limited.. Im working with a client whose email is being hosted by on our mail server. they are using outlook 2010/2013 and everytime they open outlook, they get a certification error. It seems that autodiscover functionality is looking for 'autodiscover.domain1.com.au' (Domain1 = client domain), and their mail server is 'mail.domain2.com.au' (domain2 = Email server domain). They are on a completely separate AD forest without any kind of trust in place, so are connecting over http i guess. in their exchange proxy settings the "use this URL to connect to my proxy server for exchange" is populated with the server within domain2 and has the mx record for the server entered in there. in its current state: the server is resolved using the fqdn of the mail server connecting to the mail server over http (from what i can grasp) when testing in the client domain, i cant seem to create a new outlook profile replicating other outlook profile settings as i cant authenicate against the administrator account for example. i have read up on autodiscover but cant seem to find anything that is specific to my scenario. i have created a service locator record to point at autodiscover.domain2.com.au. still no joy.... Certificate Error attached.

thanks for the info guys. Unfortunately the client has changed their mind and the request is no longer needed - a shame as this would have been a very useful exercise. But thanks for the tips, they may come in handy in the future as i am about to set up a new 2013 environment in the next month or so

thanks James that does clear it up. "I am going to assume that it's the former" yes i am trying to allow a client to send emails to us that are above the "across the board" max size limit. So yes, i am waiting for the public ip address of the concerned client and will fix this to the receive connector and see how we go and that will therefore be the "connection" so to speak that we require. thanks for the info, i will test this out and see how we go.

thanks Sukh. i must have got this wrong then... i assumed that by setting up a receive connector and entering the ip settings for the clients domain/exchange that this would in effect be the connection set up?! and should i assume that in that case the the ip address should be the clients router's external ip? the settings for mail size restrictions are correct within the organisation, its just the connection to the client eexchange im struggling to configure.

Hi, I have been asked to allow larger emails to come into the organisation from a particular client. But I just want to allow larger emails from that client and that client only. having done some digging I set up a new receive connector and allowed 30Mb max receive size for that connector but I have a query for the network settings tab. Should I enter the Ip addresses of the clients public available DNS servers? - or otherwise how will our exchange server allow the sending from the client domain only through that receive connector? is this the correct ip addresses to configure? thanks in advance for any help!