April 1, 2010 at 4:09 pm
CirquedeSQLeil (4/1/2010)
In that article I gave it discusses how the Browser Service is used for Named Instances. If you specify a different than default port for the default instance you must specify the port.
I think you are right. When using default instance and port other than 1433, we need to tell client the port number.
"If a default instance of SQL Server is listening on a port other than port 1433, you must either define a server alias name or change the global default port by using the Client Network Utility. However, you can also make the default instance of SQL Server listen on multiple static ports. "
The SQL Browser is only used for named instances.
April 1, 2010 at 4:09 pm
Nicholas Cain (4/1/2010)
So on the Protocol tab you have-Enabled Yes
-Keep Alive 30000 (example value)
-Listen All Yes
Have you changed the values under IPAll and set
-TCP Dynamic Ports to nothing (leave blank)
-TCP Port 1533
Yes. I tried. Doesn't work.
April 1, 2010 at 4:13 pm
rainleta (4/1/2010)
CirquedeSQLeil (4/1/2010)
In that article I gave it discusses how the Browser Service is used for Named Instances. If you specify a different than default port for the default instance you must specify the port.I think you are right. When using default instance and port other than 1433, we need to tell client the port number.
"If a default instance of SQL Server is listening on a port other than port 1433, you must either define a server alias name or change the global default port by using the Client Network Utility. However, you can also make the default instance of SQL Server listen on multiple static ports. "
The SQL Browser is only used for named instances.
If you go back to the default port, are you able to connect now without error?
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
April 1, 2010 at 4:27 pm
CirquedeSQLeil (4/1/2010)
rainleta (4/1/2010)
CirquedeSQLeil (4/1/2010)
In that article I gave it discusses how the Browser Service is used for Named Instances. If you specify a different than default port for the default instance you must specify the port.I think you are right. When using default instance and port other than 1433, we need to tell client the port number.
"If a default instance of SQL Server is listening on a port other than port 1433, you must either define a server alias name or change the global default port by using the Client Network Utility. However, you can also make the default instance of SQL Server listen on multiple static ports. "
The SQL Browser is only used for named instances.
If you go back to the default port, are you able to connect now without error?
Yes. No problem at all with 1433.
April 1, 2010 at 4:58 pm
rainleta (4/1/2010)
CirquedeSQLeil (4/1/2010)
rainleta (4/1/2010)
CirquedeSQLeil (4/1/2010)
In that article I gave it discusses how the Browser Service is used for Named Instances. If you specify a different than default port for the default instance you must specify the port.I think you are right. When using default instance and port other than 1433, we need to tell client the port number.
"If a default instance of SQL Server is listening on a port other than port 1433, you must either define a server alias name or change the global default port by using the Client Network Utility. However, you can also make the default instance of SQL Server listen on multiple static ports. "
The SQL Browser is only used for named instances.
If you go back to the default port, are you able to connect now without error?
Yes. No problem at all with 1433.
As i expected but wanted to confirm.
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 5 posts - 31 through 34 (of 34 total)
You must be logged in to reply to this topic. Login to reply