| Groups | Blog | Home |
sql server replication : Non-Standard Port Problems
We are moving to SQL Server 2005 and have decided to use a non-standard port
number (port number other than 1433). We also decided to turn off the SQL Browser Services as well. This was done to enhance security, so now application need to provide <servername>,<port> number when connecting to SQL Server. For the most part we are able to connect from application no problem. But now we are setting up replication and looks like the GUI and Replication Monitor will not support specifying <servername>,<port> number. The also will not support Alias names. I got replication working by scripting the setup of replication, but it would be nice to be able to use the Replication Monitor. Any suggestions on how to get this GUI tools working with a non-standard port without SQL
Hello Greg,
If you are able to connect the respective server via MS SQL Server Management Studio than your tcp/ip port setting is ok. If not do the respective tcp/ip settings in SQL Server configuration manager. Cheers! MB [quoted text, click to view] "Greg Larsen" <gregalarsen@removeit.msn.com> wrote in message news:6AD88646-A301-4A8D-90CA-18246501008D@microsoft.com... > We are moving to SQL Server 2005 and have decided to use a non-standard > port > number (port number other than 1433). We also decided to turn off the SQL > Browser Services as well. This was done to enhance security, so now > application need to provide <servername>,<port> number when connecting to > SQL > Server. > > For the most part we are able to connect from application no problem. But > now we are setting up replication and looks like the GUI and Replication > Monitor will not support specifying <servername>,<port> number. The also > will not support Alias names. > > I got replication working by scripting the setup of replication, but it > would be nice to be able to use the Replication Monitor. Any suggestions > on > how to get this GUI tools working with a non-standard port without SQL > Browser Service running?
Yes, it requires the actual name, but you can hide the alias in the name.
For example your server name is Server1 (what you get when you do this select @@servername). Your FQDN is Server1.subdomain.domain.com. Your server is running on port 5000. Your alias name should be Server1. In the properties of your alias the port number would be 5000, the protocol tcpip and the server would be server1.subdomain.domain.com or you can use server1 and then in your hosts file have the ip address for server1.subdomain.domain.com mapped to server1. With this alias you should be able to register the subscriber in SSMS. HTH. -- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Greg Larsen" <gregalarsen@removeit.msn.com> wrote in message news:5CCDCA9F-E525-4EE3-8D3A-9454A19B27CF@microsoft.com... >I tried setting up an alias and using that and got the following error: > SQL Server replication requires the actual server name to make a > connection > to the server. Connections throught a server alias, IP address, or any > other > alternative are not supported. Specify the actual server name, '<server > name.'. (Replication.Utility) > > So doesn't look like your solution will work, or am I missing something. > > > "Hilary Cotter" wrote: > >> use client network utility (sql 2000) or sql server configuration manager >> (sql 2005) to build an alias to your sql server and specify the port >> there. >> Then use this alias to build your subscriber. >> >> -- >> Hilary Cotter >> >> Looking for a SQL Server replication book? >> http://www.nwsu.com/0974973602.html >> >> Looking for a FAQ on Indexing Services/SQL FTS >> http://www.indexserverfaq.com >> >> >> >> "Greg Larsen" <gregalarsen@removeit.msn.com> wrote in message >> news:6AD88646-A301-4A8D-90CA-18246501008D@microsoft.com... >> > We are moving to SQL Server 2005 and have decided to use a non-standard >> > port >> > number (port number other than 1433). We also decided to turn off the >> > SQL >> > Browser Services as well. This was done to enhance security, so now >> > application need to provide <servername>,<port> number when connecting >> > to >> > SQL >> > Server. >> > >> > For the most part we are able to connect from application no problem. >> > But >> > now we are setting up replication and looks like the GUI and >> > Replication >> > Monitor will not support specifying <servername>,<port> number. The >> > also >> > will not support Alias names. >> > >> > I got replication working by scripting the setup of replication, but it >> > would be nice to be able to use the Replication Monitor. Any >> > suggestions >> > on >> > how to get this GUI tools working with a non-standard port without SQL >> > Browser Service running? >> >> >>
I tried setting up an alias and using that and got the following error:
SQL Server replication requires the actual server name to make a connection to the server. Connections throught a server alias, IP address, or any other alternative are not supported. Specify the actual server name, '<server name.'. (Replication.Utility) So doesn't look like your solution will work, or am I missing something. [quoted text, click to view] "Hilary Cotter" wrote:
> use client network utility (sql 2000) or sql server configuration manager > (sql 2005) to build an alias to your sql server and specify the port there. > Then use this alias to build your subscriber. > > -- > Hilary Cotter > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > > > > "Greg Larsen" <gregalarsen@removeit.msn.com> wrote in message > news:6AD88646-A301-4A8D-90CA-18246501008D@microsoft.com... > > We are moving to SQL Server 2005 and have decided to use a non-standard > > port > > number (port number other than 1433). We also decided to turn off the SQL > > Browser Services as well. This was done to enhance security, so now > > application need to provide <servername>,<port> number when connecting to > > SQL > > Server. > > > > For the most part we are able to connect from application no problem. But > > now we are setting up replication and looks like the GUI and Replication > > Monitor will not support specifying <servername>,<port> number. The also > > will not support Alias names. > > > > I got replication working by scripting the setup of replication, but it > > would be nice to be able to use the Replication Monitor. Any suggestions > > on > > how to get this GUI tools working with a non-standard port without SQL > > Browser Service running? > >
use client network utility (sql 2000) or sql server configuration manager
(sql 2005) to build an alias to your sql server and specify the port there. Then use this alias to build your subscriber. -- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Greg Larsen" <gregalarsen@removeit.msn.com> wrote in message news:6AD88646-A301-4A8D-90CA-18246501008D@microsoft.com... > We are moving to SQL Server 2005 and have decided to use a non-standard > port > number (port number other than 1433). We also decided to turn off the SQL > Browser Services as well. This was done to enhance security, so now > application need to provide <servername>,<port> number when connecting to > SQL > Server. > > For the most part we are able to connect from application no problem. But > now we are setting up replication and looks like the GUI and Replication > Monitor will not support specifying <servername>,<port> number. The also > will not support Alias names. > > I got replication working by scripting the setup of replication, but it > would be nice to be able to use the Replication Monitor. Any suggestions > on > how to get this GUI tools working with a non-standard port without SQL > Browser Service running?
Your suggestion solved the problem. Once I created an alias using a FQDN
then I was able to use the GUI to create and manager replication. Thanks for the tips. No documentation pointed this out. [quoted text, click to view] "Hilary Cotter" wrote:
> Yes, it requires the actual name, but you can hide the alias in the name. > > For example your server name is Server1 (what you get when you do this > select @@servername). Your FQDN is Server1.subdomain.domain.com. Your server > is running on port 5000. > > Your alias name should be Server1. In the properties of your alias the port > number would be 5000, the protocol tcpip and the server would be > server1.subdomain.domain.com or you can use server1 and then in your hosts > file have the ip address for server1.subdomain.domain.com mapped to server1. > > With this alias you should be able to register the subscriber in SSMS. > > HTH. > > -- > Hilary Cotter > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > > > > "Greg Larsen" <gregalarsen@removeit.msn.com> wrote in message > news:5CCDCA9F-E525-4EE3-8D3A-9454A19B27CF@microsoft.com... > >I tried setting up an alias and using that and got the following error: > > SQL Server replication requires the actual server name to make a > > connection > > to the server. Connections throught a server alias, IP address, or any > > other > > alternative are not supported. Specify the actual server name, '<server > > name.'. (Replication.Utility) > > > > So doesn't look like your solution will work, or am I missing something. > > > > > > "Hilary Cotter" wrote: > > > >> use client network utility (sql 2000) or sql server configuration manager > >> (sql 2005) to build an alias to your sql server and specify the port > >> there. > >> Then use this alias to build your subscriber. > >> > >> -- > >> Hilary Cotter > >> > >> Looking for a SQL Server replication book? > >> http://www.nwsu.com/0974973602.html > >> > >> Looking for a FAQ on Indexing Services/SQL FTS > >> http://www.indexserverfaq.com > >> > >> > >> > >> "Greg Larsen" <gregalarsen@removeit.msn.com> wrote in message > >> news:6AD88646-A301-4A8D-90CA-18246501008D@microsoft.com... > >> > We are moving to SQL Server 2005 and have decided to use a non-standard > >> > port > >> > number (port number other than 1433). We also decided to turn off the > >> > SQL > >> > Browser Services as well. This was done to enhance security, so now > >> > application need to provide <servername>,<port> number when connecting > >> > to > >> > SQL > >> > Server. > >> > > >> > For the most part we are able to connect from application no problem. > >> > But > >> > now we are setting up replication and looks like the GUI and > >> > Replication > >> > Monitor will not support specifying <servername>,<port> number. The > >> > also > >> > will not support Alias names. > >> > > >> > I got replication working by scripting the setup of replication, but it > >> > would be nice to be able to use the Replication Monitor. Any > >> > suggestions > >> > on > >> > how to get this GUI tools working with a non-standard port without SQL > >> > Browser Service running? > >> > >> > >> > >
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |