AUTHORIZATION with WINDOWS AUTHENTICATION HELP!

i want to implement authorization with windows authentication and don't
have the slightest clue of how to do this implementation. the basic
windows authentication for this .NET application is already setup. my
problem lies within my inability to manipulate the username captured in
the authentication process and my knowledge of how IIS is involved.

specifically, i have the following questions:
1) what object(s) can be used so that the user's username can be
manipulated for the authorization process?
2) in order to apply roles, do the users need to be placed in groups in
IIS? if so, how does this work?
3) is all the code that the application uses for roles in web.config?
or does global.asax play a role in this matter?
4) does the web.config file know to communicate with IIS because the
authorization type is set to windows?
5) once authorization is in place, can a section of an .aspx file be
visible to a group or can only entire files be secured for a group?

as you can see, i'm trying to figure out the relationship between
authorization and windows authentication so any help would be
appreciated.

thanks,
john
e: phreeskier@.gmail.comThis is the wrong group, try one of the microsoft.*dotnet* groups.

Authorization windows - Invalid authorization specification

Hi, Experts.
Another problem with Reporting Services authentication:
We have a windows 2003 server + iis 6.0 +Reporting Setvices
whose reports access to a sql server windows 2003 (both are situated
in the same domain).
Since I must use stored credentials in order to create subscriptions
I've decided to put a user from domain windows in stored
authentication.
As the result I´ve obtain the following error:
Error al procesar el informe. (rsProcessingAborted) Obtener ayuda en
línea
No se puede crear una conexión al origen de datos Ventas.
(rsErrorOpeningConnection) Obtener ayuda en línea
Invalid authorization specification
The user I've chosen is the same that I use to design reports and to
access the sql server usually, so I don´t understand the cause of this
error.
Good. Seeing that it has not work I´ve changed the user to "sa" and
everything works fine.
The unique problem I have that according to the policy secuirty of the
company
it is forbidden to use the sa user in order to execute the reports.
Windows authentication is strongly recommended. Any idea?
Regards
Maciej KiewraHi, Experts.
The ServicePack is the real reason of my problem.
I´ve removed RS and I've installed it again (without applying service pack)
everything ok.
Then I've installed the servicepack and now "windows authentication" does not work.
I know that in the service pack 1 a new System Property has been add that
permits the windows authentication to be disabled, but this parameter is set
to true, so it is not a case.
It seems that Reporting Service is already very premature
Regards
Maciej Kiewra
mkiewra@.mail.fujitsu.es (Maciej Kiewra) wrote in message news:<bc86bf57.0504050912.36611411@.posting.google.com>...
> Hi, Experts.
>
> Another problem with Reporting Services authentication:
> We have a windows 2003 server + iis 6.0 +Reporting Setvices
> whose reports access to a sql server windows 2003 (both are situated
> in the same domain).
> Since I must use stored credentials in order to create subscriptions
> I've decided to put a user from domain windows in stored
> authentication.
> As the result I´ve obtain the following error:
> Error al procesar el informe. (rsProcessingAborted) Obtener ayuda en
> línea
> No se puede crear una conexión al origen de datos Ventas.
> (rsErrorOpeningConnection) Obtener ayuda en línea
> Invalid authorization specification
> The user I've chosen is the same that I use to design reports and to
> access the sql server usually, so I don´t understand the cause of this
> error.
> Good. Seeing that it has not work I´ve changed the user to "sa" and
> everything works fine.
> The unique problem I have that according to the policy secuirty of the
> company
> it is forbidden to use the sa user in order to execute the reports.
> Windows authentication is strongly recommended. Any idea?
> Regards
> Maciej Kiewrasql

Authorization ticket not received by LogonUser

Hi, I integrated with
ReportingServices using Forms Authentication followed the instruction of the
article from microsoft, it works fine on my laptop (Windows 2003 server and
sql2000), but when I try to duplicate it on our company server (windows 2000
and sql2000), I always got the error: Authorization ticket not received by
LogonUser, when I try to login as the ReportAdmin user.
Could someone help?
Thank you at advance.
YanDid you ever find a solution this problem?
I'm having the same issue. It works on my LapTop but when I duplicate
exactly what I have on the Server, it doesn't work.
Thanks.
"Authorization ticket" wrote:
> Hi, I integrated with
> ReportingServices using Forms Authentication followed the instruction of the
> article from microsoft, it works fine on my laptop (Windows 2003 server and
> sql2000), but when I try to duplicate it on our company server (windows 2000
> and sql2000), I always got the error: Authorization ticket not received by
> LogonUser, when I try to login as the ReportAdmin user.
>
> Could someone help?
> Thank you at advance.
> Yan|||Make sure the <UrlRoot> element value in the RSReportServer.config file is
the same URL value you are using to call the ReportService.asmx.
This error will happen if you have <UrlRoot> =http://MACHINENAME/ReportServer and you are calling the web service like
http://localhost/ReportServer/ReportService.asmx
Not sure if that's the issue but it's something to check. For the auth
cookie to work, the cookie domains have to be the same.
--
Adrian M.
MCP
"Jon-Slem" <JonSlem@.discussions.microsoft.com> wrote in message
news:C1AC412B-0DCA-4F69-A590-650CDB81B344@.microsoft.com...
> Did you ever find a solution this problem?
> I'm having the same issue. It works on my LapTop but when I duplicate
> exactly what I have on the Server, it doesn't work.
> Thanks.
> "Authorization ticket" wrote:
>> Hi, I integrated with
>> ReportingServices using Forms Authentication followed the instruction of
>> the
>> article from microsoft, it works fine on my laptop (Windows 2003 server
>> and
>> sql2000), but when I try to duplicate it on our company server (windows
>> 2000
>> and sql2000), I always got the error: Authorization ticket not received
>> by
>> LogonUser, when I try to login as the ReportAdmin user.
>>
>> Could someone help?
>> Thank you at advance.
>> Yan|||I don't get it.
I fixed this and I'm still getting the error. I didn't even have do this on
my laptop.
Did your work right after you made the change? I made the change in the
ReportingService.cs file, I changed it to the machine name. The config file
was already the machine, no change was need there.
If you have any idea, please give my a buzz.
Thank.
"Adrian M." wrote:
> Make sure the <UrlRoot> element value in the RSReportServer.config file is
> the same URL value you are using to call the ReportService.asmx.
> This error will happen if you have <UrlRoot> => http://MACHINENAME/ReportServer and you are calling the web service like
> http://localhost/ReportServer/ReportService.asmx
> Not sure if that's the issue but it's something to check. For the auth
> cookie to work, the cookie domains have to be the same.
> --
> Adrian M.
> MCP
> "Jon-Slem" <JonSlem@.discussions.microsoft.com> wrote in message
> news:C1AC412B-0DCA-4F69-A590-650CDB81B344@.microsoft.com...
> > Did you ever find a solution this problem?
> > I'm having the same issue. It works on my LapTop but when I duplicate
> > exactly what I have on the Server, it doesn't work.
> > Thanks.
> >
> > "Authorization ticket" wrote:
> >
> >> Hi, I integrated with
> >> ReportingServices using Forms Authentication followed the instruction of
> >> the
> >> article from microsoft, it works fine on my laptop (Windows 2003 server
> >> and
> >> sql2000), but when I try to duplicate it on our company server (windows
> >> 2000
> >> and sql2000), I always got the error: Authorization ticket not received
> >> by
> >> LogonUser, when I try to login as the ReportAdmin user.
> >>
> >>
> >> Could someone help?
> >>
> >> Thank you at advance.
> >>
> >> Yan
>
>

