November 28, 2012 at 3:56 pm
hi
i have 2 pc named PC1 and PC2 that connect with wired network.i installed SQL Server 2008 on both PC.(Instance Name :MySQLServer)
on PC1 i create a new SQL Server Authentication User named :User1 by a password for example "12345".
now when i try to connect to PC1's instance server from PC2 this error occure :
Cannot connect to PC1\MSSQLServer
Additional information
A connection was successfully established with the server , but
then an error occured during the login process .
(Provider : Named pipes provider , error : 0 - NO process is on the other end of the pipe )
(Microsoft SQL Server , error :233)[/purple]
November 28, 2012 at 5:25 pm
SQL 2005 or 2008?
If 2005, in the Surface Area Configuration application, check the Connections, then Remote Connections section, then check to see if you have Named Pipes and TCP/IP connections enabled.
In 2008, right-click on the server node and select facets.
How do you have it configured?
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
November 29, 2012 at 3:49 am
MyDoggieJessie (11/28/2012)
SQL 2005 or 2008?If 2005, in the Surface Area Configuration application, check the Connections, then Remote Connections section, then check to see if you have Named Pipes and TCP/IP connections enabled.
In 2008, right-click on the server node and select facets.
How do you have it configured?
thanks...i checked it . the remote connection is ok ... both of named pipes and TCP/IP connections are enable.
November 29, 2012 at 3:57 am
What port is SQL Server on PC1 listening on? If it's not the default, and if you don't have SQL Browser running on PC1, then you need to specify the port number when you connect. You can use SQL Server Configuration Manager on PC2 to make sure you're connecting with the correct network library - TCP/IP or Named Pipes.
John
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply