Re: security SQL

Tech-Archive recommends: Fix windows errors by optimizing your registry

after running some days with the ports disabled. i still get my errors.

source: MSSQLSERVER
event-id: 18452
latest event: 16-1-2008 21:39
total events 5 *
Login failed for user 'sa'. The user is not associated with a trusted SQL
Server connection. [CLIENT: 145.52.250.194]

this is not my domain IP. how can i get other computers not contacting my
SQL?





"rostie" wrote:

i disabled all packages using port 1433 and 1434 on my internet line on the
NAT configuration. i hope this keeps the messages from getting into my system.


"bass_player [SBS-MVP]" wrote:

Make sure port 1433 and port 1434 are not opened on your router/firewall.
Also, the SA account is disabled by default in SQL Server 2005

"rostie" <rostie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CB13CB14-75A5-4E9E-B33E-AB63F19AE0D5@xxxxxxxxxxxxxxxx
I recently installed SQL workgroup edition (it came with my SBS premium)
sine then i have in a daily base multiple errors of user SA that cant
connect to the database because the logon failed.

i tracked the IP-records on the failures and noticed that they all came
from
all over the world.

is my SQL open to everyone on this planet and if so how can i get it to be
only usable within my domain (i dont need to publish online YET)

i didnt configure the SQL server yet so i guess its on windows
authentication.
i just dont like those errors in my reports.

thanks




.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS
    ... I'm not seeing performance issues with the full enchilada installed, and 25 users busy hitting SQL. ... WSUS isn't difficult to uninstall - if you have WSUS v2 (installed with SBS R2) uninstall R2 from add/remove programs. ... How can anyone work with 4 instances of SQL Server on the same box? ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Resets
    ... If it were SQL that was falling short, ... The default backlog for SQL Server is 5. ... System.InvalidOperationException: Internal connection fatal error. ... From time to time, under heavy loads, we are getting resets at ...
    (microsoft.public.sqlserver.connect)