RE: OWA VPN & Outlook

  • From: "Dolly Bareqet" <dolly@xxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 19 Aug 2004 19:16:08 +0200

good question, I also ask my self what I did. I don't remember that I
did something that can reflect this situation.


From: Lara, Greg [mailto:GLara@xxxxxxx] 
Sent: Thursday, August 19, 2004 6:17 PM
To: [ExchangeList]
Subject: [exchangelist] RE: OWA VPN & Outlook

So here's the stock question: what changed 2 days ago?
Greg Lara

This e-mail message may contain privileged, confidential and/or
proprietary information intended only for the person(s) named. If you
are not the intended recipient, please destroy this message, and any
attachments, and notify the sender by return e-mail. If you are not the
intended recipient(s), or the employee or agent responsible for
delivering the message to the intended recipient(s), you are hereby
notified that any dissemination, disclosure or copying of this
communication is strictly prohibited. 



        From: Dolly Bareqet [mailto:dolly@xxxxxxxxxxxx] 
        Sent: Thursday, August 19, 2004 12:25 PM
        To: [ExchangeList]
        Subject: [exchangelist] OWA VPN & Outlook
        Winsows 2000, Exch2k SP3
        Since 2 days ago, my external users are facing big troubled,
they can logon to their mailboxes through OWA. they open VPN connection
and when they try to log on to the mailboxes woth Outlook the fill user,
pass and domain - they get an error of wrong cradentials. 
        Any idea?

        Dolly Bareqet
        Technical Coordinator
        Phone: +972-3-6449333 #260
        Mobile: +972-54-957550
        Fax: +972-3-6449339
        Website: <> 

List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
To unsubscribe visit
Report abuse to listadmin@xxxxxxxxxxxxxx 

Other related posts: