Re: link to a folder under Public Folders

That all sounds okay. Is there any kind of third-party AV scanner or
firewall installed on the server? If so, can you see any settings in there
to check incoming http requests for escape characters, such as the %xx
characters in the URLs?

"SP_1" <none@xxxxxxx> wrote in message
news:Ou7Rz6WNJHA.456@xxxxxxxxxxxxxxxxxxxxxxx
Ok, I right-click on Public, select Properties | Directory Security |
Edit...Authentication and access control, and here are what I got in the
Authentication Methods screen.

-Enable anonymous access: blank
-Integrated Windows authentication: blank
-Digest authentication for Windows domain server: blank
-Basic authentication (password is sent in clear text): Checked
-.NET Passport authentication: blank

-Default domain: \
-Realm: blank

These are the same for Exchange VDir.
Steve


"Lee Derbyshire [MVP]" <email a@t leederbyshire d.0.t c.0.m> wrote in
message news:uAmXCFRNJHA.5692@xxxxxxxxxxxxxxxxxxxxxxx
OWA would still want to use the redir.asp file to check what you are
linking to. It's when you try to run that redir.asp file that you get
this strange 403.0 error. Can you check to make sure in IIS Manager that
you have the same security settings on your Public VDir and Exchange
VDir. Including the Default Domain for Basic Auth.

"SP_1" <non@xxxxxxx> wrote in message
news:FBC02035-E707-4FEC-883C-5E248C9A3C6F@xxxxxxxxxxxxxxxx
By the way, could you create a similar link in your Outlook for it to
work in OWA ?

In any case, here is what I got from IIS Manager | Web Service
Exntensions.

-All Unknown CGI Extension: Prohibited
-All Unknown ISAPI Extensions: Prohibited
-Active Server Pages: Allowed
-ASP.NET v1.1.4322: Allowed
-ASP.NET v2.0.50727: Allowed
-Internet Data Connector: Prohibited
-Microsoft Exchange Server: Allowed
-RPC Proxy Server Extension: Allowed
-Server Side Includes: Prohibited
-WebDAV: Prohibited

Thanks again
Steve

"Lee Derbyshire [MVP]" <email a@t leederbyshire d.0.t c.0.m> wrote in
message news:eqqjyOENJHA.2760@xxxxxxxxxxxxxxxxxxxxxxx
Ugh. It's a 403.0 error, which isn't even listed as a valid response
in IIS. It's probably something it can't recognise, like Active Server
Pages isn't installed as a component, or the ASP Web Services Extension
isn't enabled.

Can you access any other .asp files on the server? E.g. if you have
FBA enabled, and it works, then you can.



"SP_1" <none@xxxxxxx> wrote in message
news:%23aLXGP7MJHA.1308@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for the follow-up. Again, if I clicked on the Click Here link
from within OWA, a new IE window opened up - saying HTTP 403 Forbidden
... The website declined to show this webpage. The error went on to
say... Most likely causes: This website requires you to log in.

Here are the 2 lines of record that I could track down in the log file
(under folder C:\WINDOWS\system32\LogFiles\W3SVC1 of the Exchange
server).

2008-10-21 19:15:38 W3SVC1 10.14.85.105 GET
/exchange/myXYZaccount/Inbox/RE:+link2.EML cmd=preview&mime=1 443
myXYZaccount 192.168.2.148
Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+(R1+1.5);+.NET+CLR+1.0.3705;+InfoPath.1)
200 0 0

2008-10-21 19:15:43 W3SVC1 10.14.85.105 GET /exchweb/bin/redir.asp
URL=https://myDOMAIN/public/general%20documents/job%20-%20internal%20postings
443 myXYZaccount 192.168.2.148
Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+(R1+1.5);+.NET+CLR+1.0.3705;+InfoPath.1)
403 0 0

Thank you
Steve

"Lee Derbyshire [MVP]" <email a@t leederbyshire d.0.t c.0.m> wrote in
message news:%23%23lqsPFMJHA.3080@xxxxxxxxxxxxxxxxxxxxxxx
Can you post the logged 403 response from the IIS log file? There
are about 20 different types of 403 in IIS, and the logged subcode
will indicate a specific cause. Hopefully.


