Hello, When we are going to https://webmail.domain.com/exchange Then we are getting the following error (after we logon): --- HTTP Error 404.2 - Not Found The page you are requesting cannot be served because of the ISAPI and CGI Restriction list settings on the Web server. --- We need this for a third party application. Does anyone have an idea how to solve this? Best regards, Remco

Does this KB help? http://support.microsoft.com/kb/942040

No, all the ISAPI en GCI filters are allowed. Maybe I need to add a new one but if thats the case then I do not know which one I need to add.

Hi, What happens when you try https://webmail.domain.com/owaGulab Prasad, MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007 MCITP: Lync Server 2010 | MCITP: Windows Server 2008 My Blog | Z-Hire Employee Provisioning App Skype: Exchange.Ranger

We have no problems with accessing https://webmail.domain.com/owa.

Is there a reason why you cannot use this URL. /Exchange was for 2003 and is no longer used in 2007/2010.

Agree with Steve, it will always be /owa not /exchangeGulab Prasad, MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007 MCITP: Lync Server 2010 | MCITP: Windows Server 2008 My Blog | Z-Hire Employee Provisioning App Skype: Exchange.Ranger

A thrid party application still uses /exchange, that's the only reason why we need this. We have no 2003 Outlook clients, and everythins else is working perfectly.

/exchange is nothing to do with Outlook client. Exchange 2010 will work with /owa not with /exchange I would talk to the third party vendor regarding it. Gulab Prasad, MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007 MCITP: Lync Server 2010 | MCITP: Windows Server 2008 My Blog | Z-Hire Employee Provisioning App Skype: Exchange.Ranger

Hi Remco Any update on this issue? For 3rd party application integration with Exchange Maybe you can go to 3rd Party Applications Forum to discuss http://social.technet.microsoft.com/Forums/en-US/exchangesvr3rdpartyapps/threads Cheers Zi Feng

You can do this in IIS - just go to your Internet facing CAS server(s) and create a new virtual directory called Exchange (just point it to any folder, I recommend in c:\inetpub\wwwroot and create a new folder). Then select the new folder in IIS manager, and select "error pages". Then open this feature and edit the status code "404" and change it to "Respond with a 302 redirect" and type in the working URL of https://webmail.domain.com/owa If this has helped you (even if you were not the author of this question), then please press the green arrow to mark this as helpful. If this has answered your question, please press "Mark as Answer"

Hi Remco Did you try Chris's suggestion? Cheers

I've removed and recreated the /exchange virtual directory: Remove-OWAVirtualDirectory "-Identity "Exchange (Default Web Site)" -Confirm:$false New-OWAVirtualDirectory -WebsiteName "Exchange (Default Web Site)" -OwaVersion "Exchange2003or2000" -VirtualDirectoryType "Mailboxes" -ExternalAuthenticationMethods Fba After I did that it seems to be working, maybe Chris's suggestion would also work but I didn't try that. Thanks voor your help. Remco