- It is not clear what authentication you enabled on /test.asp .
- It is not clear whether "remote access" is via a server name, dotted IP,
or FQDN. The format of the name affects whether IE will auto-login, which
may be why you see the login window for the remote case but not local.
- Please search on Google on how to synchronize user account passwords.
In general, "local" and "remote" do not make a difference to IIS unless you
map the two locations to different websites. I suspect you're just seeing
different client authentication behaviors between local and remote
websites -- which affects the authenticated user that is actually launching
your ActiveX EXE, depending on your website configuration (which you have
not disclosed) -- and the identity of the user and its privileges affect
whether your ActiveX EXE works or not.
Ultimately, you need to know what privileges your own code requires, and set
up the server such that it executes as such. If you cannot do this, it is
really hard for anyone to help.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Nirosh" <nirosht.RemoveThis@yahoo.com> wrote in message
news:a184965a.0405180621.24497afa@posting.google.com...
The application works fine when I access it locally(i:e
<a style='text-decoration: underline;' href="http://localhost/test.asp" target="_blank">http://localhost/test.asp</a>) but when I access it remotely it promts the
windows login window..
As for the ActiveX EXE previleges I don't know where to specify the
users who can use...
Can you give me the instruction to manually synchronize user account
pwd's?
What I don't understand is that if the app is working via IIS locally
what could it be lacking to work for remote request and in that matter
the IP address is used to identify the webpage....
Please help me on this issue
I would very much appreciate any help.
Thanks
Nirosh
"David Wang [Msft]" <someone.RemoveThis@online.microsoft.com> wrote in message
news:<OdUm7bIPEHA.736.RemoveThis@tk2msftngp13.phx.gbl>...
> Can you define what privileges your ActiveX EXE actually needs and make
sure
> that IIS has the necessary privileges to execute your code? This is
> something that YOU should know and configure.
>
> #1 does not make sense. It sounds like you're saying that your ActiveX
EXE
> needs credentials as a certain user, which should not use "allow IIS to
> control password".
> #2 does not make sense. IIS does not need to control the password to
allow
> remote access. When you allow anonymous access, it means that IIS will
use
> the defined username/password to execute code. You give the
> username/password for IIS to use -- and if you check "control the
password",
> it means that IIS will elevate privileges to run as that username without
> the password. If anonymous does not work when you uncheck "control the
> password", it means that the username/password you gave to IIS is OUT OF
> SYNC with the real username/password -- so you should manually synchronize
> the two.
>
> Bottom line -- I think that you just need to define what privileges your
> ActiveX EXE actually needs, create a local or domain user that satisfies
> those privileges, and set the username/password inside of IIS as the
> anonymous user, and it should work. If you have further COM
configurations,
> you should also make them consistent with the IIS configuration as far as
> identity goes.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Nirosh" <nirosht.RemoveThis@yahoo.com> wrote in message
> news:a184965a.0405171324.1daca1f6@posting.google.com...
> I have created an application that captures information from ASP page
> and
> produce result for the request. The ASP page instantiate ActiveX EXE
> based class and calls a method...
> Now this web application works fine locally but in order for it to
> work even locally we had to make some changes to IIS.
>
> 1. We had to disable "Allow IIS to control password" for IIS Anonymous
> accounts(IUSR_ComputerName/IWAM_ComputerName) with the exception of
> the 'DOMAINNAME.ComputerName' account.
>
> 2.But we need to allow IIS to control the password if we need to allow
> remote access..
>
> If I force the application not to allow IIS to control password then I
> am getting 'Application-defined or object-defined error'.
>
> Does anyone familiar with this issue?
> Please help me on resolving the issue.
>
> Thanks in advance
>
> Nirosh<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Local Vs Remote Access / IIS to control password 
FAQ
Profile
Private Messages
Log in
