Unable to access owa internally in Exchange 2003

My domain changed from company.net to company.com. I created a new virtual directory named exchange2, the default is exchange, with the new domain. I can access owa externally but not internally. I would like to simply delete the second virtual directory and edit the default one with the new domain. In system manager, its greyed out and I don't know where to change it in IIS.

thank you
cyberleo2000Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SISAntCommented:
to access the OWA internally are you using the prefix https://<servername>/owa ?

(though its slightly different for much older versions of windows server i think.)
0
MegaNuk3Commented:
Try https://<e2k3ServerName>/exchange then if that works just add a new internal DNS zone for company.com and then add an A record for mail or owa and point it at your INTERNAL e2k3 server address

Then you should be able to hit https://owa.company.com/exchange internally
0
cyberleo2000Author Commented:
I get internet explorer cannot display the webpage when I try https://servername/exchange 
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

MegaNuk3Commented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cyberleo2000Author Commented:
I tried both. no good.
0
MegaNuk3Commented:
Have a look on your router/firewall at which ip address you are forwarding port 443 to and then take that IP address and try https://<ip address>/exchange
0
SISAntCommented:
I think thing to try here rather than guessing is go into the IIS manager and check what the website is. Though its strange that you've used all the standard ones and they haven't gone through. possible port issue?
0
cyberleo2000Author Commented:
It turns out I had the servername wrong the whole time.
0
MegaNuk3Commented:
Thanks for the update and points
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.