jovonn
asked on
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 = company.com (also own the external.com address but not used)
web site = company.co.uk
Exchange setup to use = mail.company.co.uk, autodiscover.company.co.uk , svrname.company.com, svrname.company.co.uk
Could rekey the UCC cert
Thanks
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 = company.com (also own the external.com address but not used)
web site = company.co.uk
Exchange setup to use = mail.company.co.uk, autodiscover.company.co.uk
Could rekey the UCC cert
Thanks
ASKER
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?
My point earlier about the same external domin name being used in exchange virtual directories such as auto discover etc shouldn't cause it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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:
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 yourexternaldcoman.com 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.
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 websitethen 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 yourexternaldcoman.com 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.
ASKER
sorry for the delay, managed to get this resolved
we had a divert that was placed in the background for our companydomain.com address on the public side which diverts to the actual live site (www.companywebsite.co.uk)
The companydomain.com 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 (mail.companywebsite.co.uk ). 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 companywebsite.co.uk - 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.
we had a divert that was placed in the background for our companydomain.com address on the public side which diverts to the actual live site (www.companywebsite.co.uk)
The companydomain.com 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 (mail.companywebsite.co.uk
Do you have problem accessing external website from Exchange server machine or from your network ?
is this regular www address or other ?