Jump to content

local-lad-steve

Members
 View Profile  See their activity

  • Posts

    43

  • Joined

  • Last visited

 Content Type 

Everything posted by local-lad-steve

  1. local-lad-steve
    Sukh, i have PM'd you.
  2. local-lad-steve
    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.
  3. local-lad-steve
    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.
  4. local-lad-steve
    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.
  5. local-lad-steve
    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.
  6. local-lad-steve
    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.
  7. local-lad-steve
    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.
  8. local-lad-steve
    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?
  9. local-lad-steve
    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?
  10. local-lad-steve
    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....
  11. local-lad-steve
    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.
  12. local-lad-steve
    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
  13. local-lad-steve
    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.
  14. local-lad-steve
    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.
  15. local-lad-steve
    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!
  16. local-lad-steve
    Recreated the internet receive connector, all mail seems to be flowing as per normal now. thanks for your suggestions and help everyone.
  17. local-lad-steve
    Sukh, it is inbound mail thats affected only....
  18. local-lad-steve
    When i mentioned TLS authentication i was looking at the receive connector properties, Authentication tab. i have set the receive connector to verbose for logging. it is a SBS single exchange server environment, no edge server, running windows sbs 2008. mail scanning is completely disabled right now while there are problems, and the client is getting very grump about the delay of this....so as always any suggestions are appreciated.
  19. local-lad-steve
    having said that, ran the mail flow ttroubleshooter and it came up with the following: Error submitting mail: Mail submission failed: Error message: Server does not support secure connections.. im wondering if the TLS authenication for the server being enabled is causing an issue?? is it something that i can just disable or will i dig a deeper hole for myself?
  20. local-lad-steve
    I just ran the same test and got a fail. its very temperamental: Resolving hostname... Connecting... SMTP -> FROM SERVER: 220 remote.obbc.com.au Microsoft ESMTP MAIL Service ready at Wed, 11 Sep 2013 06:41:01 +1000 SMTP -> FROM SERVER: 250-remote.obbc.com.au Hello [184.72.226.23] 250-SIZE 52428800 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-AUTH 250-8BITMIME 250 XXXXXXXX MAIL FROM: [email protected] SMTP -> FROM SERVER: 250 2.1.0 Sender OK RCPT TO: [email protected] SMTP -> FROM SERVER: 250 2.1.5 Recipient OK Sending Mail Message Body... SMTP -> FROM SERVER: SMTP -> ERROR: DATA command not accepted from server: Message sending failed. Yes outbaound mail is working fine, its just inbound mail. have ran all the mail flow toolbox tools, and theres no issues being thrown up.
  21. local-lad-steve
    having spent two days trying to clear up the exchange box, I was thinking the same and that I was looking in the wrong place. from the email I received today, the above list fell under the mx records for the domain. that's all I was provided with. With regards the remote/mail.obbc.com.au...there are event viewer errors for this, but its just for sending mail I think and outbound mail is fine. I reckon it is a DNS issue....so do you think we need to be contacting the service provider?
  22. local-lad-steve
    having cleared space and give the server a reboot, exchange emails came in when I sent some test messages and I thought we were at the finish line... however it stopped working again..... james, details u requested earlier as follows: Domain name: obbc.com.au ip address: 203.89.201.60 mail server host name: mail.obbc.com.au priority: 10 host/alias Record type ip/hostname adsl.obbc.com.au CNAME mail.obbc.com.au mail.obbc.com.au A 14.201.14.48 oldmail.obbc.com.au A xxx.xxx.xxx.xxx oldremote.obbc.com.au A xxx.xxx.xxx.xxx remote.obbc.com.au A 14.240.126.117 Financial planning, Business Leasing & Asset Purchase, Auditing, Business Loans, O A 203.89.201.60 if I do a remote connectivity test analyser, sometimes it connects and sometimes it fails. any more thoughts folks?
  23. local-lad-steve
    Thanks! This is something that i have looked into today. so i have managed to create another 60Gb of space on the drive and nothing changed, but, i am going to restart the server in 2 hours time to see if a kick will bring the box back into life.
  24. local-lad-steve
    From my understanding, the MX records sits with the isp? no? there is only a single exchange server in this organisation. i guess i would need access to the the DNS of the isp to find out about the mx records, which i dont have. ...and emails "5" and "8" came through 2 hours later than the others..... im completely lost as to what is going off here...
  25. local-lad-steve
    Further update: I sent 8 test emails from my external email address to the administrator mailbox one after the other and labelled the subject line 1 to 8 as per email. within 2 mins, emails number 3 and 6 came through. after 10 mins, emails number 4 and 7 came through, then 12 mins later emails 1 and 2 came through. bizarre behaviour. can anyone suggest what might be causing this???
×
×
  • Create New...