2147467259 - [DBNETLIB][ConnectionWrite (send()).]General network

I Have SQL Express installed on 17 ships. Each ship has a VB6 Client
application using OLEDB to connect to the database on local machine. Other
workstations on network also connect - we think without error. The error
above is thrown on 4 of the 17 ships. The workstations acting as the file
server are supposed to be identical (Windows XP).
We have been assured that all poer save settings on LAN Card and motherboard
have been disabled.
If I google on this error, I get over 100 hits going back several years !
Ideas to fix have included turning off connection pooling and using TCPIP
instead of Named Pipes on client workstation where database server and
application are running.
Any other ideas on what could cause this, or why 13 machines are OK, but 4
are not ? Thanks.
Mark StoryPerhaps watching this might help:
http://support.microsoft.com/kb/875285/
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Mark Story" <MarkStory@.discussions.microsoft.com> wrote in message
news:E02C9E86-1EF3-40CD-8487-57B18A02BFCA@.microsoft.com...
>I Have SQL Express installed on 17 ships. Each ship has a VB6 Client
> application using OLEDB to connect to the database on local machine. Other
> workstations on network also connect - we think without error. The error
> above is thrown on 4 of the 17 ships. The workstations acting as the file
> server are supposed to be identical (Windows XP).
> We have been assured that all poer save settings on LAN Card and
> motherboard
> have been disabled.
> If I google on this error, I get over 100 hits going back several years !
> Ideas to fix have included turning off connection pooling and using TCPIP
> instead of Named Pipes on client workstation where database server and
> application are running.
> Any other ideas on what could cause this, or why 13 machines are OK, but 4
> are not ? Thanks.
>
> --
> Mark Story

2005 + Alias not working

I've just built our new 2005 cluster and I'm having some issues with
connectivity via a client network alias. It's a 2 node active/active 64 bit
Ent Edit, sp1, 32gb ram. Both nodes are listening on port 1433 with both tcp
and named pipes (although we never use named pipes)
Node Names are:
vdb1
vdb2\ins2
Most everything is working like a champ. Except setting up a local alias
from my machine.
I setup an alias that connects to vdb2\ins2. The alias name is vdb2, port is
1433. I cannot get sqlwb to connect via the alias.
Error message pop up is "An error has occurred while establishing a
connection to the server. When connecting to SQL Server 2005, this failure
may be caused by the fact that under the default settings SQL Server does no
t
allow remote connections. (Provider: TCP Provider, error: 0 - No Connection
could be made because the target machine actively refused it) (Microsoft SQL
Server, Error 10061).
I can connect directly to vbdb2\ins2 (not using the alias) without failure.
The reason why this is important is I have lots of linked server code on
vdb1 that references vdb2.dbname.dbo.tablename. I would have to touch a lo
t
of code (probably 100 stored procs) to be [vdb2\ins2].dbname.dbo.tablena
me.
The aliases are working in 2000 on our current production boxes, but it
doesn't work on 2005. Any ideas?I am having this exact same problem. Does anyone have any ideas'
*** Sent via Developersdex http://www.codecomments.com ***