OWA - 'Forbidden' popup when user clicks 'Send'

Exchange 2000

    Next

  • 1. Some users can send but not receive mail
    Hi All Here's a wierd one! Setup 2003SBS with 8 users. 4 users work perfectly however the remaining 4 can send and not receive mail. These 4 with the problem had the .pst file copied into their new local settings folder, ok bad move i now realise. i have tried deleting the mailboxes, removing users and permanently deletin the mailstore and re-booting but the problem still exists. if i create a new user all is well so it looks like these 4 are corrupt. Does anyone have any comments of how i can get out of this hole b4 Monday? Cheers Cogs
  • 2. OL2003 OAB: Exceeded the download limit set by your administrator
    I have 2 users that currently receive the following error during a Send/Receive: Task 'Microsoft Exchange Server' reported error (0x80070005) : 'The Offline Address Book could not be updated because you have exceeded the download limit set by your administrator. Please try again later.' Servers are Exchange 5.5 SP4. As far as I know we have no limit set on the servers for OAB download limits.... didn't know there were any limits I could set. Anyone seen this issue? Any ideas on fixing? My desktop support folks tell me a new Outlook profile doesn't seem to fix it. Let me know!
  • 3. E-Mail Client Suggestions
    A client has a SBS 2K3 server running Exchange 2003 SP2. He has a laptop and it has joined the domain. He's been floundering around trying to find a way to duplicate his LAN experience with Outlook 2003 from afar (Home). He has a Cingular WWAN card so the EDGE network is available to him and his throughput is nearly half that of a basic aDSL connection. He's acquainted with OWA but isn't really impressed by it as there are some Outlook functions it doesn't seem to support. He's now trying to get RCP over HTTP running but isn't sure what he's going to get in the "look-and-feel" department if and when he gets it working. He's also become aware of IMAP access to his server but again, hasn't gotten that working yet either. He'd prefer to avoid using VPN connections to log into the domain from home. Does anyone have a suggestion for which of these alternatives (or any other) provide the closest match to his actual domain connection via his office LAN? From a "look-and-feel" and "function" point of view? I'm really at a loss for how to guide him as I've never experimented with RPC or IMAP for Exchange. I don't know of any place where there is a side-by-side comparision of facilities in an Outlook 2K3 context. All suggestions gratefully received. -- BilBo
  • 4. Configuring a "sent rule" for two exchange mailboxs in a same clie
    Hello, actually i have the current scenario: Windows 2003 SBS with a Exchange 2003 running. I Have 2 mailboxs asociated with their own users, and other mailbox that must be used by this two users. User1 with Mailbox1 - Only for Exchange Locals mails User2 with Mailbox2 - Only for Exchange Locals mails UserX with MailboxA - Pop3 connector, no real user exist. Mailbox viewed by User1 and User2 User1 load in Outlook his own mailbox as primary and also the MailboxA as secondary. When User1 Send a new mail as UserX, the "sent item" appear on his Primary mailbox, i need that each mail send by User1 or User2 (have the same configuration) will be moved to Sent Items of MailboxA. This will able User1 and User2 know what mails have replyed the other user. Well appears to be easy with a Outlook 2003 client rule, but there is not rule that able me to do this far as i saw. Thanks in Advance. aec.
  • 5. OWA read reciept
    Is there a way to automatically return a read receipt besides the user controlled setting in 'options' in the OWA client? A group policy setting or and Exchange server setting?

OWA - 'Forbidden' popup when user clicks 'Send'

Postby Boris Nikolaevich » Thu, 29 Jan 2004 14:30:16 GMT

OWA 2003, Exchange 2003, Windows Server 2003

Users are able to log in to OWA and view messages, and even click "New" to
create a new e-mail.  But when the user clicks "send," a very non-helpful
popup with the single word "Forbidden" pops up.  This is not an HTTP 403
Forbidden page, but a window.alert() [or msgbox() for VBScripters] style
popup.

When I first set up OWA, I had no problem connecting and sending messages.
However, in the course of troubleshooting the "Can't Change Expired Password
in OWA" problem, I now experience this error consistently.

