Timeline for SQL Server 2012 - SA account probe
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2015 at 1:42 | history | tweeted | twitter.com/#!/StackDBAs/status/634903439798108160 | ||
| Aug 19, 2015 at 14:14 | vote | accept | Nelson Pires | ||
| Aug 18, 2015 at 1:08 | comment | added | Ali Razeghi - AWS | You could use a port forwarder and proxy to hit the dev box from the same ip. You could RDP in to that network to do work. You can automate the IP settings and only have it off while you're working then have it turn back on. You can set it up as part of something like a octopus/jenkins system like you do dev. There's many options, do any of those work for you? | |
| Aug 18, 2015 at 0:44 | answer | added | Kin Shah | timeline score: 5 | |
| Aug 18, 2015 at 0:36 | answer | added | IT Thug Ninja | timeline score: 7 | |
| Aug 18, 2015 at 0:03 | comment | added | mustaccio | May be there is such a tool, but then 1) you may want to clarify what you ask in the question itself and 2) it's not a SQL Server problem; you may have better chance asking about it at Server Fault | |
| Aug 17, 2015 at 23:58 | comment | added | Nelson Pires | I have closed the SQL port and that stopped all the probing by I have to remember to enable my IP in all the time (dynamic IP) for development. Isn't there a tool that looks at the windows log files and on those events that show a SQL probe, add the IPs to the firewall to block them automatically? | |
| Aug 17, 2015 at 23:52 | comment | added | mustaccio | You appear to be able to block IPs in the Windows firewall; I'm sure closing ports should also be available as an option, no? | |
| Aug 17, 2015 at 23:45 | review | First posts | |||
| Aug 17, 2015 at 23:52 | |||||
| Aug 17, 2015 at 23:44 | history | asked | Nelson Pires | CC BY-SA 3.0 |