March 9, 2009 at 12:57 pm
er.imran.it (3/9/2009)
Any resolution???? I am not good in DB.. Plz help....
If you are logged on to the same computer as SQL Server, then use SQLCMD with the following flags:
SQLCMD -A -E
This forces SQLCMD to connect to the DAC as your Windows account. From there you should be able to drop or disable the trigger as given in the article.
K. Brian Kelley
@kbriankelley
March 9, 2009 at 1:03 pm
K. Brian Kelley (3/9/2009)
RBarryYoung (3/9/2009)
Great article, Brian. Is the Client_Host ip information still available about a session later on, or would I need to store it from a Logon Trigger like yours if I needed that?It's also available in sys.dm_exec_connections in the column client_net_address.
Hah! That's great, Brian. I've seen this question (how can to get a session's IP address) asked many times without hearing an answer. Thanks.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 9, 2009 at 1:06 pm
er.imran.it (3/9/2009)
Any resolution???? I am not good in DB.. Plz help....
Probably shouldn't have run the code then.
March 9, 2009 at 4:05 pm
This is good stuff. I'm learning. It's got me thinking how an attacker could ompromise our web servers and launch an attack against the SQL Server.
March 20, 2009 at 5:24 am
Thanks for the post Brian.
However, I am stuck with few issues. Hope you could throw some light on them and clarify .
1. I executed the Step to insert <local machine< into ValidIP table and still i am not able to connect from my local machine, bcoz of trigger execution.
2. I changed the trigger to capture the @IP value in troubleshooting the above said issue. Below is my code:
CREATE TRIGGER tr_logon_CheckIP
ON ALL SERVER
FOR LOGON
AS
DECLARE @IP NVARCHAR(15),@SqlCmd NVARCHAR(100);
SET @IP = (SELECT EVENTDATA().value('(/EVENT_INSTANCE/ClientHost)[1]', 'NVARCHAR(15)'));
INSERT INTO dbo.ValidIP (IP) VALUES (@IP);
BEGIN
IF IS_SRVROLEMEMBER('sysadmin') = 1
BEGIN
IF NOT EXISTS(SELECT IP FROM DBAWork.dbo.ValidIP WHERE IP = @IP)
ROLLBACK;
END;
END;
GO
But this is not inserting any @IP value in the ValidIP table. Does triggers have constraint of not inserting any value into the tables in execution.
3. If @IP value can't be inserted into the table ,as desired, is there any other way to see the output of EventData() or IP later.
Thanks in advance!!
[font="Comic Sans MS"]Vampire[/font]
--In 'thoughts'...
Lonely Rogue
March 20, 2009 at 7:41 am
Vampire (3/20/2009)
Thanks for the post Brian.However, I am stuck with few issues. Hope you could throw some light on them and clarify .
1. I executed the Step to insert <local machine< into ValidIP table and still i am not able to connect from my local machine, bcoz of trigger execution.
2. I changed the trigger to capture the @IP value in troubleshooting the above said issue. Below is my code:
CREATE TRIGGER tr_logon_CheckIP
ON ALL SERVER
FOR LOGON
AS
DECLARE @IP NVARCHAR(15),@SqlCmd NVARCHAR(100);
SET @IP = (SELECT EVENTDATA().value('(/EVENT_INSTANCE/ClientHost)[1]', 'NVARCHAR(15)'));
INSERT INTO dbo.ValidIP (IP) VALUES (@IP);
BEGIN
IF IS_SRVROLEMEMBER('sysadmin') = 1
BEGIN
IF NOT EXISTS(SELECT IP FROM DBAWork.dbo.ValidIP WHERE IP = @IP)
ROLLBACK;
END;
END;
GO
But this is not inserting any @IP value in the ValidIP table. Does triggers have constraint of not inserting any value into the tables in execution.
3. If @IP value can't be inserted into the table ,as desired, is there any other way to see the output of EventData() or IP later.
Thanks in advance!!
[font="Comic Sans MS"]Vampire[/font]
:hehe::hehe: Your code here is like a virus for SQL Server ( never never can connect to SQL )
You should have the DAC ( Dedicated Admin Connection) available or active before working with this trigger. Then connect to SQL server with DAC like Brian said in the article and be sure that the SQL Browser is running ...so you will connect to the Server on master DB and you should disable or delete the trigger!
:w00t::w00t::w00t::w00t::w00t::w00t::w00t:
March 20, 2009 at 1:54 pm
Vampire (3/20/2009)
this is not inserting any @IP value in the ValidIP table. Does triggers have constraint of not inserting any value into the tables in execution.3. If @IP value can't be inserted into the table ,as desired, is there any other way to see the output of EventData() or IP later.
Thanks in advance!!
[font="Comic Sans MS"]Vampire[/font]
The trigger is still, for accessing other objects, executing in the context of the login that's coming in. That means all logins need INSERT rights agaisnt the ValidIP table. If that's in a separate database, they need to have access to said database.
K. Brian Kelley
@kbriankelley
March 24, 2009 at 1:19 am
Brian,
I guess I dig grave for my own SQL Server :crying:
I have executed this trigger on a SQL Instance .\Inst1 and now it is not allowing me to connect from my local machine. However, let me state few facts:
1. I have inserted <local machine>, My computer Name and my IP address as values into ValidIP table, and now when i connect to the Instance from my computer(the instance on which trigger is created, also resides on my computer), the trigger executes. The login am using is a SysAdmin Acct.
2. Based on the above fact, my question is : This trigger allows only connections from the computers listed in ValidIP table..right? If yes, though I inserted my computer name in the ValidIP table..why is trigger executing?
3. What does statement return : (SELECT EVENTDATA().value('(/EVENT_INSTANCE/ClientHost)[1]', 'NVARCHAR(15)'));
Returns value as "<local machine>"; if connected from my computer OR
IP address of Local machine or computer from which connection origins??
4. I have used your tip of DAC to break this trigger barrier..it seems my DAC is also failing. I am pasting the Error output of my DAC connection. My question here is..does SQL instances support DAC Or is DAC available only for default instances.
C:\Documents and Settings\vampire>sqlcmd -S ADMIN:.\inst1 -A -dMaster
HResult 0xFFFFFFFF, Level 16, State 1
SQL Network Interfaces: An error occurred while obtaining the dedicated administrator
connection (DAC) port. Make sure that SQL Browser is running, or check the
error log for the port number [xFFFFFFFF].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
If DAC is available for SQL Instances also..so please based on the above output..can you suggest me some work around.
Thanks
Vampire
--In 'thoughts'...
Lonely Rogue
March 24, 2009 at 2:13 am
Vampire (3/24/2009)
Brian,I guess I dig grave for my own SQL Server :crying:
I have executed this trigger on a SQL Instance .\Inst1 and now it is not allowing me to connect from my local machine. However, let me state few facts:
1. I have inserted <local machine>, My computer Name and my IP address as values into ValidIP table, and now when i connect to the Instance from my computer(the instance on which trigger is created, also resides on my computer), the trigger executes. The login am using is a SysAdmin Acct.
2. Based on the above fact, my question is : This trigger allows only connections from the computers listed in ValidIP table..right? If yes, though I inserted my computer name in the ValidIP table..why is trigger executing?
3. What does statement return : (SELECT EVENTDATA().value('(/EVENT_INSTANCE/ClientHost)[1]', 'NVARCHAR(15)'));
Returns value as "<local machine>"; if connected from my computer OR
IP address of Local machine or computer from which connection origins??
4. I have used your tip of DAC to break this trigger barrier..it seems my DAC is also failing. I am pasting the Error output of my DAC connection. My question here is..does SQL instances support DAC Or is DAC available only for default instances.
C:\Documents and Settings\vampire>sqlcmd -S ADMIN:.\inst1 -A -dMaster
HResult 0xFFFFFFFF, Level 16, State 1
SQL Network Interfaces: An error occurred while obtaining the dedicated administrator
connection (DAC) port. Make sure that SQL Browser is running, or check the
error log for the port number [xFFFFFFFF].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
If DAC is available for SQL Instances also..so please based on the above output..can you suggest me some work around.
Thanks
Vampire
I told you in my post above that you should be sure that the SQL Browser is running ... also the DAC is only available from a client on the server!!!
Or you can do something in sqlcmd like this:
sqlcmd –A –d master
A - it will use the DAC connection
d - connection to the master DB
then you can kill or drop the trigger!!
:w00t:
March 24, 2009 at 2:58 am
Thanks for your tip..it worked. Am now able to login. However,I have my SQL Browser running earlier too...
I earlier used this command to connect to DAC as Admin..but couldn't
sqlcmd -S ADMIN:.\inst1 -A -dMaster
Dugi/Brian:
Could either of you please let me know the difference between these two along with answers to other questions ( posted in my previous reply, as this reply of yours answers my 4th question only).
Thanks a lot!!
Vampire
--In 'thoughts'...
Lonely Rogue
March 24, 2009 at 12:38 pm
Vampire (3/24/2009)
@DugiThanks for your tip..it worked. Am now able to login. However,I have my SQL Browser running earlier too...
I earlier used this command to connect to DAC as Admin..but couldn't
sqlcmd -S ADMIN:.\inst1 -A -dMaster
Dugi/Brian:
Could either of you please let me know the difference between these two along with answers to other questions ( posted in my previous reply, as this reply of yours answers my 4th question only).
Thanks a lot!!
Vampire
That means you connected to the default instance, not a named instance if you followed Dugi's example and left off -S.
K. Brian Kelley
@kbriankelley
April 23, 2009 at 8:17 am
The idea is very nice, but I can´t make this work.
The problem is that value() does not work inside logon triggers. In fact, it seems xqueries don´t work inside logon triggers.
I don´t have any trouble using them inside DDL triggers.
What I can do in a logon trigger is inserting the result of EVENTDATA() into a xml column. That is not what I need.
If anyone has an explanation or a solution for this, I would appreciate it very much.
April 24, 2009 at 2:44 pm
I will answer my own question. ARITHABORT must be on in order that xqueries such as VALUE() work.
So I began my logon trigger code with:
set arithabort on
and it worked nicely.
Thanxs 🙂
April 15, 2011 at 2:13 am
Hopefully I'm not being dim here, but this seems like a lot of effort and increased overhead on your SQL database, for something that can be handled much more efficiently at the transport layer. In general, if you want to ensure that connections to a server are only made by a specific IP address, then you set the network card up to only accept connections from a specific IP, address, or you use a firewall, since this is more robust at detecting IP spoofing ect... by all means, limit the access of the security principle, but creating a trigger for each time a connection is made seems like a really bad idea.:w00t:
April 15, 2011 at 2:40 am
In the past I have used IP restriction on the infrastructure side of things to get this done. Restricting PROD access to application, software management and SQL machines. But this is a nice way of doing it all in SQL.
Viewing 15 posts - 16 through 30 (of 53 total)
You must be logged in to reply to this topic. Login to reply