Hi hopeing someone can tell me quickly where the possible issue may be with the mail server access. The upshot is We can connect to the mail server via (https://) thedomainname.com/owa but not via (https:// )mail.thedomainname.com/owa
Could somebody who knows please confirm, if it is and easy one, where the config ammendment needs to be made.
If both names resolve to the same IP address (I assume they do, otherwise you wouldn't be asking, but try pinging both names to make sure), then you may have a host name configured for your default web site in iis. If a host name is configured for a web site, the server will only respond if that particular name is used in the request.
_____________________________
Lee. ___________________________________
Outlook Web Access for PDA and WAP: www.leederbyshire.com ___________________________________
Hi Guys thanks for you help. Internally can connectvia actual_server_name/owa mail.domain.com/owa returns page 404 Not Found externally can connect to domain.com/owa (not mail.domain.com/owa) There is a default website on https:/ /domain.com
Internally Can ping mail.domain.com with reply from wan address cannot ping domain.com........."could not find host domain.com". Externally pinging mail.domain.com "could not find host" Pinging domain.com [wan address appears] request times out.
Internal mail accounts Can send and receive messages to themselves via web connected to domain.net or via mail wan address. Cannot receive external mail 550 5.1.2 host unknown (name server mail.domain.com) Can Send Mail to External recipients.
i was able to receive before recreating reverse lookup zone and deleted mail.domain.local mx record In domain.local zone. Only necessary to have mail.domain.com mx record in domain.com zone? Is it necessary to have A, NS, SOA records in in domain.local zone?
If you ping a server name from the LAN, and it resolves to your public ip address, then your http requests are probably going to the administration web site on your router/firewall (which won't have an /owa directory), although a few of them are clever enough to reflect the requests back in. So yes, you need internal DNS records pointing to your private ip addresses for any server name you want to resolve from the LAN. Obviously any name that doesn't resolve from the WAN needs public DNS records pointing to your public IP address. If your ping attempts don't resolve the name to an IP address, then you need DNS records (public or private, depending on your location - LAN or WAN). It doesn't matter if you don't get a reply to the ping (the WAN pings will probably be blocked by your firewall) as long as you see it resolve a name to an ip address.
_____________________________
Lee. ___________________________________
Outlook Web Access for PDA and WAP: www.leederbyshire.com ___________________________________
Hi Thanks Again There was a conflict with my domain provider and third party DNS forwarding.
a couple of more things if anyone is viewing would be appreciated. Internaly, connections seem to use a different certifcate to connect to exchange . Can any one can tell me which certificate it is so I may update it? Its expired and issued from bangalore???
Second I'm nearly connected owa via outlook. Upto the point of being prompted for login details after configuring proxy server and authentication settings (basic) "the connection to MS exchange is unavailable. Outlook must be online or connected to complete this action." or with NTLM authentication "the name cannot be resolved. The connection to MS exchange is unavailable. Outlook must be online or connected to complete this action."
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2007] >> Outlook Web Access >> connect to mydomain.com not mail.mydomain.com 
connect to mydomain.com not mail.mydomain.com - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
