Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / December 2006

Tip: Looking for answers? Try searching our database.

Client to IIS to SQL Server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
czuvich - 04 Dec 2006 15:56 GMT
I am completely stumped and hopefully someone will be able to give me
some guidance.

Here's our problem:
We are getting an 'NT AUTHORITY\ANONYMOUS LOGON' error randomly when
accessing our database from an asp.net web page. I know that's a vague
description, but it's as good as I can get. We clear the error by
logging off and on the client machine. Here's some of the details of
our setup.

IIS 5.0 Windows 2000 Server (stand alone machine)
SQL Server 2000 SP 4 on a W2K machine (stand alone machine - separate
from IIS)
Client is running XP SP 2.

For the most part everything works fine, but every once in awhile (once
or twice a week), the page throws this error. We have a page that shows
the username on IIS by doing a System.Environment.UserName and it shows
the authenticated user (not anonymous). Our web.config uses
impersonation=true. Now, I am still trying to understand the difference
between System.Environment.UserName and
HttpContext.Current.User.Identity.Name, but that's a different story.
Can anyone help me out? Any would be greatly appreciated.
Jacek Stawicki - 05 Dec 2006 09:01 GMT
>I am completely stumped and hopefully someone will be able to give me
> some guidance.
[quoted text clipped - 5 lines]
> logging off and on the client machine. Here's some of the details of
> our setup.

> the authenticated user (not anonymous). Our web.config uses
> impersonation=true. Now, I am still trying to understand the difference
> between System.Environment.UserName and

Once I had problem with this error. The reason was:
1. Workstation wasn't in domain
2. Windows has problem with SPN when and it throws this error.

Regards
Jacek

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.