First Last
asked on
Outlook Web Access URLs won't open
I've noticed a problem that our web access users have been running into. When they are sent emails with links and they click on it instead of opening the address as written they get something similar to the following which never gets past a blank IE window:
https://10.35.208.101/owa/redir.aspx?C=5hTVl8OnX0q3gdexCsZsBdyEuNpUQdAIfSKW4MnCUnIJo1XTSt6HzXNGWo6JCEF4xF6ktxDSkdI.&URL=file%3a%2f%2f%2f%5c%5ccunj-file3%5cpublic%5cMarketing%5c2013%5cMarketing%2520Bulletins%5cMB41-Market-Linked%2520Certificates%2520of%2520Deposit%2520Seminar.htm
10.35.208.101 is the OWA server. I'm not sure why it stops at the redirection URL and never goes past it, any ideas?
https://10.35.208.101/owa/redir.aspx?C=5hTVl8OnX0q3gdexCsZsBdyEuNpUQdAIfSKW4MnCUnIJo1XTSt6HzXNGWo6JCEF4xF6ktxDSkdI.&URL=file%3a%2f%2f%2f%5c%5ccunj-file3%5cpublic%5cMarketing%5c2013%5cMarketing%2520Bulletins%5cMB41-Market-Linked%2520Certificates%2520of%2520Deposit%2520Seminar.htm
10.35.208.101 is the OWA server. I'm not sure why it stops at the redirection URL and never goes past it, any ideas?
ASKER
They're using it inside the LAN to access a file share also on the LAN which I think is the problem. The results are the same whether we use the DNS name or IP. HTTP works fine.
So that IP address is actually a file server link? or is the IP the OWA server?
What kind of link are you seeing?
The behaviour of OWA to route email through redir.aspx is normal - it is there to protect the Exchange server. It has to be something about the original link that is the problem.
Simon.
The behaviour of OWA to route email through redir.aspx is normal - it is there to protect the Exchange server. It has to be something about the original link that is the problem.
Simon.
ASKER
Here is an example of a UNC link that our Marketing department sends out regularly that OWA users have trouble opening:
\\cunj-fileserver\public\M arketing\2 013\Market ing Bulletins\2013 Marketing Bulletins.htm
When they click on it they get the above IE page which goes no further. External links to websites seem to work fine.
\\cunj-fileserver\public\M
When they click on it they get the above IE page which goes no further. External links to websites seem to work fine.
OWA has always struggled with UNC links.
Try it in < > - so <\\host\share\share\file.h tm>
Simon.
Try it in < > - so <\\host\share\share\file.h
Simon.
ASKER
Worth a try and using <> does create a nice link but OWA still it still stalls at this address:
https://10.35.208.101/owa/redir.aspx?C=6IcuXWkB4UKLjNJPYmVH0vc0LnwdQtAI9ATZEUiQBX8g-4nPNXYULAeIoECDHq7TRhnyHrCVxJk.&URL=file%3a%2f%2f%2f%5c%5cFileServer%5cpublic%5cerror.jpg
I was using this UNC path:
<\\fileserver\public\error .jpg>
I also tried it logging in with the FQDN of the exchange server but had the same results.
https://10.35.208.101/owa/redir.aspx?C=6IcuXWkB4UKLjNJPYmVH0vc0LnwdQtAI9ATZEUiQBX8g-4nPNXYULAeIoECDHq7TRhnyHrCVxJk.&URL=file%3a%2f%2f%2f%5c%5cFileServer%5cpublic%5cerror.jpg
I was using this UNC path:
<\\fileserver\public\error
I also tried it logging in with the FQDN of the exchange server but had the same results.
Lots of others seem to have reported the problem.
The only other thing that might work is file:\\ in front.
Simon.
The only other thing that might work is file:\\ in front.
Simon.
ASKER
Interesting...I'm on the most recent version of exchange 2010, very surprising its still a problem for many people. I tried using file:\\ and it also makes a nice link in blue but I get the same problem.
I'd be very interested if someone has a work-around for the problem. At the moment I'm having users copy/paste the link.
I'd be very interested if someone has a work-around for the problem. At the moment I'm having users copy/paste the link.
ASKER
Standing by...
ASKER
Why was this closed, there has been no resolution
ASKER
Thank you!
ASKER
Any updates for me? Its not a huge problem but at the moment I've got nothing...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi spaperov, I've found the same contradictory links in Technet. I've been looking at this for weeks and my conclusion is what you've found in the last link, its no longer supported. Thanks!
I have never seen an OWA setup that doesnt use DNS rather than IP address, so somethings wrong there.
My guess would be that your users trying to access it dont have access to 10.35.208.101 as its a private IP address that only works inside your network.