Problems with authentication and using alias to the local machine

I'm having trouble with authentication when using aliases in the "hosts"
file (located at C:\WINDOWS\system32\drivers\etc) wich point to "127.0.0.1".

Sql Server:
=======

All of these sentences work:

osql -E -d pubs -Q "select * from authors" -S localhost
osql -E -d pubs -Q "select * from authors" -S 127.0.0.1
osql -E -d pubs -Q "select * from authors" -S [ReplaceWithTheIPAdress]
osql -E -d pubs -Q "select * from authors" -S [ReplaceWithTheDNSName]

but this doesn't work:

osql -E -d pubs -Q "select * from authors" -S [ReplaceWithMyAlias]

it returns "Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection."

I found a workaround which is to register the alias in the "SQL Server
Client Network Utility"



WebSite using NTLM Authentication:
==========================

Loading a page in IE

This two addresses just load the page
http://localhost/MySite/default.aspx
http://[ReplaceWithTheDNSName]/MySite/default.aspx

the next two show a window asking for credentials and after the credentials
are entered the page is loaded
http://127.0.0.1/MySite/default.aspx
http://[ReplaceWithTheIPAdress]/MySite/default.aspx

but the one using the alias shows a window asking for credentials BUT after
the credentials are entered the page is NOT loaded and "unahutorized" error
message is display
http://[ReplaceWithMyAlias]/MySite/default.aspx

the same problem shows up when calling a WebService from a net client
program.


What's going on ? Why aliases to the local machine doesn't work ? I've also
tried creating the alias to the IP address instead of the loopback IP
address with same results.


.

Relevant Pages

  • Re: Windows Authentication in asp.net 2005 to SQL Server?
    ... If the domains do not trust each other, Windows authentication is not going ... Basic authentication sometimes makes the need for Kerberos delegation go ... generic account to do the backend data stuff on our SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: I dont want to re-invent the Login/Login Wheel - Help with utilities
    ... Yes, if you use .NET1.1, there isn't built-in login control, and more importanltly there isn't ready-to-use membership component to use. ... the membership provider uses SQL Server or SQL Server Express. ... We feel that having the capability to force password change would be a better benefit in securing our application and data access. ... Both Windows authentication and authorization wolud be be fine if we wanted the world to have access to our application data, but not very intuitive for maintaining integrity over our data. ...
    (microsoft.public.vstudio.general)
  • RE: IIS (ASP) -> SQLServer Authentication Issue
    ... I understand that you'd like to use IIS Intergration authentication in the ... and ASP "impersonates" authencitaed users to access SQL Server on ... only kerberos authentication allows double-hops from clients ...
    (microsoft.public.sqlserver.security)
  • Re: SBS Premium Edition .. what way is SQL licenced
    ... Another thing to note in using your SQL Server as a backend database is the ... concept of Forms-based authentication and Integrated Windows authentication. ... thereby requiring individual CALs to access SQL Server. ... Chad A. Gross - SBS MVP ...
    (microsoft.public.windows.server.sbs)
  • Re: Integrated Authentication with SQL
    ... On the IIS level there is no trouble authenticating with kerberos. ... problem is in when I try to flow those credentials over to the SQL server. ... Successful Network Logon: ... Authentication Package: Kerberos ...
    (microsoft.public.dotnet.framework.aspnet.security)