sql server connect:
This is the expected behavior. Since both the machines have same
administrator password, when you try to connect from system2 to system1,
system2 uses NTLM Authentication protocol (which in turn uses the current
user's credentails) to authenticate against System1's SAM database. Since
the administrator password is same, the connection succeeds. In fact this is
not specific to SQL Server, if you go to command prompt and do a net use to
C$ on system1 you would successfully map a drive to that c$.
Logged on user on System1 doesnt have any role in this. In face each network
login gets his own logon session.
Thanks,
Bala Neerumalla.
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
[quoted text, click to view] "Srinivasa Rao B" <srinivasab@cybage.com> wrote in message
news:eRNMa489DHA.1636@TK2MSFTNGP12.phx.gbl...
> Hi,
> Pleae consider this scenario, where I have 2 systems on the same domain
and
> named as system1 and system2. Two systems have Administrator logins as
their
> local login, not part of domain and these two have same password say
123456
>
> System1 has database installed with that and NT authentication enabled. I
> have one more domain account on system1 with which i have logged in. On
> system2 I have logged in using local admin of system2. Now on system2, I
> configure one DSN, and that connects to system1 with NT authentication.
> Actually it should fail as this local admin does not have any previliges
> over system1.
>
> Surprisingly it got connected to the database on the system1. Same
behaviour
> with Enterprise manager also.
>
> Do not you think its a bug with SQL server?
>
> Regards
> BSR
>
>