Authentication/Security Issue!

Hi,
I have installed SQL reporting services on the local system test machine
[standard edition] which points to a DB that is on a different machine.
Everything works ok if I use a domain account and assign security rights for
each report. But in production I will want to have a local windows account
and assign read rights on the reports individually. I tried doing this in
the test environment.
When I try to access the site using the IP I get the windows log on box.
After entering the local user account I can get to the reports but as soon
as I try and run the report it gives me this error:
The permissions granted to user [domain\user] are insufficient for
performing this operation. (rsAccessDenied)
The problem is i am not logged on as a domain user but as a local machine
user.
Was wondering if any of you have come across this error before and possibly
know the cause/solution to this.
Thanks for your help!
Regards
AnilHi Anil:
Even if you go to an IP address for the server, when you run a report
the report is rendered by an IFRAME element with the URL pointing to
the report server by name.
To verify this behavior, just right-click in the report area, select
properties, and look at the URL. You'll notice your address bar might
look like http://x.x.x.x, but the report properties URL will indicate
http://reporting. The server always uses the <ReportServerUrl> element
in RSWebApplication.config.
Since the IFRAME points you back to the server by name, IE is probably
automatically logging you in again with your domain account, which is
not in a Browse role. You can change IE's behavior in Tools ->
Internet Options -> Security -> Custom Level -> User Authentication
(at the bottom of the list).
--
Scott
http://www.OdeToCode.com
On Mon, 16 Aug 2004 12:31:41 +1200, "anil" <test@.test.com> wrote:
>Hi,
>I have installed SQL reporting services on the local system test machine
>[standard edition] which points to a DB that is on a different machine.
>Everything works ok if I use a domain account and assign security rights for
>each report. But in production I will want to have a local windows account
>and assign read rights on the reports individually. I tried doing this in
>the test environment.
>When I try to access the site using the IP I get the windows log on box.
>After entering the local user account I can get to the reports but as soon
>as I try and run the report it gives me this error:
>
>The permissions granted to user [domain\user] are insufficient for
>performing this operation. (rsAccessDenied)
>The problem is i am not logged on as a domain user but as a local machine
>user.
>Was wondering if any of you have come across this error before and possibly
>know the cause/solution to this.
>Thanks for your help!
>Regards
>Anil
>

authentication/db connection issues with new setup

Hi,
I've pretty much just thrown together a reporting services (2005)
configuration which connects to a mature sql server 2000 database held
elsewhere. Forgive me for probably not having too much of a clue
about how things should be set up, but I had a go.
I'll get straight to the problem.. that is I can view reports from the
machine running the server, using my own credentials or those of
someone else (tested by running IE7 under an alternative account on
the domain).
However, when using those same user credentials but from a different
machine, I get the following error:
An error has occurred during report processing.
Cannot create a connection to data source 'dsTachyon'.
Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection.
Any ideas as to what would be causing this?
cheers,
ChrisMy guess is that it's a "double hop" authentication problem.
You can connect directly to the db when you're on the server, which is a
direct connection. But when you're trying to connect to the db through the
report server, you have one connection hop from your pc to the report
server, and one hop from the report server to the db server. This is called
a double hop.
There are two ways of fixing it.
1) You can connect to the db with a static account that has read access to
the db you get your data from. Instead of using Windows Integrated
Authentication, you use "Credentials stored securely in the report server".
This can be either a SQL account or a Windows account. If you use this, make
sure you're encrypting the data in your report database, in order to encrypt
the password you add.
2) Configure the report server and the db server to use Kerberos, to allow
the credentials to be sent from your pc through the report server to the db
server.
If you want to use Kerberos, start by reading
Configuring Authentication for Reporting Services
http://msdn2.microsoft.com/en-us/library/bb283249.aspx
Specifying Credential and Connection Information
http://msdn2.microsoft.com/en-us/library/ms160330.aspx#
And
Configuring Constrained Delegation for Kerberos (IIS 6.0)
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/df979570-81f6-4586-83c6-676bb005b13e.mspx?mfr=true
You also need to make sure Anonymous Access to the Report Server web
application is not allowed.
My suggestion is to first see if you're able to connect to the data with the
first setup (using a static account). If it works, you should use Kerberos,
as this is a more secure solution. If it doesn't work with a static account,
you might want to work out why before setting up Kerberos, because it's
usually easier, but less secure to make it work with a static account.
Kaisa M. Lindahl Lervik
"Not Me" <clhumphreys@.gmail.com> wrote in message
news:1174310214.836485.140910@.n59g2000hsh.googlegroups.com...
> Hi,
> I've pretty much just thrown together a reporting services (2005)
> configuration which connects to a mature sql server 2000 database held
> elsewhere. Forgive me for probably not having too much of a clue
> about how things should be set up, but I had a go.
> I'll get straight to the problem.. that is I can view reports from the
> machine running the server, using my own credentials or those of
> someone else (tested by running IE7 under an alternative account on
> the domain).
> However, when using those same user credentials but from a different
> machine, I get the following error:
> An error has occurred during report processing.
> Cannot create a connection to data source 'dsTachyon'.
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection.
> Any ideas as to what would be causing this?
> cheers,
> Chris
>|||On 19 Mar, 14:00, "Kaisa M. Lindahl Lervik" <kais...@.hotmail.com>
wrote:
> My guess is that it's a "double hop" authentication problem.
> You can connect directly to the db when you're on the server, which is a
> direct connection. But when you're trying to connect to the db through the
> report server, you have one connection hop from your pc to the report
> server, and one hop from the report server to the db server. This is called
> a double hop.
Thank you! Great depth to your reply, I've tried the static account
solution and that works so I'll give Kerberos a look.
Cheers,
Chris

