|
 |
asp_cdo thread: CDO in ASP
Message #1 by dave.miller@e... on Thu, 23 Aug 2001 18:24:03
|
|
I am very familiar with CDO and MAPI in the VB world, but I have not done
anything in ASP before. Here is the problem...
Exchange 5.0 is on one server, IIS 4.0 is on a different server and I am
working through Interdev at a client station, pointing to a porject folder
on the IIS server.
Within ASP I am creating a CDO session object, and then logging on. I have
a valid username and password for the account I want to access. I do not
get an error return at the logon method invocation. However, when I try to
send a message, I get an error that I do not have authenticated access to
the user account folder.
I tried doing the same thing in VB, and discovered that a credentials
dialog is poppoed, with the User Name I have used, the Domain Name and a
blank password text box. Responding to this box allows me authenticated
access, and all is well.
Probably the same thing would happen in ASP, except my understandng is
that the interface is automatically disabled due to the client-side vs
server-side environment.
Is there a way to get around this that I am missing?? It seems there would
be a way, as OWA would be working under a similar scenario. Does it have
to do with the IIS and Exchange server being on physically different boxes?
Any help would be appreciated!
Message #2 by "Adrian" <adrianto.handisurya@s...> on Fri, 24 Aug 2001 00:40:19
|
|
Check Ed Beck's article 'Getting started with ASP messaging' in MSDN
> I am very familiar with CDO and MAPI in the VB world, but I have not
done
> anything in ASP before. Here is the problem...
>
> Exchange 5.0 is on one server, IIS 4.0 is on a different server and I am
> working through Interdev at a client station, pointing to a porject
folder
> on the IIS server.
>
> Within ASP I am creating a CDO session object, and then logging on. I
have
> a valid username and password for the account I want to access. I do not
> get an error return at the logon method invocation. However, when I try
to
> send a message, I get an error that I do not have authenticated access
to
> the user account folder.
>
> I tried doing the same thing in VB, and discovered that a credentials
> dialog is poppoed, with the User Name I have used, the Domain Name and a
> blank password text box. Responding to this box allows me authenticated
> access, and all is well.
>
> Probably the same thing would happen in ASP, except my understandng is
> that the interface is automatically disabled due to the client-side vs
> server-side environment.
>
> Is there a way to get around this that I am missing?? It seems there
would
> be a way, as OWA would be working under a similar scenario. Does it have
> to do with the IIS and Exchange server being on physically different
boxes?
>
> Any help would be appreciated!
Message #3 by "David A. Miller" <Dave.Miller@e...> on Fri, 24 Aug 2001 14:54:19 -0400
|
|
Thanks Adrian, I will read that over. It looks promising, particularly the
Security aspect. I appreciate your help.
David
-----Original Message-----
From: Adrian [mailto:adrianto.handisurya@s...]
Sent: Friday, August 24, 2001 12:40 AM
To: ASP CDO
Subject: [asp_cdo] Re: CDO in ASP
Check Ed Beck's article 'Getting started with ASP messaging' in MSDN
> I am very familiar with CDO and MAPI in the VB world, but I have not
done
> anything in ASP before. Here is the problem...
>
> Exchange 5.0 is on one server, IIS 4.0 is on a different server and I am
> working through Interdev at a client station, pointing to a porject
folder
> on the IIS server.
>
> Within ASP I am creating a CDO session object, and then logging on. I
have
> a valid username and password for the account I want to access. I do not
> get an error return at the logon method invocation. However, when I try
to
> send a message, I get an error that I do not have authenticated access
to
> the user account folder.
>
> I tried doing the same thing in VB, and discovered that a credentials
> dialog is poppoed, with the User Name I have used, the Domain Name and a
> blank password text box. Responding to this box allows me authenticated
> access, and all is well.
>
> Probably the same thing would happen in ASP, except my understandng is
> that the interface is automatically disabled due to the client-side vs
> server-side environment.
>
> Is there a way to get around this that I am missing?? It seems there
would
> be a way, as OWA would be working under a similar scenario. Does it have
> to do with the IIS and Exchange server being on physically different
boxes?
>
> Any help would be appreciated!
|
|
|
View Cart
