Re: [DBNETLIB]ConnectionWrite (send()) error
- From: "Kevin3NF" <kevin@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 8 Nov 2006 15:28:50 -0600
At least we know that its trying to listen
From your client machine, assuming you have Query Analyzer, try to make anew connection. In the servername box, instead of SERVERNAME use
tcp:SERVERNAME, 1433
if that fails, try:
tcp:x.x.x.x, 14yy (replace x with your external ip, and 14yy with the
correct port)
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"mikron2" <mikron2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9D5AC8FF-7CF9-4BC0-9B12-13206F8CE225@xxxxxxxxxxxxxxxx
Sorry, I missed a line:
SQL server listening on TCP, Shared Memory, Named Pipes.
It's after the other two lines I mentioned earlier.
Mike
.
- References:
- Re: [DBNETLIB]ConnectionWrite (send()) error
- From: Kevin3NF
- Re: [DBNETLIB]ConnectionWrite (send()) error
- Prev by Date: Accessing Published SQL Databases from Active Directory
- Next by Date: Re: connect to remote sql server failed
- Previous by thread: Re: [DBNETLIB]ConnectionWrite (send()) error
- Next by thread: Accessing Published SQL Databases from Active Directory
- Index(es):
Relevant Pages
|