Authentication, windows or custom

I have read most of the threads regarding form authentication as well as the suggested articles. Unfortunately I am not clear if I need to do custom security or stay with windows authentication

I would like to access a specific report using a URL so that all the features and funcionalty of the report is available to the user. There are to many users and reports to assign and maintain individual users and/or groups to a specific report.

Our users would access the report from either a windows or web application having already passed security. They would have a button to press to obtain the report. We would prefer to pass a specific userid to report services at this point that is authorized to view the report.

Can this be done without switching to custom security? To use form authentication must you switch to custom security? Would impersonation work?Hi,

If you go with Windows Authentication, then you can retrieve the Windows UserId from the Thread class - Thread.CurrentPrincipal.Identity.Name

Regards,
Vikram

Authentication With RS 2000

I am using RS 2000 Eval Edition
I have just enstalled it on my notebook. This is where my existing copy of
SQL Server 2000 resides. The SQL 2000 Server is working fine (as it has for
the past several months)
I installed RS 2000 Eval Edition using all of the "default" settings. I
then re-booted, and installed both RS 2000 Service Packages. ASP.net is
running, and I have verified this.
When I try to open the Report Manager a window pops up and states an
Authentication Required. It prompts me for a User Name and Password. When I
try to type in the Windows User Name and password, it fails. When I try to
type in the Username and password for the SQL 2000 Database it fails.
What am I doing wrong. I have installed RS 2000 Eval on another computer
several years ago so I know what the Report Manager looks like.
Further, I have tried simply going to the Internet and typing in several
variations of: http://<ServerName> directly. Each time it prompts for
Authentication.
I am becoming very frustrated and very angry. It should not be so difficult.
Any suggestions would be welcomed. Also, I have been asked to undertake
this work using SQL 2000 and RS 2000 so please don't tell me to get of of the
dark ages and upgrade to SQL 2005 and RS 2005!
PatHi Again...
I solved my problem by changing the Anonymous Access and Authentication
Control settings in the Default Website folder in my IIS settings.
Thanks
Pat
"Pat (Disciple of Aloof-ism)" wrote:
> I am using RS 2000 Eval Edition
> I have just enstalled it on my notebook. This is where my existing copy of
> SQL Server 2000 resides. The SQL 2000 Server is working fine (as it has for
> the past several months)
> I installed RS 2000 Eval Edition using all of the "default" settings. I
> then re-booted, and installed both RS 2000 Service Packages. ASP.net is
> running, and I have verified this.
> When I try to open the Report Manager a window pops up and states an
> Authentication Required. It prompts me for a User Name and Password. When I
> try to type in the Windows User Name and password, it fails. When I try to
> type in the Username and password for the SQL 2000 Database it fails.
> What am I doing wrong. I have installed RS 2000 Eval on another computer
> several years ago so I know what the Report Manager looks like.
> Further, I have tried simply going to the Internet and typing in several
> variations of: http://<ServerName> directly. Each time it prompts for
> Authentication.
> I am becoming very frustrated and very angry. It should not be so difficult.
> Any suggestions would be welcomed. Also, I have been asked to undertake
> this work using SQL 2000 and RS 2000 so please don't tell me to get of of the
> dark ages and upgrade to SQL 2005 and RS 2005!
> Pat
>

authentication with mssql server

Currently all of our MS SQL Server databases have been installed so as once an administrator connects to the server they can get access to the SQL Server database. We would like to change this to ensure that no matter who you are you have to enter a valid username and password in SQL Server to connect to the database. I cannot seem to find out how to do this. All help will be greatly appreciated.

Thanks
SamRefer to books online for AUTHENTICATION MODES & other related topics which covers what you're looking for. Adopt Mixed mode authentication if you would like to enter user/password during the connection.

Authentication with MSSQL 2005 Mobile Merge Replication

