Hi all, Well im not shure if its a issue but its realy bugging me. When executing the command form a CAS server test-owaconnectivity I get an error: CAS1 CCR https://cas1.contoso.local/owa Logon Failure -1 The test was unable to establish a connection to Outlook Web Access. I know why im getting the error, but im not sure why it happening. CAS1 is Windows 2008 SP2 The IIS binding to the OWA website is done with IP addresses (10.1.1.10:443 and 80), the server CAS1 is in DNS (CAS1.contoso.local 10.1.1.10). When i try to open https://cas1.contoso.local/owa from CAS1, it also doenst open. The server doesnt want to resolve its name CAS1 to the IPv4 address 10.1.1.10, instead its resloving it to ::1. And as im not doing the binding with ::1 the OWA wont open localy. Any help is really apreshiated!!! Tnx! Zarko

hi, have you tried checking the network adapter (s) for the CAS server? Looks like its resolving to its ipv6 address try to disable that and see what happens. Also ensure that it has the correct entry for DNS settings.

Another thing you may want to check is the HOSTS file (in the c:\windows\system32\drivers\etc folder by default). In there you will see the loopback address for IPv4 and IPv6. Place a hash (#) just before the ::1 entry (as such: "# ::1 localhost"), save and close the file. From a command prompt, type PING LOCALHOST and it should resolve to the IPv4 now.Thank you, Ibrahim Benna MCSA+Messaging, MCSE+Messaging, MCT, MVP "Did you backup your Information Store Today?!"

Thanks for the reply, Damiola, iv disabled ipv6 on the card, but i didnt do that in the registry. I didnt mention an inportant thing when i ping like ping -4 CAS1, the ip address is resolved corectly. Ibenna, i tried that but its still resolving its self as ::1. If i put CAS1 10.1.1.10 in to the host file then its ok, but im not sure if i should and can do that (im not sure what impact that would have on the CAS server and the Exhcange org), and that isnt the resolution of the problem more of a workaround :)

hi Zack, looks more like a dns issue if the hosts file workaround seems to correct it. Kindly confirm properly that the DNS enteries are correct for the CAS servers. Try recreating the dns records for the cas server!

i will, but i think we have the same issue for all of the win 2008 servers that are hosting our exchange 2007

Hi Zack, Just for troubleshooting purpose, are you sure https (require ssl) is checked on the owa directory in IIS? When you try http://cas1.contoso.local/owa what response do you get?

Sure thing, i get error 403. 403 - Forbidden: Access is denied. You do not have permission to view this directory or page using the credentials that you supplied. All the best Zack

so definitely its https and it should work. now you say you have the issue with your windows 2008 servers, can i ask if having the ip in the refrence in the host file resolves the issue? Also can you shed more light on the exchange design you have now. http://social.technet.microsoft.com/Forums/en/exchangesvrclients/thread/4655b89e-9897-4205-a23a-45cbccde616f you can also read through the above if you find any similarities that may help resolve the issue.

Yes, adding the ip address to the hosts file resolves the issue but im not sure if it has any impact on ne exchange org. Tnx ill read the thread and see if it helps. All of the excahnge server rolles are on seperate servers, and they are all windows 2008 sp2. Im not sure what you are interested in, All the best

Hi, Go through below post: http://social.technet.microsoft.com/forums/en-US/exchangesvrdeploy/thread/37c13f76-5055-44c7-a036-75ff0b207c0e Dinesh

Noup that not the issue Dinesh, but thanks anyway.

hi Zack, have you tried disabling ipv6 in the registry and see what the impact is, cos if the hosts file entry resolves the issue, then it's an indicator that its a name resolution issue. So you can either try the ipv6 workaround or you can re-reate the hosts on the dns server and ensure that you reload the zone to which they belong. Also ensure replication takes place on all available dns servers in your environment. Do keep us updated so we know if you finally resolved this. Thanks!

We didnt try disabling it in the registry, we will have to see if we are going to do that. The main issue is with SCOM as we cant monitor cas servers health complealty whitout the test cmdlet for owa, activesync and webservices.

Hi Zark, If its a scom thing have u created the test user mailbox has required in the exchange server, look through the MP guide for how to cmdlet needed for that. Also you can try to create the scom health connector after going through the guide.

Hi Damilola, As far as i know the users were created correcty (the test-mailflow command is working and im getting the email that are sent by those users), but the test-owaconn... command isnt working localy, if im not mistaking the cmdlet test-owaconnectivity is done locally on every cas server with scom? But ill double check this and see if maby that the issue, but im not sure. Thanks!

I managed to make it work on SCOM, recreated the monitors and set the hosts file on the cas server.