Re: SQL 2000 drops connection, DDOS attack?
- From: "Chris" <Chris@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 24 Feb 2006 05:23:27 -0800
Dan,
Run-time error '-2147467259 (80004005)':
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied.
Hope this helps. Thanks
"Dan Guzman" wrote:
What's the exact error you get from the application? If it's a 'general.
network error', you might try using a different protocol. This can be done
using the Client Network utility or specified in the connection string.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Chris" <Chris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3792EA5E-A646-400F-BE69-3B633807297E@xxxxxxxxxxxxxxxx
Dan,
I have tried this one before and it still doesn't get around the problem:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type SynAttackProtect, and then press ENTER.
5. On the Edit menu, click Modify.
6. In the Value data box, type 00000000. Click OK.
7. Quit Registry Editor.
Any other ideas please?? I would have thought this would have sorted it,
but
no. Please help. Thanks
"Dan Guzman" wrote:
Check out http://support.microsoft.com/kb/899599/en-us
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Chris" <Chris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A0620D88-A311-4346-A903-9556A66C40A8@xxxxxxxxxxxxxxxx
This is relating to SQL slammer question I posted.
We open 1 connection to SQL and we're
opening multiple recordsets, literally 1000s at a time. If you run it
on
the
server that is running SQL 2000 it's fine...but do this from a client
PC
then
you get a general network error. It's dropping the initial SQL
connection
halfway through running a recordset lookup and causes an error...as the
connection has been dropped. We can put a 30 second delay in there and
this
gets around the problem, while it restablishes the connection, but this
is
not practical. There must be something that can be done to tell SQL
2000
or
server 2003 sp1 to leave the connection alone when it's connected?? Any
ideas
anyone? Thanks
- Follow-Ups:
- Re: SQL 2000 drops connection, DDOS attack?
- From: Dan Guzman
- Re: SQL 2000 drops connection, DDOS attack?
- References:
- Re: SQL 2000 drops connection, DDOS attack?
- From: Dan Guzman
- Re: SQL 2000 drops connection, DDOS attack?
- From: Dan Guzman
- Re: SQL 2000 drops connection, DDOS attack?
- Prev by Date: Re: SQL 2000 drops connection, DDOS attack?
- Next by Date: Re: SQL 2000 drops connection, DDOS attack?
- Previous by thread: Re: SQL 2000 drops connection, DDOS attack?
- Next by thread: Re: SQL 2000 drops connection, DDOS attack?
- Index(es):
Relevant Pages
|