June 22, 2006 at 6:10 am
Hi
We have installed SQL Server 2005 Enterprise Evaluation Edition for testing purpose.
In Surface Area Configuration, we had set "Local and Remote Connections" as "Using both TCP/IP and named pipes" In SQL Server Configuration Manager, we had enabled "SQL Server 2005 Network Configuration" for Shared Memory, Named Pipes and TCP/IP.
Now we cannot connect from client (SSMS) to access this server. Anyone can help me please.
Thanks
Sathish
S A T ...
Sathish's Blog
June 23, 2006 at 1:14 am
Hi Sathish..
Are you running the Windows Firewall on your SQL Server box? If so, you might want to make sure that sqlservr.exe is not blocked at the firewall.
Hope this helps..
- Ward Pond
blogs.technet.com/wardpond
June 23, 2006 at 7:54 am
After you made the network connectivity changes, SQL Server was restarted? Also, when the SQL Server was last restarted, was it able to bind to the various network libraries you have specified?
K. Brian Kelley
@kbriankelley
June 26, 2006 at 6:40 am
Brian
Yes I restarted the SQL Server as well as restarted the server.
How can I check whether it is bind to various libraries ?
Sathish
S A T ...
Sathish's Blog
June 26, 2006 at 2:04 pm
In the SQL Server event log it'll tell you what it's listening on. For instance...
Named Pipes:
Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$NamedInstance\sql\query ]
TCP/IP:
Server is listening on [ 'any' 1433]
Shared Memory:
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\NamedInstance ]
K. Brian Kelley
@kbriankelley
June 28, 2006 at 2:51 am
Brian
Yes the following messages were found in SQL Server Event Log
1. Server is listening on [ 'any' <ipv4> 1433].
2. Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
3. Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
4. Server is listening on [ 127.0.0.1 <ipv4> 1434].
Then the following message is found
1. Dedicated admin connection support was established for listening locally on port 1434.
2. SQL Server is now ready for client connections. This is an informational message; no user action is required.
But the next message is
The Service Broker protocol transport is disabled or not configured.
Does I need to configure the Service Broker protocol for client connection. Can you pls help me in cofiguring the same ?
Sathish
S A T ...
Sathish's Blog
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply