Connection : trusted

Hi all, in one of my newly configured SQL server logs, I found a error
message like this:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server
connection.
Also in both of my new servers , SQL server logs following message repeated
all the time with differefnt date.
Login succeeded for user 'domain\user1'. Connection: Trusted.
And I couldn't find any similar log messages from the current production
server.
Any ideas? did I do something wrong when I set up new servers?
Thanks a lot.
Your server is not configures for mixed authentication, that why he is
accepting domain users but not the SQL Users:
http://msdn.microsoft.com/library/de...urity_47u6.asp
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
> Hi all, in one of my newly configured SQL server logs, I found a error
> message like this:
> Login failed for user 'sa'. Reason: Not associated with a trusted SQL
> Server
> connection.
> Also in both of my new servers , SQL server logs following message
> repeated
> all the time with differefnt date.
> Login succeeded for user 'domain\user1'. Connection: Trusted.
> And I couldn't find any similar log messages from the current production
> server.
> Any ideas? did I do something wrong when I set up new servers?
> Thanks a lot.
|||thanks. But my production server is using the same authentication, why I did
not see the same logs messages?
"Jens Sü?meyer" wrote:

> Your server is not configures for mixed authentication, that why he is
> accepting domain users but not the SQL Users:
> http://msdn.microsoft.com/library/de...urity_47u6.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
>
>
|||Then you have not set the same security options for the new server.
Apparently one of the servers is set to audit all login attempts, the other
is set to audit successful logins.
|||You are right, I set different audit trace for the two servers, but I how can
I find if I set to log successful logins ?
Thanks a lot!
"Scott Morris" wrote:

> Then you have not set the same security options for the new server.
> Apparently one of the servers is set to audit all login attempts, the other
> is set to audit successful logins.
>
>
|||Documentation? BOL -> Search -> "login failure"
|||Thnaks, I found it.
"Scott Morris" wrote:

> Documentation? BOL -> Search -> "login failure"
>
>

Connection : trusted

Hi all, in one of my newly configured SQL server logs, I found a error
message like this:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server
connection.
Also in both of my new servers , SQL server logs following message repeated
all the time with differefnt date.
Login succeeded for user 'domain\user1'. Connection: Trusted.
And I couldn't find any similar log messages from the current production
server.
Any ideas? did I do something wrong when I set up new servers?
Thanks a lot.Your server is not configures for mixed authentication, that why he is
accepting domain users but not the SQL Users:
http://msdn.microsoft.com/library/d...>
ity_47u6.asp
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
> Hi all, in one of my newly configured SQL server logs, I found a error
> message like this:
> Login failed for user 'sa'. Reason: Not associated with a trusted SQL
> Server
> connection.
> Also in both of my new servers , SQL server logs following message
> repeated
> all the time with differefnt date.
> Login succeeded for user 'domain\user1'. Connection: Trusted.
> And I couldn't find any similar log messages from the current production
> server.
> Any ideas? did I do something wrong when I set up new servers?
> Thanks a lot.|||thanks. But my production server is using the same authentication, why I did
not see the same logs messages?
"Jens Sü?meyer" wrote:

> Your server is not configures for mixed authentication, that why he is
> accepting domain users but not the SQL Users:
> http://msdn.microsoft.com/library/d...
urity_47u6.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
>
>|||Then you have not set the same security options for the new server.
Apparently one of the servers is set to audit all login attempts, the other
is set to audit successful logins.|||You are right, I set different audit trace for the two servers, but I how ca
n
I find if I set to log successful logins '
Thanks a lot!
"Scott Morris" wrote:

> Then you have not set the same security options for the new server.
> Apparently one of the servers is set to audit all login attempts, the othe
r
> is set to audit successful logins.
>
>|||Documentation? BOL -> Search -> "login failure"|||Thnaks, I found it.
"Scott Morris" wrote:

> Documentation? BOL -> Search -> "login failure"
>
>

Connection : trusted