Hi,
I'm using MSSQL 2005 Mobile subscriber to partitioned publication (with
merge replication). In my case the partition is security-related, so it's
important to ensure that different subscribers will get only their own data.
Since I can't use SUSER_NAME(), and since HOST_NAME() can be overriden, what
are the options to authenticate the user properly?
Thanks,
Vladimir K.
You can use suser_name, it maps to publisherlogin, I also don't quite
understand what you mean by host_name can be overridden - it can be
overridden by the hostname parameter in your merge replication class
(SQLCeReplication) to define whatever you want, which could be the account
name you wish to filter by.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Vladimir Kofman" <vladimir.kofman@.gmail.com> wrote in message
news:u9lqmIRSHHA.4832@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I'm using MSSQL 2005 Mobile subscriber to partitioned publication (with
> merge replication). In my case the partition is security-related, so it's
> important to ensure that different subscribers will get only their own
> data. Since I can't use SUSER_NAME(), and since HOST_NAME() can be
> overriden, what are the options to authenticate the user properly?
> Thanks,
> Vladimir K.
>
|||In SQL Mobile suser_name doesn't work for me... And the problem with
host_name is exactly as you stated: anyone can define anything, so it seems
I don't have an option to define partitions based on some security setting:
let's say I have two partitions A and B, and have two users a and b
appropriately. How do I prevent from user a to synchronize with partition B?
(and from user b with A?)
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uMU67pSSHHA.2212@.TK2MSFTNGP02.phx.gbl...
> You can use suser_name, it maps to publisherlogin, I also don't quite
> understand what you mean by host_name can be overridden - it can be
> overridden by the hostname parameter in your merge replication class
> (SQLCeReplication) to define whatever you want, which could be the account
> name you wish to filter by.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Vladimir Kofman" <vladimir.kofman@.gmail.com> wrote in message
> news:u9lqmIRSHHA.4832@.TK2MSFTNGP04.phx.gbl...
>
|||how about using certificates mapped to nt accounts. This way they will have
to know the password of the account you are going to pull with. The
communication will be encrypted and you can filter on suser_name which maps
to the publisherlogin.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Vladimir Kofman" <vladimir.kofman@.gmail.com> wrote in message
news:endEvgVSHHA.1228@.TK2MSFTNGP06.phx.gbl...
> In SQL Mobile suser_name doesn't work for me... And the problem with
> host_name is exactly as you stated: anyone can define anything, so it
> seems I don't have an option to define partitions based on some security
> setting: let's say I have two partitions A and B, and have two users a and
> b appropriately. How do I prevent from user a to synchronize with
> partition B? (and from user b with A?)
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uMU67pSSHHA.2212@.TK2MSFTNGP02.phx.gbl...
>
|||Thanks for your replies
But can you elaborate a bit more on the option you've suggested?
Thanks again.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eLdVCrVSHHA.2212@.TK2MSFTNGP02.phx.gbl...
> how about using certificates mapped to nt accounts. This way they will
> have to know the password of the account you are going to pull with. The
> communication will be encrypted and you can filter on suser_name which
> maps to the publisherlogin.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Vladimir Kofman" <vladimir.kofman@.gmail.com> wrote in message
> news:endEvgVSHHA.1228@.TK2MSFTNGP06.phx.gbl...
>
|||You have to configure the web serve to accept client certificates. This was
supported in SQL CE 2.0, it appears to be supported in Web Synchronization
as well, but it is not clear from the documentation that it is.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Vladimir Kofman" <vladimir.kofman@.gmail.com> wrote in message
news:OL9wDOWSHHA.3948@.TK2MSFTNGP05.phx.gbl...
> Thanks for your replies
> But can you elaborate a bit more on the option you've suggested?
> Thanks again.
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eLdVCrVSHHA.2212@.TK2MSFTNGP02.phx.gbl...
>
sql

Authentication with AD and cookies

