August 25, 2009 at 1:21 pm
we are having some issues with one of my server.which is hosting the Named instance
Connecting from workstations.to the named instance is erroring out But I can connect it using port number or i can connect it locally.
when i restart the Browser service i see this warning massage
The configuration of the AdminConnection\TCP protocol in the SQL instance DEV is not valid.
i see bunch of kerboros errors on evernt log but not sure it preventing it or not.
August 25, 2009 at 1:31 pm
A couple of things to check:
Check in the SQL Server Configuration Manager > Network Protocols > Protocols
Verify that Hide instance is set to no
In SQL Server Surface Configuration Manager, make sure remote connections is set for TCP/IP and Named Pipes
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 25, 2009 at 2:57 pm
Client Protocols set to no
and remote connections are open for tcp and named pipes.
August 25, 2009 at 4:53 pm
Which version of Management Studio are you using and which version of SQL?
Are these connection issues related to trying to connect to SharePoint, WSUS or something like that?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 26, 2009 at 7:01 am
sql 2005 management studio,
version MSSQL 2005 ,4035
August 26, 2009 at 7:01 am
sql 2005 management studio,
version MSSQL 2005 ,4035
Its trying to connect to just sql server 2005
August 26, 2009 at 9:09 am
Are you using a service account for the Browser service startup? If so, is that account expired, or password expired?
Also try from a cmd prompt:
ipconfig /flushdns
And then have your networking guys verify dns settings (on the dns server) for the server that is having the issue.
We had some similar issues where we actually had to remove TCP/IP settings from the server and then reset them back to the settings we removed - in order to get some of the services to start back up. The server just lost itself somehow and wouldn't talk anymore to AD until we did that. That might be the next step for you as well.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply