Can I protect MSSQL in such a way with to connect the SQL error come??? Because I often see with other MSSQL. Have belongs does one must a file delete or like functioned that?

ok

use this command to delete the cmdshell
sp_dropextendedproc xp_cmdshell
works good in a bat too!

taimoor stop spamming.

you have to switch the dll`s then you'll get the SQL_ERROR on connecting. dropping the cmdshell won't result in a SQL_ERROR!

switching DLLs is not needed, if you delete the xpcmdshell noone can exec commands on that server bud

well just reread this
to drop a xp doesnt mean its deleted dude. your server is in noway secured then.
its one cmd to reload the extanded procedure.

I will be a unhackable SQL_ERROr, the drop cmdshell are very easy to hack!!!

Witch dlls must i renamord deltree?

every day the same lame questions...

I don't understand how this people get member status without the knowledgement to use the search button..

sometimes the posts are really senseless..

'I will be a unhackable SQL_ERROR,the drop cmdshell are very easy to hack'

I think many people wrote that securing the account is the only real way ..drop the xp_cmdshell or delete/rename the .dll is worthless ..i should not really care about but
reading GSO was interesting some time ago at the moment [censored]..just my 2 cents