Hi all!
We are going to set up Reporting Services 2005. We have two groups of
customers that are going to access our reports; internal and external
customers.
The internal customers should be authenticated through Active Directory,
while the external customers should be authenticated using cookies. The
external customers will first logon to another web-application which has its
own user database. From this application they will have a link to Reporting
Services.
How will I have to set up my reporting services server(s) to achieve this?
The internal and external uses are not going to share reports. However, the
extenal users should access linked reports (ie. same report but different
parameter values).
Thanks in advance for your help.RS doesn't support a mixed security mode, so it has to be either Windows or
custom security. It looks like in your scenario, Windows security could be a
better fit. Assuming that you don't need the external customer identity in
your reports, once the web app authenticates the external customers, it can
connect to RS using a single trusted account, e.g. the identity of the IIS
application pool in Windows Server 2003.
--
HTH,
---
Teo Lachev, MVP, MCSD, MCT
"Microsoft Reporting Services in Action"
"Applied Microsoft Analysis Services 2005"
Home page and blog: http://www.prologika.com/
---
"Billy" <Billy@.discussions.microsoft.com> wrote in message
news:8CBE5F6F-B2A5-44DA-A8DA-E4887C60BF67@.microsoft.com...
> Hi all!
> We are going to set up Reporting Services 2005. We have two groups of
> customers that are going to access our reports; internal and external
> customers.
> The internal customers should be authenticated through Active Directory,
> while the external customers should be authenticated using cookies. The
> external customers will first logon to another web-application which has
> its
> own user database. From this application they will have a link to
> Reporting
> Services.
> How will I have to set up my reporting services server(s) to achieve this?
> The internal and external uses are not going to share reports. However,
> the
> extenal users should access linked reports (ie. same report but different
> parameter values).
> Thanks in advance for your help.
>|||ok.
Is it possible to set up two separate instances of RS om the same server and
then route external users to instance A and internal users to instance B?
"Teo Lachev [MVP]" wrote:
> RS doesn't support a mixed security mode, so it has to be either Windows or
> custom security. It looks like in your scenario, Windows security could be a
> better fit. Assuming that you don't need the external customer identity in
> your reports, once the web app authenticates the external customers, it can
> connect to RS using a single trusted account, e.g. the identity of the IIS
> application pool in Windows Server 2003.
> --
> HTH,
> ---
> Teo Lachev, MVP, MCSD, MCT
> "Microsoft Reporting Services in Action"
> "Applied Microsoft Analysis Services 2005"
> Home page and blog: http://www.prologika.com/
> ---
> "Billy" <Billy@.discussions.microsoft.com> wrote in message
> news:8CBE5F6F-B2A5-44DA-A8DA-E4887C60BF67@.microsoft.com...
> > Hi all!
> >
> > We are going to set up Reporting Services 2005. We have two groups of
> > customers that are going to access our reports; internal and external
> > customers.
> >
> > The internal customers should be authenticated through Active Directory,
> > while the external customers should be authenticated using cookies. The
> > external customers will first logon to another web-application which has
> > its
> > own user database. From this application they will have a link to
> > Reporting
> > Services.
> >
> > How will I have to set up my reporting services server(s) to achieve this?
> > The internal and external uses are not going to share reports. However,
> > the
> > extenal users should access linked reports (ie. same report but different
> > parameter values).
> >
> > Thanks in advance for your help.
> >
>
>|||I don't think this scenario is officially supported but it looks like when
there is a will, there is a way
(http://www.sqljunkies.com/HowTo/525B575A-7F61-483A-AC8F-FEC700C34674.scuk).
--
HTH,
---
Teo Lachev, MVP, MCSD, MCT
"Microsoft Reporting Services in Action"
"Applied Microsoft Analysis Services 2005"
Home page and blog: http://www.prologika.com/
---
"Billy" <Billy@.discussions.microsoft.com> wrote in message
news:E6DD5D19-8C25-4C1E-8154-5C736723D80C@.microsoft.com...
> ok.
> Is it possible to set up two separate instances of RS om the same server
> and
> then route external users to instance A and internal users to instance B?
> "Teo Lachev [MVP]" wrote:
>> RS doesn't support a mixed security mode, so it has to be either Windows
>> or
>> custom security. It looks like in your scenario, Windows security could
>> be a
>> better fit. Assuming that you don't need the external customer identity
>> in
>> your reports, once the web app authenticates the external customers, it
>> can
>> connect to RS using a single trusted account, e.g. the identity of the
>> IIS
>> application pool in Windows Server 2003.
>> --
>> HTH,
>> ---
>> Teo Lachev, MVP, MCSD, MCT
>> "Microsoft Reporting Services in Action"
>> "Applied Microsoft Analysis Services 2005"
>> Home page and blog: http://www.prologika.com/
>> ---
>> "Billy" <Billy@.discussions.microsoft.com> wrote in message
>> news:8CBE5F6F-B2A5-44DA-A8DA-E4887C60BF67@.microsoft.com...
>> > Hi all!
>> >
>> > We are going to set up Reporting Services 2005. We have two groups of
>> > customers that are going to access our reports; internal and external
>> > customers.
>> >
>> > The internal customers should be authenticated through Active
>> > Directory,
>> > while the external customers should be authenticated using cookies. The
>> > external customers will first logon to another web-application which
>> > has
>> > its
>> > own user database. From this application they will have a link to
>> > Reporting
>> > Services.
>> >
>> > How will I have to set up my reporting services server(s) to achieve
>> > this?
>> > The internal and external uses are not going to share reports. However,
>> > the
>> > extenal users should access linked reports (ie. same report but
>> > different
>> > parameter values).
>> >
>> > Thanks in advance for your help.
>> >
>>

Authentication to SQL Server in ASP on Active Directory

I would like to be able to autheticate users connecting to SQL Server in
Active Server Pages on MS Active Directory.
Is this possible? If so, how?
Thank you.
AAAHi,
then you have to Map AD user account / group to sql server then you are
able to do it . please refer sp_adduser for more information it can be done
very well using this sp it is used to map those Windows (AD) accounts to SQL
and then use it in you ASP connection string. What is your Authentication
mode ?!
--
Andy Davis
Active Crypt Team
---SQL Server Encryption
Decryption Software
http://www.activecrypt.com
"AuntieAuntieAuntie" wrote:

> I would like to be able to autheticate users connecting to SQL Server in
> Active Server Pages on MS Active Directory.
> Is this possible? If so, how?
> Thank you.
> AAA|||Hi Andy,
This is the situation, (we can add users) but, not Domain Accounts that
belong to Domain Groups without a password on the connection string, within
an ASP on Active Directory, this is my current connection string:
<%
Dim strDatabaseType, objConn, cst
cst = "Provider=SQLOLEDB;data source=Z0123456;" &_
"Database=myDatabase;User ID=99;password=XXXXXXX;"
Set objConn = Server.CreateObject("ADODB.Connection")
%>
We would like to use a Domain Account as the userID without the password on
this connection string. On the database side, this account belongs to a
Domain Group, that has access to the database, it this possible? How can we
accomplish it?
AAA
"Andy Davis" wrote:
[vbcol=seagreen]
> Hi,
> then you have to Map AD user account / group to sql server then you are
> able to do it . please refer sp_adduser for more information it can be don
e
> very well using this sp it is used to map those Windows (AD) accounts to S
QL
> and then use it in you ASP connection string. What is your Authentication
> mode ?!
> --
> Andy Davis
> Active Crypt Team
> ---SQL Server Encryption
> Decryption Software
> http://www.activecrypt.com
>
> "AuntieAuntieAuntie" wrote:
>|||Hi,
We are using Windows Authentication for this applicaton.
AAA
"Andy Davis" wrote:
[vbcol=seagreen]
> Hi,
> then you have to Map AD user account / group to sql server then you are
> able to do it . please refer sp_adduser for more information it can be don
e
> very well using this sp it is used to map those Windows (AD) accounts to S
QL
> and then use it in you ASP connection string. What is your Authentication
> mode ?!
> --
> Andy Davis
> Active Crypt Team
> ---SQL Server Encryption
> Decryption Software
> http://www.activecrypt.com
>
> "AuntieAuntieAuntie" wrote:
>

authentication to SQL Server 2000 from ASP

please let me know if I need to post this on another SQL forum, and I'll be glad to do so.

I'm trying to set up the equivalent of Integrated Security=SSPI for SQL Server 2000 on IIS5.0. It's my understanding the SSPI string above is for Win NT, but not for Active Dir 2000 domains.

I'm using ASP 2.0 (NOT .Net), so please apprise me to what info I'd need in the connection string.

Currently it reads like this:

Set cn = CreateObject("ADODB.Connection")
cn.CursorLocation = 3 'Client side cursor
cn.Open "Provider=SQLOLEDB;Data Source=191.181.92.73;Integrated Security=SSPI"

Any feedback is welcomed.

Thanks!

Are the WebServer and the SQL Server on the same machine ? Did you enable Windows Authentication for the Website ?

Jens K. Suessmeyer

http://www.sqlserver2005.de
|||Any updates on that, or is the problem solved ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Authentication to Novell

I am wondering whether SQL Server 97 or SQL Server 2000 can be made to
authenticate to Novell. If so what is involved? We wish to consolidate our
user names, passwords, and access. ThanksOur SQL boxes have corresponding IDs on Novell to access
resources and have a Novell client or gateway installed.
You still have to have a Windows login though.
>--Original Message--
>I am wondering whether SQL Server 97 or SQL Server 2000
can be made to
>authenticate to Novell. If so what is involved? We wish
to consolidate our
>user names, passwords, and access. Thanks
>.
>|||I am considering a DLL which intercepts all database connection attempts,
does authentication on token files using workstation resources, and if
successful fetches a blanket username and password from a password server,
substitutes into the connection string, then backs out of the way and allows
native ODBC drivers to work.
>Subject: Authentication to Novell
>Date: Wed, 20 Aug 2003 07:06:08 -0700
>Our SQL boxes have corresponding IDs on Novell to access
>resources and have a Novell client or gateway installed.
>You still have to have a Windows login though.
>>--Original Message--
>>I am wondering whether SQL Server 97 or SQL Server 2000
>can be made to
>>authenticate to Novell. If so what is involved? We wish
>to consolidate our
>>user names, passwords, and access. Thanks
>>.sql

Authentication Reporting Services and web reportviewer

Hi,

I’ve an application Web which uses to reportviewer to show information. I want that all the users of the application accede to reports by means of he himself user and password. This user is a local user of report’s server. The problem is that when attempt to show report always appear the following error:

The request failed with HTTP status 401: Unauthorized.

The code that use is the following one:

ReportViewer1.ServerReport.ReportServerCredentials = new ReportViewerCredentials("Usuario", "pwd", "servidor");

using System;

using System.Data;

using System.Configuration;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Web.UI.HtmlControls;

using Microsoft.Reporting.WebForms;

using System.Net;

using System.Security.Principal;

using System.Runtime.InteropServices;

/// <summary>

/// Summary description for ReportViewerCredentials

/// </summary>

public class ReportViewerCredentials : IReportServerCredentials

{

[DllImport("advapi32.dll", SetLastError = true)]

public extern static bool LogonUser(String lpszUsername, String lpszDomain, String lpszPassword, int dwLogonType, int dwLogonProvider, ref IntPtr phToken);

[DllImport("kernel32.dll", CharSet = CharSet.Auto)]

public extern static bool CloseHandle(IntPtr handle);

[DllImport("advapi32.dll", CharSet = CharSet.Auto, SetLastError = true)]

public extern static bool DuplicateToken(IntPtr ExistingTokenHandle,

int SECURITY_IMPERSONATION_LEVEL, ref IntPtr DuplicateTokenHandle);

public ReportViewerCredentials()

{

}

public ReportViewerCredentials(string username)

{

this.Username = username;

}

public ReportViewerCredentials(string username, string password)

{

this.Username = username;

this.Password = password;

}

public ReportViewerCredentials(string username, string password, string domain)

{

this.Username = username;

this.Password = password;

this.Domain = domain;

}

public string Username

{

get

{

return this.username;

}

set

{

string username = value;

if (username.Contains("\\"))

{

this.domain = username.Substring(0, username.IndexOf("\\"));

this.username = username.Substring(username.IndexOf("\\") + 1);

}

else

{

this.username = username;

}

}

}

private string username;

public string Password

{

get

{

return this.password;

}

set

{

this.password = value;

}

}

private string password;

public string Domain

{

get

{

return this.domain;

}

set

{

this.domain = value;

}

}

private string domain;

#region IReportServerCredentials Members

public bool GetBasicCredentials(out string basicUser, out string basicPassword, out string basicDomain)

{

basicUser = username;

basicPassword = password;

basicDomain = domain;

return username != null && password != null && domain != null;

}

public bool GetFormsCredentials(out string formsUser, out string formsPassword, out string formsAuthority)

{

formsUser = username;

formsPassword = password;

formsAuthority = domain;

return username != null && password != null && domain != null;

}

public bool GetFormsCredentials(out Cookie authCookie,out string user, out string password, out string authority)

{

authCookie = null;

user = password = authority = null;

return false;// Not implemented

}

public WindowsIdentity ImpersonationUser

{

get

{

string[] args = new string[3] { this.Domain.ToString(), this.Username.ToString(), this.Password.ToString() };

IntPtr tokenHandle = new IntPtr(0);

IntPtr dupeTokenHandle = new IntPtr(0);

//const int LOGON32_PROVIDER_DEFAULT = 0;

////This parameter causes LogonUser to create a primary token.

//const int LOGON32_LOGON_INTERACTIVE = 2;

const int LOGON32_PROVIDER_DEFAULT = 3;

//This parameter causes LogonUser to create a primary token.

const int LOGON32_LOGON_INTERACTIVE = 9;

const int SecurityImpersonation = 2;

tokenHandle = IntPtr.Zero;

dupeTokenHandle = IntPtr.Zero;

try

{

// Call LogonUser to obtain an handle to an access token.

bool returnValue = LogonUser(args[1], args[0], args[2],

LOGON32_LOGON_INTERACTIVE, LOGON32_PROVIDER_DEFAULT,

ref tokenHandle);

if (false == returnValue)

{

Console.WriteLine("LogonUser failed with error code : {0}",Marshal.GetLastWin32Error());

return null;

}

// Check the identity.

System.Diagnostics.Trace.WriteLine("Before impersonation: "

+ WindowsIdentity.GetCurrent().Name);

bool retVal = DuplicateToken(tokenHandle, SecurityImpersonation, ref dupeTokenHandle);

if (false == retVal)

{

CloseHandle(tokenHandle);

Console.WriteLine("Exception in token duplication.");

return null;

}

// The token that is passed to the following constructor must

// be a primary token to impersonate.

WindowsIdentity newId = new WindowsIdentity(dupeTokenHandle);

WindowsImpersonationContext impersonatedUser = newId.Impersonate();

// Free the tokens.

if (tokenHandle != IntPtr.Zero)

CloseHandle(tokenHandle);

if (dupeTokenHandle != IntPtr.Zero)

CloseHandle(dupeTokenHandle);

// Check the identity.

System.Diagnostics.Trace.WriteLine("After impersonation: "

+ WindowsIdentity.GetCurrent().Name);

return newId;

}

catch (Exception ex)

{

Console.WriteLine("Exception occurred. " + ex.Message);

}

return null;

}

}

public ICredentials NetworkCredentials

{

get

{

return null;// Not using NetworkCredentials to authenticate.

}

}

#endregion

}

Go to the following links, this will solve your problem

http://blogs.msdn.com/bimusings/archive/2005/12/05/500195.aspx

http://www.odetocode.com/Articles/216.aspx

Authentication Quirk

For some reason that I cannot figure out, some users are prompted for a
username and password when they request data in some reports. They can access
the reports OK, and choose the parameters OK, but then when they try to view
the report, they are prompted for credentials. If they click Cancel, the
report runs fine and the data is retrieved.
Any initial ideas?Do you have the datasource the report is using set to:
Connect Using:
The credentials supplied by the user running the report?
Adrian M.
"Mark Parter" <MarkParter@.discussions.microsoft.com> wrote in message
news:5D8230E0-EA56-4673-A88F-91E7C54F9DE8@.microsoft.com...
> For some reason that I cannot figure out, some users are prompted for a
> username and password when they request data in some reports. They can
> access
> the reports OK, and choose the parameters OK, but then when they try to
> view
> the report, they are prompted for credentials. If they click Cancel, the
> report runs fine and the data is retrieved.
> Any initial ideas?|||Thanks for replying.
To answer your question, no. The data source has the "Credentials stored
securely in the report server" option selected with the additional "Use as
Windows credentials when connecting to the data source" also selected.
Thanks.
"Adrian M." wrote:
> Do you have the datasource the report is using set to:
> Connect Using:
> The credentials supplied by the user running the report?
> Adrian M.
> "Mark Parter" <MarkParter@.discussions.microsoft.com> wrote in message
> news:5D8230E0-EA56-4673-A88F-91E7C54F9DE8@.microsoft.com...
> > For some reason that I cannot figure out, some users are prompted for a
> > username and password when they request data in some reports. They can
> > access
> > the reports OK, and choose the parameters OK, but then when they try to
> > view
> > the report, they are prompted for credentials. If they click Cancel, the
> > report runs fine and the data is retrieved.
> >
> > Any initial ideas?
>
>|||hmm, odd...
Some ideas, try the article http://support.microsoft.com/kb/842517
hth
Adrian M.
"Mark Parter" <MarkParter@.discussions.microsoft.com> wrote in message
news:FBAE3BCE-F1D9-4B02-AAAF-44199ADF3744@.microsoft.com...
> Thanks for replying.
> To answer your question, no. The data source has the "Credentials stored
> securely in the report server" option selected with the additional "Use as
> Windows credentials when connecting to the data source" also selected.
> Thanks.
> "Adrian M." wrote:
>> Do you have the datasource the report is using set to:
>> Connect Using:
>> The credentials supplied by the user running the report?
>> Adrian M.
>> "Mark Parter" <MarkParter@.discussions.microsoft.com> wrote in message
>> news:5D8230E0-EA56-4673-A88F-91E7C54F9DE8@.microsoft.com...
>> > For some reason that I cannot figure out, some users are prompted for a
>> > username and password when they request data in some reports. They can
>> > access
>> > the reports OK, and choose the parameters OK, but then when they try to
>> > view
>> > the report, they are prompted for credentials. If they click Cancel,
>> > the
>> > report runs fine and the data is retrieved.
>> >
>> > Any initial ideas?
>>|||Thanks for taking the time to help/post Adrian. For some unknown reason, the
problem has allegedly vanished. I say allegedly as a colleague informed me
yesterday that it was now working Ok for him but as I wasn't in the office
yesterday, I won't be able to confirm till Monday.
Fingers crossed.
"Adrian M." wrote:
> hmm, odd...
> Some ideas, try the article http://support.microsoft.com/kb/842517
> hth
> Adrian M.
> "Mark Parter" <MarkParter@.discussions.microsoft.com> wrote in message
> news:FBAE3BCE-F1D9-4B02-AAAF-44199ADF3744@.microsoft.com...
> > Thanks for replying.
> >
> > To answer your question, no. The data source has the "Credentials stored
> > securely in the report server" option selected with the additional "Use as
> > Windows credentials when connecting to the data source" also selected.
> >
> > Thanks.
> >
> > "Adrian M." wrote:
> >
> >> Do you have the datasource the report is using set to:
> >>
> >> Connect Using:
> >> The credentials supplied by the user running the report?
> >>
> >> Adrian M.
> >>
> >> "Mark Parter" <MarkParter@.discussions.microsoft.com> wrote in message
> >> news:5D8230E0-EA56-4673-A88F-91E7C54F9DE8@.microsoft.com...
> >> > For some reason that I cannot figure out, some users are prompted for a
> >> > username and password when they request data in some reports. They can
> >> > access
> >> > the reports OK, and choose the parameters OK, but then when they try to
> >> > view
> >> > the report, they are prompted for credentials. If they click Cancel,
> >> > the
> >> > report runs fine and the data is retrieved.
> >> >
> >> > Any initial ideas?
> >>
> >>
> >>
>
>

Authentication question

Greetings from an SQL Server newbie.

We are purchasing 3rd party software with a SQL Server back end. A tech person installing SQL Server on the server insisted we use mixed mode authentication. (We are running Windows 2003 using Active Directory) We want Windows authentication (WA) but he claims it is "more complicated" to use.

His example: A shop using WA found that users running a certain process that creates and deletes temp tables did not have permission to delete tables and the process failed. The vendor had to go in and manually delete the tables.

The application uses .INI files with passwords and user names in plain text to connect to SQL Server. Our security specialist's eyes bugged out. :eek: We all think this is not good.

Is the vendor blowing us smoke? Should we insist on WA?

Thanks for your help.Depending on the package, what you want your users to do, network topography, and other issues they might have a point.

Just a few weeks ago some of the folks at a major manufacturer in Moline were having a fit about a package that had been developed internally (by a plant manager) that used SQL authentication. The central admin folks were having a fit, until they discovered that the reason the app was written that way was due to limitations in their internal network that made AD impractical. Sometimes even when you have the source code, other conditions prevent you from being able to make the changes that you'd like!

Even Microsoft came to the conclusion that SQL Authentication was the best option for those conditions, as much as it irked them to have to say that!

-PatP|||The vendor's example smacks of bogosity. Windows authenticated users, and SQL authenticated users can both be granted and denied the same set of permissions. Once a login is authenticated, there is no difference between them. The major reasons we would go with SQL authentication is for webservers. Generally, webservers run several applications (web sites), and each may need their own set of permissions on a set of databases (usually one DB per application). Windows authentication allows for only one login for the server, while SQL authentication allows each application to have its unique login.|||Exactly the problem that they were having. Pseudo-public machines force all users to share a common NT login. If you want users to have different levels of permission, you have to use SQL authentication.

The same problem applies on a more general scale to a WAN that doesn't support NetBIOS completely. Since the workstations can't authenticate over the WAN, the credentials have to be forged... Because they can't authenticate, they all get the same credentials. Same problem as before, but LOTS harder to fix!

-PatP|||So I guess sometimes it makes sense to use SQL Authentication instead of Windows Authentication. But it makes no sense to store username/passwords in an .ini file as plaintext. Perhaps it says someting about the effort put in by the vendor.|||So I guess sometimes it makes sense to use SQL Authentication instead of Windows Authentication. But it makes no sense to store username/passwords in an .ini file as plaintext. Perhaps it says someting about the effort put in by the vendor.I see that as pure idiocy, not really a database issue at all. I'm flat out allergic to storing passwords in plain text anywhere, and generally uncomfortable with storing them on PCs at all (with the exception of tools like SplashId or Password Safe that are designed for just that purpose).

-PatP|||hmmz.. pwsafe comes in handy and secure indeed. btw: it comes with an export-function to plaintext ;)|||hmmz.. pwsafe comes in handy and secure indeed. btw: it comes with an export-function to plaintext ;)I suppose that all tools have to have some flaw! ;)

