dotnet web services:
The issue is IIS connections are anonymous until login. With a local app, you
do not get a logon box, so you stay anon. Boom!!!
Good starting point:
http://msdn.microsoft.com/library/en-us/dnnetsec/html/SecNetch11.asp I assume you are using HTTP as transport (IIS) as you want the built in
authentication methods. That is fine, but realize you will have to have the
user log in, or have the machines set up to automatically use the user's
account. Network admins can push this out, via policy, to avoid individually
setting up machines.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
[quoted text, click to view] "Ron L" wrote:
> We are working on a distributed VB.Net application which will access a SQL
> database located on a known server. Each client will run on the user's
> local machine. To implement this, we are trying to use remoting for our
> access to the SQL server, with the remoting being via IIS. Since all of our
> users will have accounts in the destination domain, we want to have IIS
> handle the security for us and not allow anonymous. We have set this up
> with one of our development clients and servers, but when we try to connect
> we get the following error message:
> An unhandled exception of type 'System.Net.WebException' occurred in
> mscorlib.dll
>
> Additional information: the remote server returned an error: (401)
> Unauthorized.
>
>
>
> Our configuration is this:
> Component Running on
> Module1 the development machine
> RemotingTest IIS on the development machine
> NorthWind DB SQL Server on another server
>
> IIS is configured for Windows Authentication, and the directory with the
> RemotingTest object has "Script Source Access" set and the Execute
> Permissions are set to "Scripts and Executables". We have also tried with
> setting IIS to Allow Anonymous, which moves the error out to the SQL
> connection (with the error message of "can't make a connection for user
> NULL"). Even if anonymous did work, it would be a problem for us since the
> application we are using requires the username to be accessible.
>
> The SQL server is in a different domain from development machine, however a
> trust relationship exists between the two domains. We have verified that
> the trust works by opening the NorthWind database in Enterprise Manager on
> the development machine.
>
> Can anyone tell us what we are doing wrong here?
>
>
>
We are working on a distributed VB.Net application which will access a SQL
database located on a known server. Each client will run on the user's
local machine. To implement this, we are trying to use remoting for our
access to the SQL server, with the remoting being via IIS. Since all of our
users will have accounts in the destination domain, we want to have IIS
handle the security for us and not allow anonymous. We have set this up
with one of our development clients and servers, but when we try to connect
we get the following error message:
An unhandled exception of type 'System.Net.WebException' occurred in
mscorlib.dll
Additional information: the remote server returned an error: (401)
Unauthorized.
Our configuration is this:
Component Running on
Module1 the development machine
RemotingTest IIS on the development machine
NorthWind DB SQL Server on another server
IIS is configured for Windows Authentication, and the directory with the
RemotingTest object has "Script Source Access" set and the Execute
Permissions are set to "Scripts and Executables". We have also tried with
setting IIS to Allow Anonymous, which moves the error out to the SQL
connection (with the error message of "can't make a connection for user
NULL"). Even if anonymous did work, it would be a problem for us since the
application we are using requires the username to be accessible.
The SQL server is in a different domain from development machine, however a
trust relationship exists between the two domains. We have verified that
the trust works by opening the NorthWind database in Enterprise Manager on
the development machine.
Can anyone tell us what we are doing wrong here?
Have you set the remoting client to pass the default credentials to the
server? If so, how? Also, what happens when you attempt to browse to the
server URL in IE?
[quoted text, click to view] "Ron L" <ronl@bogus.Address.com> wrote in message
news:eg4E7IeZFHA.3220@TK2MSFTNGP14.phx.gbl...
> We are working on a distributed VB.Net application which will access a SQL
> database located on a known server. Each client will run on the user's
> local machine. To implement this, we are trying to use remoting for our
> access to the SQL server, with the remoting being via IIS. Since all of
> our users will have accounts in the destination domain, we want to have
> IIS handle the security for us and not allow anonymous. We have set this
> up with one of our development clients and servers, but when we try to
> connect we get the following error message:
> An unhandled exception of type 'System.Net.WebException' occurred in
> mscorlib.dll
>
> Additional information: the remote server returned an error: (401)
> Unauthorized.
>
>
>
> Our configuration is this:
> Component Running on
> Module1 the development machine
> RemotingTest IIS on the development machine
> NorthWind DB SQL Server on another server
>
> IIS is configured for Windows Authentication, and the directory with the
> RemotingTest object has "Script Source Access" set and the Execute
> Permissions are set to "Scripts and Executables". We have also tried with
> setting IIS to Allow Anonymous, which moves the error out to the SQL
> connection (with the error message of "can't make a connection for user
> NULL"). Even if anonymous did work, it would be a problem for us since
> the application we are using requires the username to be accessible.
>
> The SQL server is in a different domain from development machine, however
> a trust relationship exists between the two domains. We have verified
> that the trust works by opening the NorthWind database in Enterprise
> Manager on the development machine.
>
> Can anyone tell us what we are doing wrong here?
>
>
>
