January 30, 2012 at 8:35 am
Hello,
I'm trying to connect to a sql server from my desktop to my laptop through SQL Management Studio, but I am getting the "Provider: Named Pipes Provider, Error 40 - Could not open a connection to SQL Server (Microsoft SQL Server, Error: 1326)" Error.
I cannot connect either way (Desktop -> Laptop or Laptop -> Desktop)
When I try Desktop -> Laptop, I get SQL Error 1326
When I try Laptop -> Desktop, I get SQL Error 1792
All of the sites I've seen have not been able to resolve this issue.
Details and steps I've done so far below:
Desktop
Windows XP SP3
SQL Server Express R2
Laptop
Windows Vista SP2
SQL Server Express R2
Steps:
Allow remote connections on both the desktop and laptop
Verified that SQL Browser is running on both computers
Verified that the port and SQL Browser are on the Exceptions list for Windows Firewall (doesn't work even if the firewall is off)
Added an alias for the laptop on the desktop and an alias for the desktop on the laptop
Added a user on the laptop SQL Server with all permissions (sysadmin, etc)
Pinged successfully the server on the laptop from the desktop and vice versa
Verified that both computers are on the same domain/workgroup
run the sqlcmd -L to verify that both servers are visible
Any further help to resolve this issue is appreciated.
:crazy:
January 30, 2012 at 8:56 am
Don't use named pipes. Used TCPIP
January 30, 2012 at 10:41 am
Thanks! That did the trick.
January 30, 2012 at 10:44 am
Aren't they removing named pipes entirely from the next version of MSSQL?
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 30, 2012 at 1:25 pm
Not that I know of. Named pipes is usually used for local connections. It's not listed as deprecated in the R2 docs: http://msdn.microsoft.com/en-us/library/ms187892.aspx
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply