Unfortunately since 2003-SP1 it occasionally does it... and for me, we are
"Bruce L-C [MVP]" wrote:
> Here is something I wrote awhile back: I had a case where the issue was that
> the server (it was a test server) was using DHCP (dynamic tcpip address
> instead of fixed). When I went to a fixed IP address the probelm went away.
> Obscure but thought I would mention it.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "David Bienstock" <davidleebspam-sqlrs@yahoo.com> wrote in message
> news:6007DFF2-9784-4BAA-BE34-939AB0E65AA0@microsoft.com...
> >I found
http://support.microsoft.com/kb/896861/ but it didn't work for me
> >on
> > the server side... I haven't tried it on the XP-SP2 side.
> >
> > Did you get yours fixed?
> > --
> > "Everyone knows something you don't know"
> >
> >
> > "Praveen Chand" wrote:
> >
> >> Hello,
> >> We have the following configuration:
> >> 1. Windows 2003
> >> 2. SQL Server 2000 Standard Edition
> >> 3. We don't have the domain setup.
> >> 4. We are using the Data sources option "Credentails Stored securely in
> >> the
> >> report server".
> >>
> >> Currently RS reports are working fine in Windows 2000 environment with
> >> user
> >> authentication prompt. When we deployed the reports in Windows 2003 the
> >> reports prompts for the user authentication.
> >>
> >> We don't want the user authentication prompt.
> >>
> >> Can anyone please share the knowledge how we could avoid the user
> >> authentication prompt and why we are facing this problem in Windows 2003
> >> environment only?
> >>
> >> Let us know if you need more information.
> >>
> >> PC
>
>