-PatP

Authentication question

I have a question about authentication with SQL 2005. I want to create a
group in our Active Directory (Win 2003) and make it a user in MS SQL 2005.
Would users of the AD group then be able to authenticate to the SQL Server
because the group is in SQL Server or not?You need to connect to your instance and create a login principal from the
Security for the mentioned Windows Group and map it to whatever resource
they need to reach.
To achieve this, your SQL Server server also has to be joined to the
mentioned domain.
--
Ekrem Önsoy
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:uTlojAEAIHA.536@.TK2MSFTNGP06.phx.gbl...
>I have a question about authentication with SQL 2005. I want to create a
>group in our Active Directory (Win 2003) and make it a user in MS SQL 2005.
>Would users of the AD group then be able to authenticate to the SQL Server
>because the group is in SQL Server or not?
>

Authentication Question

Hello,
I want to setup authentication so that if any requests come from a
certain ip address they are automattically accepted. Is there an easy
way to do this or is using some kind of custom extension using forms
the only way?
Thanks,
DavidAccepted or rejected? Rejected can easily be done by configuring IIS to
reject a particular IP address. If you want it to accept then I don't see
any way to do this other than with a custom extension.
Bruce L-C
"David" <davidbjunk@.gmail.com> wrote in message
news:67845027.0409231000.7feb8eb5@.posting.google.com...
> Hello,
> I want to setup authentication so that if any requests come from a
> certain ip address they are automattically accepted. Is there an easy
> way to do this or is using some kind of custom extension using forms
> the only way?
> Thanks,
> Davidsql

