Exchange 2010 OWA not working via internal IP address...

I have a Dell PET300 running Windows Server 2008 R2 Enterprise and Exchange Server 2010 Standard and all was working as expected.  This morning during my maintenance window I uninstalled the Hyper-V role from the server as we are not going to use it.  As required, the server rebooted and when I tested access OWA externally and internally it did not work.  More troubleshooting steps have revealed the following:

 1.  https://192.168.0.4/owa doesn't work.
 2.  https://localhost/owa works
 3.  https://127.0.0.1/owa works

All of my services appear to be running fine; I just can't figure this issue out.  I even went so far as to install Hyper-V again hoping that would correct the problem, but no luck.  I also ran updatecas.ps1, but again no luck.

Any help would be greatly appreciated!
LVL 1
YortAsked:
Who is Participating?
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.

Simon Butler (Sembee)ConsultantCommented:
Sounds like the wrong IP address is bound in IIS manager, something like that.
Hyper-V does make changes to the networking stack on the server, so you should check the IP address and then look at the bindings in IIS manager. I don't think this is an Exchange issue at all.

Simon.
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
YortAuthor Commented:
Sembee2 - Thank you for your quick response.  I, also, don't think it is an Exchange issue but rather an IIS issue.  Before posting, I did check the bindings and the correct internal IP address of 192.168.0.4 was listed.  Please see attached screen shot.
IIS-screenshot.jpg
0
YortAuthor Commented:
Sembee2 - after looking through IIS and determining everything was setup correctly, I had a hunch to check the local IP address of the Exchange server...low and behold, it was changed back to what it was prior to installation of the Hyper-V.  I changed the IP address to the correct 192.168.0.4 and everything is again working.

Thanks!
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.