Problems Accessing Website after Exchange install

Hi, having issues where I can no longer connect to the externally hosted website after an exchange 2010 install.  I've tried adding an A record in DNS with www pointing to the external IP of the website but still no luck even with http.

So is exchange impacting on this because of the following and should I just change the internal exch directory details to something else instead of using the same domain name as the website (sorry it's late cant think :-/ ) Please can someone clarify

AD name                            = (also own the address but not used)
web site                              =
Exchange setup to use     =,,,

Could rekey the UCC cert

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.

Tom CieslikIT EngineerCommented:
What kind of website you're talking about ? Its hard to understand.
Do you have problem accessing external website from Exchange server machine or from your network ?
is this regular www address or other ?
jovonnAuthor Commented:
It's just our regular www company website which works externally but not from the internal network and was ok before exchange was added

My point earlier about the same external domin name being used in exchange virtual directories such as auto discover etc shouldn't cause it?
David NeedhamFreelance ConsultantCommented:

While I agree that it should perhaps not cause problems,  using the same domain name internally as you have externally, is not something that I would recommend.  It could very well be that the fact that your are caused this problem.

In all of my installs I have always used .local, or . lcl.  I've then set the Exchange server to masquerade as an externally named device in it's connector/s.

Kind regards,

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
Tom CieslikIT EngineerCommented:
I don't understand your point.
Sorry but can you please clarify ?

1. Is a OWA you talking about or regular www ?
2. On first post you said:
I can no longer connect to the externally hosted website
then in second post you said
regular www company website which works externally but not from the internal network

If I think right you have problem to access regular www website hosted outside and you have not access to it from inside
If this is the case and you sure you did not changed anything in firewall, for some reason request from your inside network to www is poiting to different place.

Can you confirm that ?

Try ping your www website from inside and from outside and compare IP address if is the same?

if is the same IP, double check your firewall settings.
If is different it's mean in your IIS integrated with your DC must be some redirection to different place.

You can create new forward lookup zone named and inside just create a www record with host A pointed to your external website IP.

Refresh DNS on workstation and check if is working.
jovonnAuthor Commented:
sorry for the delay, managed to get this resolved  

we had a divert that was placed in the background for our address on the public side which diverts to the actual live site (

The is the same name used internally for Active Directory so we ended up disabling the divert at the hosting company as it wasn't used - main thing is it's registered to the company.

secondly, the name space supplied in the virtual directories for internal and external on exchange server were the same which is usually recommended  ( However setting up an A record for www just didn't work -  tried a few things!  - split DNS wasn't sending web requests externally to - so ended up using the internal FQDN of the exchange server (also on the exchange cert) in the virtual directories, and changing the SCP for the local clients,  removed the split dns and access was fine again.
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

From novice to tech pro — start learning today.