Authentication query

I have a service broker application which is used to exchange messages between two endpoints.

I am currently using certificates for dialog and transport security.

The transport security certificate has been created in master database.

My understanding is that since service broker endpoint is a instance level object so I have to create the certificate in the master database.

But our production dba has suggested that we do not disturb the master database and create this certificate in some user database.

I don't see how that can be possible. Still I tried that, but endpoint creation script failed as it could not find the certificate.

Here I have two questions-

1. Is it possible to set up transport level security by creation of certificate in some user database and referring the sql server endpoint to this certificate.

2. I read somewhere in this forum that certificate authentication is preferable to Windows authentication for creation of endpoints. Is that correct? Is there any article which substantiates this?

Any help will be appreciated.

Warm regards.

Sudhir.

thanks Remus,

That was really helpful and quiet prompt.

Very glad that I posted my query here.

Thanks a bunch.

Have a nice day

Sudhir

|||

1) No. Endpoint certificates must be deployed in master.

2) Certificates authentication does not depend on the availability of the Active Directory and can cross domains and forests.

HTH,
~ Remus

Authentication Problems

We have an application which uses a SQL Server 7 database installed locally
on laptops. This then replicates with a central server. The laptops, server
etc are all on the same domain and the database uses Windows Authentication
only.
Everything works fine when running W2K.
However following the installation of SQL Server 7 and the app on laptops
running XP SP2 we are experiencing problems. The app runs fine when the user
is VPNed into the network but when they are working remotely with only their
local databases problems occur.
Usually the app authenticates seamlessly with the local database but under
XP SP2 a dialog entitled 'SQL Server Login' is displayed and access to the
database is not allowed.
There are also issues in relation to the running of the SQL Server Agent.
When working remotely users cannot start the service properly, they receive
the following message :
'The sqlserveragent service on local computer started and then stopped.
Some services stop automatically if they have nothing to do , for example,
the performance logs and alerts service'.
My suspicion is that it is an XP SP2 issue.
There may be issues related to the installation of IIS as well but I'm not
sure.
Any help to solve this problem would be gratefully appreciated.
Thanks,
DD.
Yeah, XPSP2 is your culprit there.
Make sure you've followed these articles:
How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
Contains links to articles that you can use to help you configure Windows
Firewall to permit access for SQL Server, Analysis Services, and MSDE.
http://support.microsoft.com/default...b;en-us;841249
Microsoft SQL Server: FAQ: How Windows XP Service Pack 2 (SP2) Affects SQL
Server and MSDE
Get answers to frequently asked questions about how Windows XP Service Pack
2 (SP2) affects installations of SQL Server 2000 and MSDE.
http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
Donna Lambert
"Dave52" wrote:

> We have an application which uses a SQL Server 7 database installed locally
> on laptops. This then replicates with a central server. The laptops, server
> etc are all on the same domain and the database uses Windows Authentication
> only.
> Everything works fine when running W2K.
> However following the installation of SQL Server 7 and the app on laptops
> running XP SP2 we are experiencing problems. The app runs fine when the user
> is VPNed into the network but when they are working remotely with only their
> local databases problems occur.
> Usually the app authenticates seamlessly with the local database but under
> XP SP2 a dialog entitled 'SQL Server Login' is displayed and access to the
> database is not allowed.
> There are also issues in relation to the running of the SQL Server Agent.
> When working remotely users cannot start the service properly, they receive
> the following message :
> 'The sqlserveragent service on local computer started and then stopped.
> Some services stop automatically if they have nothing to do , for example,
> the performance logs and alerts service'.
> My suspicion is that it is an XP SP2 issue.
> There may be issues related to the installation of IIS as well but I'm not
> sure.
> Any help to solve this problem would be gratefully appreciated.
> Thanks,
> DD.