• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 348
  • Last Modified:

Exchange 2003 Outlook Web Access External DNS issue

I recently upgraded to new hardware and OS from Windows 2000/Exchange 2000 to Windows 2003/Exchange 2003 - New server clean install. Email is working correctly without any problems. I have Outlook Web Access set up with a public IP address pointing to the internal server IP and port 443 open on the firewall. Web OUtlook was working correclty on Exchange 2000. I can access Webmail fine internally and can access it externally be using pub.lic.ip/exchange but not by using mail.domain.com/exchange. I have called my ISP and asked them to update the DNS to point to the new public IP of the exchange 2003 server and it still doesn't resolve mail.domain.com. Additionally pop3 is not working either ( I also have pop3 set up on firewall to point public ip to internal ip with approiate ports open)

My question is there anything I should be looking at to try and resolve this or is it something misconfigured at my ISP?

Thanks

Travis
0
tmorrison3
Asked:
tmorrison3
  • 4
  • 2
1 Solution
 
ksharma4Commented:

Check if authentication is correct set.

http://support.microsoft.com/kb/290341/en-us

Thanks
0
 
tmorrison3Author Commented:
Authentication is set to basic and default domain is correct and integrated windows is checked as well

Anonymous is unchecked
digest is unchecked
0
 
SembeeCommented:
DNS Changes can take 48 hours or more to propagate round. If the name resolution externally doesn't resolve to the correct IP address then you may have to just wait longer for the change to propagate.

As for POP3, that is disabled by default. Therefore I presume that you have enabled the service and then started it?
If so, can you define what you mean by not working? If it is authentication related, what are you using for authentication?

username
domain\username
username@domain
domain\username\alias

Something else?

Simon.
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
tmorrison3Author Commented:
I can authenticate fine for webmail using pub.lic.ip/exchange - so that is not an issue
 Pop3 virtual server was not started - thanks! I'll test that now and let you know
0
 
tmorrison3Author Commented:
POP3 is working if I use pub.lic.ip as the in and out address

So - I just need to get DNS from ISP to point to my public exchange IP as everything works correclty? or is there something else I need to do?
0
 
SembeeCommented:
If everything works when you are using the public IP address, then it sounds like it is just DNS that needs to propagate round and you should be working.

Simon.
0
 
tmorrison3Author Commented:
Everything is working correctly now - thanks
Points to Simon for pointing out pop3 oversight

Thanks
0

Featured Post

Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now