Hi all, in one of my newly configured SQL server logs, I found a error
message like this:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server
connection.
Also in both of my new servers , SQL server logs following message repeated
all the time with differefnt date.
Login succeeded for user 'domain\user1'. Connection: Trusted.
And I couldn't find any similar log messages from the current production
server.
Any ideas? did I do something wrong when I set up new servers?
Thanks a lot.Your server is not configures for mixed authentication, that why he is
accepting domain users but not the SQL Users:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_47u6.asp
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
> Hi all, in one of my newly configured SQL server logs, I found a error
> message like this:
> Login failed for user 'sa'. Reason: Not associated with a trusted SQL
> Server
> connection.
> Also in both of my new servers , SQL server logs following message
> repeated
> all the time with differefnt date.
> Login succeeded for user 'domain\user1'. Connection: Trusted.
> And I couldn't find any similar log messages from the current production
> server.
> Any ideas? did I do something wrong when I set up new servers?
> Thanks a lot.|||thanks. But my production server is using the same authentication, why I did
not see the same logs messages?
"Jens Sü�meyer" wrote:
> Your server is not configures for mixed authentication, that why he is
> accepting domain users but not the SQL Users:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_47u6.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
> > Hi all, in one of my newly configured SQL server logs, I found a error
> > message like this:
> > Login failed for user 'sa'. Reason: Not associated with a trusted SQL
> > Server
> > connection.
> >
> > Also in both of my new servers , SQL server logs following message
> > repeated
> > all the time with differefnt date.
> >
> > Login succeeded for user 'domain\user1'. Connection: Trusted.
> >
> > And I couldn't find any similar log messages from the current production
> > server.
> > Any ideas? did I do something wrong when I set up new servers?
> >
> > Thanks a lot.
>
>|||Then you have not set the same security options for the new server.
Apparently one of the servers is set to audit all login attempts, the other
is set to audit successful logins.|||You are right, I set different audit trace for the two servers, but I how can
I find if I set to log successful logins '
Thanks a lot!
"Scott Morris" wrote:
> Then you have not set the same security options for the new server.
> Apparently one of the servers is set to audit all login attempts, the other
> is set to audit successful logins.
>
>|||Documentation? BOL -> Search -> "login failure"|||Thnaks, I found it.
"Scott Morris" wrote:
> Documentation? BOL -> Search -> "login failure"
>
>

Connecting VIA IP Address

When I try to connect via IP to a newly created Active Active cluster I
have to add the port to the IP for it to work. An example is if my IP
is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
then it works fine. Am I missing a setting somewhere to make this work
just by using the IP? Oh... and just to note this work the same accross
the network or if I am logged on local to the box.
thanks
Chris
I should have stated this but I am using SQL Server 2000 and the server
is Windows 2003
|||I should have stated this but I am using SQL Server 200 on a Windows
2003 cluster

COnnecting via IP address

When I try to connect via IP to a newly created Active Active cluster I
have to add the port to the IP for it to work. An example is if my IP
is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
then it works fine. Am I missing a setting somewhere to make this work
just by using the IP? Oh... and just to note this work the same accross
the network or if I am logged on local to the box.
thanks
Chris
I should have stated this but I am using SQL Server 200 on a Windows
2003 cluster
|||Your SQL Server instance must be a named instance listening on port 1433. If
it were a default instance, connecting to the IP without specifying a port
would have automatically led to the default port of 1433, and would have
succeeded.
With a named instance, however, you are not directed to 1433 by default.
Either the client has to be told by the server via UDP 1434 as to what port
to use, or it has to identify the port explicitly. And if the client is
using an explicit IP address, you are not using UDP 1434.
Linchi
<cfrank@.investorforce.com> wrote in message
news:1140797262.929065.72080@.i40g2000cwc.googlegro ups.com...
> When I try to connect via IP to a newly created Active Active cluster I
> have to add the port to the IP for it to work. An example is if my IP
> is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
> then it works fine. Am I missing a setting somewhere to make this work
> just by using the IP? Oh... and just to note this work the same accross
> the network or if I am logged on local to the box.
> thanks
> Chris
>

COnnecting via IP address

When I try to connect via IP to a newly created Active Active cluster I
have to add the port to the IP for it to work. An example is if my IP
is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
then it works fine. Am I missing a setting somewhere to make this work
just by using the IP? Oh... and just to note this work the same accross
the network or if I am logged on local to the box.
thanks
ChrisI should have stated this but I am using SQL Server 200 on a Windows
2003 cluster|||Your SQL Server instance must be a named instance listening on port 1433. If
it were a default instance, connecting to the IP without specifying a port
would have automatically led to the default port of 1433, and would have
succeeded.
With a named instance, however, you are not directed to 1433 by default.
Either the client has to be told by the server via UDP 1434 as to what port
to use, or it has to identify the port explicitly. And if the client is
using an explicit IP address, you are not using UDP 1434.
Linchi
<cfrank@.investorforce.com> wrote in message
news:1140797262.929065.72080@.i40g2000cwc.googlegroups.com...
> When I try to connect via IP to a newly created Active Active cluster I
> have to add the port to the IP for it to work. An example is if my IP
> is 10.0.0.1 and I try to connect it times out. if I try 10.0.0.1,1433
> then it works fine. Am I missing a setting somewhere to make this work
> just by using the IP? Oh... and just to note this work the same accross
> the network or if I am logged on local to the box.
> thanks
> Chris
>