The error seems to occur whether I log in using HTTP or HTTPS, and whether
I'm using Forms Based Authentication or not.

Thanks for any help you can give!

--Boris



Re: OWA - 'Forbidden' popup when user clicks 'Send'

Postby ncointepoix » Fri, 30 Jan 2004 00:19:07 GMT

Boris,

Please let me know if you ever found an answer to this problem. I am
still working on it.

Thanks,

Norbert




Re: OWA - 'Forbidden' popup when user clicks 'Send'

Postby Boris Nikolaevich » Fri, 30 Jan 2004 04:05:19 GMT

Still no solution.  It's odd, to me, that this appeared as a client-side
problem, since a) the changes I've made per MS and newsgroup posts have all
been server-side and b) the client (aka Internet Explorer) connects to OWA
via HTTPS and has the site listed in Trusted Sites (so there should not be
any JavaScript security issues).

Thanks, though, for letting me know I'm not alone!  I will DEFINITELY post
when I find a solution.  (After all, that's how I finally configured Outlook
2003 to connect via RPC over HTTP -- someone with the same problem posted
back when they found a solution!  Turns out you can only log in using
DOMAIN\user when connecting this way (the AD-style  XXXX@XXXXX.COM 
won't work).  I didn't find anything about this in any documentation, only
in that single follow-up post!)

--Boris








to
non-helpful
messages.
Password
whether



Re: OWA - 'Forbidden' popup when user clicks 'Send'

Postby Boris Nikolaevich » Thu, 04 Mar 2004 15:46:51 GMT

This turned out to be an IIS permissions issue.  Make sure that the web has
Write permissions enabled -- if users can't save a new message to the queue,
they can't send it!






all
Outlook






"New"
403
style



Similar Threads:

1.OWA - 'Forbidden' popup when user clicks 'Send' (Solution)

I believe I solved the problem by making sure the Exchange virtual directory
had "Read", "Write", and "Directory Browsing" enabled.  (In other words,
users can't create new messages if they can't write to the store!)

"Boris Nikolaevich" < XXXX@XXXXX.COM > wrote in message
news:e6BsS$ XXXX@XXXXX.COM ...
> OWA 2003, Exchange 2003, Windows Server 2003
>
> Users are able to log in to OWA and view messages, and even click "New" to
> create a new e-mail.  But when the user clicks "send," a very non-helpful
> popup with the single word "Forbidden" pops up.  This is not an HTTP 403
> Forbidden page, but a window.alert() [or msgbox() for VBScripters] style
> popup.
>
> When I first set up OWA, I had no problem connecting and sending messages.
> However, in the course of troubleshooting the "Can't Change Expired
Password
> in OWA" problem, I now experience this error consistently.
>
> The error seems to occur whether I log in using HTTP or HTTPS, and whether
> I'm using Forms Based Authentication or not.
>
> Thanks for any help you can give!
>
> --Boris
>
>


2.OWA on Exch2003: "Forbidden" popup when sending mail

New install of SBS2003 with Exchange 2003; all seems to be working okay 
except users cannot send or reply to messages using OWA. Instead, a popup 
comes up with only the word "Forbidden" and nothing else.

I have seen many newsgroup postings on the net regarding this, but no 
specific fixes. This is not related to "FreeDocs" or other issues; I believe 
it may have something to do with write access in IIS on the default web site, 
where OWA resides, but again I cannot find a specific solution.

Any ideas?  Thanks in advance.

3.I got 'forbidden' popup message OWA.

I got 'forbidden' popup message when sending, replying 
emails using OWA. Please help! Also any configuration 
change gives me a also "Denied" Help please!

4.OWA Forbidden popup

When sending an email via OWA, upon clicking send, a 
popup comes that says Forbidden.  The message is not sent.

This also occurs for fowarding/replying and across all 
users.

There was another post about this last month, but no 
replies.  Has anyone else seen this?



Return to Exchange 2000

 

Who is online

Users browsing this forum: No registered users and 80 guest