Thursday, March 8, 2012

Blocking a specific host

here's one... we have a rogue system on our network. Every 8months or so,
someone flips the "on" switch to the computer and brings it up. Aparently, it
has an application that uses a generic login (used by other applications) to
access SQL Server. The problem is, what ever file that once was there is no
longer there, so when the startup routine trys connecting to the db and
application, it gets connected to the db, but hangs trying to get connected
to the app. Our network team has no idea where the offending system is, but
obviously it's booted up every once in a blue moon.
My question is, can one block access from a Host to a SQL Server box? If
not, does anyone have ideas on how to capture the ip address or something
that could identify this rogue system by means other than User (remember,
it's a generic userid) or Host?
Thanks a ton for any idea presented!!Andy wrote:
> here's one... we have a rogue system on our network. Every 8months or
> so, someone flips the "on" switch to the computer and brings it up.
> Aparently, it has an application that uses a generic login (used by
> other applications) to access SQL Server. The problem is, what ever
> file that once was there is no longer there, so when the startup
> routine trys connecting to the db and application, it gets connected
> to the db, but hangs trying to get connected to the app. Our network
> team has no idea where the offending system is, but obviously it's
> booted up every once in a blue moon.
> My question is, can one block access from a Host to a SQL Server box?
> If not, does anyone have ideas on how to capture the ip address or
> something that could identify this rogue system by means other than
> User (remember, it's a generic userid) or Host?
> Thanks a ton for any idea presented!!
You can get the MAC address and Host Name from the sysprocesses table in
the master database once the rogue system in connected. Your network
admin should be able to trace that back to the PC that's causing the
problem.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com

No comments:

Post a Comment