"SP_1" <none@xxxxxxx> wrote in message
news:OoK6ef$LJHA.2164@xxxxxxxxxxxxxxxxxxxxxxx
Just an update...

Ok, so I created a "Click Here" with an embedded link to a folder in
Public Folders. The link only worked if clicked it from Outlook; it
doesn't work (or 403 error) if I clicked it from OWA.

Meaning...when I clicked on the Click Here link from within Outlook,
IE7 opened up and prompted for username/password. After logon,
voila, it went straight to the folder that I needed. But, this
would defeat the purpose of Outlook. If I'm in Outlook, I might as
well access the Public Folders from within Outlook. I wouldn't need
to go to OWA.

My main objective is to get the link to work for those users who do
not have Outlook (ie. only having OWA). The problem remains that
when I read the message from OWA and click on the link, I get the
403 error as if the link requires some sort of authentication.

So, the link typo was correct as it did work from Outlook.

Steve




"SP_1" <none@xxxxxxx> wrote in message
news:%23g6ujs8LJHA.4536@xxxxxxxxxxxxxxxxxxxxxxx
Hi

I did use https, and I still got the 403 error. Again, this is
clicking on the click HERE from within OWA.

Any other idea ?

Steve

"Lee Derbyshire [MVP]" <email a@t leederbyshire d.0.t c.0.m> wrote
in message news:ux2K9t4LJHA.3744@xxxxxxxxxxxxxxxxxxxxxxx
"SP_1" <none@xxxxxxx> wrote in message
news:e7HbWSwLJHA.5472@xxxxxxxxxxxxxxxxxxxxxxx
Hi

Say, there is an "ABC" folder (under the All Public Folders), and
I'd like to send a message to everyone who uses OWA about how to
get to this folder. The message would say something like this: To
access ABC folder, click HERE.

From Outlook, I tried to embed various hyperlinks that pointed to
the ABC folder, but when I read the message from within OWA, I
got a HTTP 403 Forbidden error when I clicked on the click HERE
link.

Is it possible to have a hyperlink embedded in the "click HERE"
for OWA use ? And what is that URL ?

Thanks
Steve
ps. I don't have problem getting the link to work if I click on
it from within Outlook - only in OWA that I have problem.

Which version of Exchange? If it's 2000 or 2003, you would use
http://server/public/folder+name . Spaces in the folder name are
escaped with + or %20 . If you require SSL, you should use
https - if you didn't use https, this might explain the 403
response.

Lee.

--
______________________________________

Outlook Web Access For PDA , OWA For WAP
www.leederbyshire.com
email a@t leederbyshire d.0.t c.0.m
______________________________________


















.

Relevant Pages

  • Re: Cannot reply/forward in OWA - Page cannot be displayed
    ... I understand all the pictures in the OWA ... Check if OfficeScan is installed on the SBS server. ... Microsoft is providing this information as a convenience to you. ... Locate the Urlcache folder. ...
    (microsoft.public.windows.server.sbs)
  • Re: link to a folder under Public Folders
    ... Authentication Methods screen. ... from within OWA, a new IE window opened up - saying HTTP 403 Forbidden ... so I created a "Click Here" with an embedded link to a folder in ... Meaning...when I clicked on the Click Here link from within Outlook, ...
    (microsoft.public.exchange.clients)
  • Re: link to a folder under Public Folders
    ... Can you post the logged 403 response from the IIS log file? ... Meaning...when I clicked on the Click Here link from within Outlook, ... straight to the folder that I needed. ... I wouldn't need to go to OWA. ...
    (microsoft.public.exchange.clients)
  • Re: link to a folder under Public Folders
    ... Can you send yourself a link and see if it works in OWA? ... Edit...Authentication and access control, and here are what I got in the Authentication Methods screen. ... so I created a "Click Here" with an embedded link to a folder in Public Folders. ... Meaning...when I clicked on the Click Here link from within Outlook, IE7 opened up and prompted for username/password. ...
    (microsoft.public.exchange.clients)
  • Re: link to a folder under Public Folders
    ... It's probably something it can't recognise, like Active Server Pages ... so I created a "Click Here" with an embedded link to a folder in ... Meaning...when I clicked on the Click Here link from within Outlook, ... I wouldn't need to go to OWA. ...
    (microsoft.public.exchange.clients)