Non-standard port through router

Here's my setup. I have an SQL server machine with a local LAN ip. I have
a router with an internet IP. I configured the router to pass external port
5000 through to the sql machine's ip on port 1433. When I try to connect to
the sql server using the router's IP and port 5000 I get a timeout. I can
telnet to the router's IP and port 5000 (get a blank screen, but connection
succeeds).
Does anyone know why I would be getting a timeout? If I (internaly) connect
to the sql machine's local LAN IP port 1433 I can access the SQL server with
no problems.
Hi Lee,
If you get a blank black screen from telnet <MachineName>_or_<IP> <Port
Number>, then you have succeeded in connecting over TCP/IP to the ROUTER
port. We are not able to say it connects to SQL Server's TCP/IP port
successfully. I still think your mapping in router is not configured
correctly.
Secondly, what client tools you used to connect SQL Server? Query Analyzer?
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
sql

Non-Standard Port for SQL2K

If SQL2K is not listening to the standard ports because
1433 has been changed to 14000, then what should the
connectionstring in as ASP page look like so that it uses
the correct port in order to make the connection?
object.ConnectionString(
"Provider=SQLOLEDB.1;
Data Source=MyServer;
Catalog=MyDB;
Persist Security Info=False;
UID=MyUID;
PWD=MyPWD;"
)Create an alias in the client network utility and specify the port there.
This approach is better because if the port/server changes then you don't
have to change your code.
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"Michael" <anonymous@.discussions.microsoft.com> wrote in message
news:577801c3e502$311a2c40$a601280a@.phx.gbl...

quote:

---

> If SQL2K is not listening to the standard ports because
> 1433 has been changed to 14000, then what should the
> connectionstring in as ASP page look like so that it uses
> the correct port in order to make the connection?
> object.ConnectionString(
> "Provider=SQLOLEDB.1;
> Data Source=MyServer;
> Catalog=MyDB;
> Persist Security Info=False;
> UID=MyUID;
> PWD=MyPWD;"
> )
>

---

|||Thank you Carlos. I'll give it a shot.

quote:

---

>--Original Message--
>Create an alias in the client network utility and specify

---

the port there.

quote:

---

>This approach is better because if the port/server

---

changes then you don't

quote:

---

>have to change your code.
>--
>Carlos E. Rojas
>SQL Server MVP
>Co-Author SQL Server 2000 programming by Example
>
>"Michael" <anonymous@.discussions.microsoft.com> wrote in

---

message

quote:

---

>news:577801c3e502$311a2c40$a601280a@.phx.gbl...
uses[QUOTE]
>
>.
>

---

Non-Default SQL Server Port

Using Visual Studio .NET 2005 and I cannot make a database connection in sever explorer to a SQL server that listens on a non-default port. I can do this with VS .NET 2003, but not 2005. Please assist.Please help on this.|||

What is the version of the SQL Server?

Does the SQL Server and the connection application run on the same machine or on two different machines?

What protocols are enabled on the SQL Server?

What connection string does the application use?

Depending on your connection string you may need to start the SQL Browser service on the machine running SQL Server.

|||

SQL Server 2000
SQL Server 2000 and Visual Studio .NET 2005 are on seperate boxes.
SQL Server is listening on a non-default port (9696).
Just trying to connect to the database in server explorer.

Non standard port - non default instance

Hi all,
I'm trying to create a subscription for a merge replication on a sql
server mobile 2005 based application.
The publisher is on a intranet, listening on port 9091 and with a named
instance.
The merge agent is in a DMZ with port 9091 open for inbound/outbound TCP
traffic to the intranet.
Problem:
when I try to synchronize I receive the "SQL Server does not exists" error.
My subscription has the following setup:
Publisher = "ServerName\InstanceName";
PublisherNetwork = NetworkType.TcpIpSockets;
PublisherAddress = "10.xxx.xxx.xxx,9091";
PublisherDatabase = "DatabaseName";
PublisherSecurityMode = SecurityType.DBAuthentication;
PublisherLogin = "name";
PublisherPassword = "pwd";
name/pwd user has correct priviledges non publisher database.
I can connect via SQL Client to the database from the machine in DMZ.
In my (many) tries, I also created an alias on the DMZ client and used
that for the Publisher property at the subscriber.
Nothing worked.
I'm finishing options...
Cl@. ha scritto:

> Problem:
> when I try to synchronize I receive the "SQL Server does not exists" error.
I solved opening 1434 udp port.
Question is: why sql client can connect without 1434 port open and the
merge agent can't?

non default port - client cannot connect

I have changed the default port away from 1433 on sql server 2005. Now I
cannot connect from pc. What do I need to change on the client pc?
Thanks
Connect by adding a comma and port number after machine name, like:
machinename,1456
Or use cliconfg.exe to add an alias and specify the port number in that alias.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"guest5" <guest5@.discussions.microsoft.com> wrote in message
news:0A38D0A1-E40F-4A97-93D6-5C288E867802@.microsoft.com...
>I have changed the default port away from 1433 on sql server 2005. Now I
> cannot connect from pc. What do I need to change on the client pc?
> Thanks

non default port - client cannot connect

I have changed the default port away from 1433 on sql server 2005. Now I
cannot connect from pc. What do I need to change on the client pc?
ThanksConnect by adding a comma and port number after machine name, like:
machinename,1456
Or use cliconfg.exe to add an alias and specify the port number in that alia
s.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"guest5" <guest5@.discussions.microsoft.com> wrote in message
news:0A38D0A1-E40F-4A97-93D6-5C288E867802@.microsoft.com...
>I have changed the default port away from 1433 on sql server 2005. Now I
> cannot connect from pc. What do I need to change on the client pc?
> Thanks

non default port - client cannot connect

I have changed the default port away from 1433 on sql server 2005. Now I
cannot connect from pc. What do I need to change on the client pc?
ThanksConnect by adding a comma and port number after machine name, like:
machinename,1456
Or use cliconfg.exe to add an alias and specify the port number in that alias.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"guest5" <guest5@.discussions.microsoft.com> wrote in message
news:0A38D0A1-E40F-4A97-93D6-5C288E867802@.microsoft.com...
>I have changed the default port away from 1433 on sql server 2005. Now I
> cannot connect from pc. What do I need to change on the client pc?
> Thanks

Non default port

I am using SQL 2005 and have multiple instances installed on multiple
servers. None are on the default port. When I connect to box 01
without specifying the port in the connection string, it connects.
But on box 02, it will only connect to the instance if I specify the
port name. Is this because it will only connect to the default
instance without specifying a port? or is there something else I need
to have setup on box 02 to make this work?
thanks in advance
> Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
Check to ensure the SQL Browser service is running as Tibor suggested.
Another possible cause is that UDP port 1434 is blocked.
When you connect to the default instance, TCP port 1433 is used by default.
When you connect to a named instance without a specifying a port, the client
requests a list of the named instances and corresponding ports via UDP port
1434 (this is the SQL Browser service). The client then determines the
named instance port.
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"Victag" <miketaggart@.gmail.com> wrote in message
news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>I am using SQL 2005 and have multiple instances installed on multiple
> servers. None are on the default port. When I connect to box 01
> without specifying the port in the connection string, it connects.
> But on box 02, it will only connect to the instance if I specify the
> port name. Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
> thanks in advance
|||On Mar 13, 4:26Xam, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> Check to ensure the SQL Browser service is running as Tibor suggested.
> Another possible cause is that UDP port 1434 is blocked.
> When you connect to the default instance, TCP port 1433 is used by default..
> When you connect to a named instance without a specifying a port, the client
> requests a list of the named instances and corresponding ports via UDP port
> 1434 (this is the SQL Browser service). XThe client then determines the
> named instance port.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVPhttp://weblogs.sqlteam.com/dang/
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>
>
> - Show quoted text -
Thanks folks! I have checked and the Browser service is disabled on
both boxes (event he working one), so I could try turning it on, but I
would rather explain/understand what the difference is between these
boxes. I have also confirmed that no ports are blocked at all. Any
other suggestions?
|||Hi,
You can access named instances (if you know port number) in this way:
tcp:server_name,port_number
Regards,
anxcomp
|||On Mar 13, 11:12Xam, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> <<Thanks folks! XI have checked and the Browser service is disabled on
> both boxes (event he working one), so I could try turning it on, but I
> would rather explain/understand what the difference is between these
> boxes. XI have also confirmed that no ports are blocked at all. XAny
> other suggestions?>>
> We can only explain how things work:
> When you connect to a default instance (no backslash and instance name), the data access components
> will connect to port 1433. The SQL Server service by default listens to 1433 for a default instance
> (well-known port).
> The port number for a named instance is determined dynamically the first time you start the
> instance. SQL Server asks Windows for an available port, uses it and stores the port number in the
> registry (as you can see using SQL Server Configuration Manager). It will try to use the same port
> number on subsequent start-ups.
> If you from the client app only specify machine name/IP backslash instancename, then you need some
> component to translate this instance name to a port number. That componentis SQL Server Browser
> service. The client data access components connects to the SSB service using port 1434 UDP and
> passes the instance name, and the SSB service returns the port number. Youcan also from the client
> app specify machine/IP comma portnumber, so there would now be no use for the SSB service. SQL
> Server 2000 didn't come with an SSB service so for 2000 the database engine did this job (listening
> on port 1434).
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:bee0415f-6523-45e7-9d46-ad9a01846809@.d62g2000hsf.googlegroups.com...
> On Mar 13, 4:26 am, "Dan Guzman" <guzma...@.nospam-
>
>
> online.sbcglobal.net> wrote:
>
>
>
>
>
> Thanks folks! XI have checked and the Browser service is disabled on
> both boxes (event he working one), so I could try turning it on, but I
> would rather explain/understand what the difference is between these
> boxes. XI have also confirmed that no ports are blocked at all. XAny
> other suggestions... Hide quoted text -
> - Show quoted text -
Thanks again. I have made progress and found that the boxes that are
not working have many client aliases created on them, some of which
appear to be invalid. When I deleted the aliases that did not exist
on the server that is working, it fixed them. So now that I know how
to fix it, I am curious to know how these bad aliases got created
since we did not create them manually.
|||"Victag" wrote:

>I am curious to know how these bad aliases got created
> since we did not create them manually.
Did you install Visio? For example Visio installation process create for me
some alias. I have to delete it manually.
Regards,
anxcomp

Non default port

I am using SQL 2005 and have multiple instances installed on multiple
servers. None are on the default port. When I connect to box 01
without specifying the port in the connection string, it connects.
But on box 02, it will only connect to the instance if I specify the
port name. Is this because it will only connect to the default
instance without specifying a port? or is there something else I need
to have setup on box 02 to make this work?
thanks in advance :)See if the SQL Server Browser service is started on box 02.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Victag" <miketaggart@.gmail.com> wrote in message
news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>I am using SQL 2005 and have multiple instances installed on multiple
> servers. None are on the default port. When I connect to box 01
> without specifying the port in the connection string, it connects.
> But on box 02, it will only connect to the instance if I specify the
> port name. Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
> thanks in advance :)|||> Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
Check to ensure the SQL Browser service is running as Tibor suggested.
Another possible cause is that UDP port 1434 is blocked.
When you connect to the default instance, TCP port 1433 is used by default.
When you connect to a named instance without a specifying a port, the client
requests a list of the named instances and corresponding ports via UDP port
1434 (this is the SQL Browser service). The client then determines the
named instance port.
--
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"Victag" <miketaggart@.gmail.com> wrote in message
news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>I am using SQL 2005 and have multiple instances installed on multiple
> servers. None are on the default port. When I connect to box 01
> without specifying the port in the connection string, it connects.
> But on box 02, it will only connect to the instance if I specify the
> port name. Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
> thanks in advance :)|||On Mar 13, 4:26=A0am, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> > Is this because it will only connect to the default
> > instance without specifying a port? or is there something else I need
> > to have setup on box 02 to make this work?
> Check to ensure the SQL Browser service is running as Tibor suggested.
> Another possible cause is that UDP port 1434 is blocked.
> When you connect to the default instance, TCP port 1433 is used by default=.
> When you connect to a named instance without a specifying a port, the clie=nt
> requests a list of the named instances and corresponding ports via UDP por=t
> 1434 (this is the SQL Browser service). =A0The client then determines the
> named instance port.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVPhttp://weblogs.sqlteam.com/dang/
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>
> >I am using SQL 2005 and have multiple instances installed on multiple
> > servers. =A0None are on the default port. =A0When I connect to box 01
> > without specifying the port in the connection string, it connects.
> > But on box 02, it will only connect to the instance if I specify the
> > port name. =A0Is this because it will only connect to the default
> > instance without specifying a port? or is there something else I need
> > to have setup on box 02 to make this work?
> > thanks in advance :)- Hide quoted text -
> - Show quoted text -
Thanks folks! I have checked and the Browser service is disabled on
both boxes (event he working one), so I could try turning it on, but I
would rather explain/understand what the difference is between these
boxes. I have also confirmed that no ports are blocked at all. Any
other suggestions?|||<<Thanks folks! I have checked and the Browser service is disabled on
both boxes (event he working one), so I could try turning it on, but I
would rather explain/understand what the difference is between these
boxes. I have also confirmed that no ports are blocked at all. Any
other suggestions?>>
We can only explain how things work:
When you connect to a default instance (no backslash and instance name), the data access components
will connect to port 1433. The SQL Server service by default listens to 1433 for a default instance
(well-known port).
The port number for a named instance is determined dynamically the first time you start the
instance. SQL Server asks Windows for an available port, uses it and stores the port number in the
registry (as you can see using SQL Server Configuration Manager). It will try to use the same port
number on subsequent start-ups.
If you from the client app only specify machine name/IP backslash instancename, then you need some
component to translate this instance name to a port number. That component is SQL Server Browser
service. The client data access components connects to the SSB service using port 1434 UDP and
passes the instance name, and the SSB service returns the port number. You can also from the client
app specify machine/IP comma portnumber, so there would now be no use for the SSB service. SQL
Server 2000 didn't come with an SSB service so for 2000 the database engine did this job (listening
on port 1434).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Victag" <miketaggart@.gmail.com> wrote in message
news:bee0415f-6523-45e7-9d46-ad9a01846809@.d62g2000hsf.googlegroups.com...
On Mar 13, 4:26 am, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> > Is this because it will only connect to the default
> > instance without specifying a port? or is there something else I need
> > to have setup on box 02 to make this work?
> Check to ensure the SQL Browser service is running as Tibor suggested.
> Another possible cause is that UDP port 1434 is blocked.
> When you connect to the default instance, TCP port 1433 is used by default.
> When you connect to a named instance without a specifying a port, the client
> requests a list of the named instances and corresponding ports via UDP port
> 1434 (this is the SQL Browser service). The client then determines the
> named instance port.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVPhttp://weblogs.sqlteam.com/dang/
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>
> >I am using SQL 2005 and have multiple instances installed on multiple
> > servers. None are on the default port. When I connect to box 01
> > without specifying the port in the connection string, it connects.
> > But on box 02, it will only connect to the instance if I specify the
> > port name. Is this because it will only connect to the default
> > instance without specifying a port? or is there something else I need
> > to have setup on box 02 to make this work?
> > thanks in advance :)- Hide quoted text -
> - Show quoted text -
Thanks folks! I have checked and the Browser service is disabled on
both boxes (event he working one), so I could try turning it on, but I
would rather explain/understand what the difference is between these
boxes. I have also confirmed that no ports are blocked at all. Any
other suggestions?|||Hi,
You can access named instances (if you know port number) in this way:
tcp:server_name,port_number
--
Regards,
anxcomp|||On Mar 13, 11:12=A0am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> <<Thanks folks! =A0I have checked and the Browser service is disabled on
> both boxes (event he working one), so I could try turning it on, but I
> would rather explain/understand what the difference is between these
> boxes. =A0I have also confirmed that no ports are blocked at all. =A0Any
> other suggestions?>>
> We can only explain how things work:
> When you connect to a default instance (no backslash and instance name), t=he data access components
> will connect to port 1433. The SQL Server service by default listens to 14=33 for a default instance
> (well-known port).
> The port number for a named instance is determined dynamically the first t=ime you start the
> instance. SQL Server asks Windows for an available port, uses it and store=s the port number in the
> registry (as you can see using SQL Server Configuration Manager). It will =try to use the same port
> number on subsequent start-ups.
> If you from the client app only specify machine name/IP backslash instance=name, then you need some
> component to translate this instance name to a port number. That component= is SQL Server Browser
> service. The client data access components connects to the SSB service usi=ng port 1434 UDP and
> passes the instance name, and the SSB service returns the port number. You= can also from the client
> app specify machine/IP comma portnumber, so there would now be no use for =the SSB service. SQL
> Server 2000 didn't come with an SSB service so for 2000 the database engin=e did this job (listening
> on port 1434).
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph=
ttp://sqlblog.com/blogs/tibor_karaszi
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:bee0415f-6523-45e7-9d46-ad9a01846809@.d62g2000hsf.googlegroups.com...
> On Mar 13, 4:26 am, "Dan Guzman" <guzma...@.nospam-
>
>
> online.sbcglobal.net> wrote:
> > > Is this because it will only connect to the default
> > > instance without specifying a port? or is there something else I need
> > > to have setup on box 02 to make this work?
> > Check to ensure the SQL Browser service is running as Tibor suggested.
> > Another possible cause is that UDP port 1434 is blocked.
> > When you connect to the default instance, TCP port 1433 is used by defau=lt.
> > When you connect to a named instance without a specifying a port, the cl=ient
> > requests a list of the named instances and corresponding ports via UDP p=ort
> > 1434 (this is the SQL Browser service). The client then determines the
> > named instance port.
> > --
> > Hope this helps.
> > Dan Guzman
> > SQL Server MVPhttp://weblogs.sqlteam.com/dang/
> > "Victag" <miketagg...@.gmail.com> wrote in message
> >news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...=
> > >I am using SQL 2005 and have multiple instances installed on multiple
> > > servers. None are on the default port. When I connect to box 01
> > > without specifying the port in the connection string, it connects.
> > > But on box 02, it will only connect to the instance if I specify the
> > > port name. Is this because it will only connect to the default
> > > instance without specifying a port? or is there something else I need
> > > to have setup on box 02 to make this work?
> > > thanks in advance :)- Hide quoted text -
> > - Show quoted text -
> Thanks folks! =A0I have checked and the Browser service is disabled on
> both boxes (event he working one), so I could try turning it on, but I
> would rather explain/understand what the difference is between these
> boxes. =A0I have also confirmed that no ports are blocked at all. =A0Any
> other suggestions... Hide quoted text -
> - Show quoted text -
Thanks again. I have made progress and found that the boxes that are
not working have many client aliases created on them, some of which
appear to be invalid. When I deleted the aliases that did not exist
on the server that is working, it fixed them. So now that I know how
to fix it, I am curious to know how these bad aliases got created
since we did not create them manually.|||"Victag" wrote:
>I am curious to know how these bad aliases got created
> since we did not create them manually.
Did you install Visio? For example Visio installation process create for me
some alias. I have to delete it manually.
Regards,
anxcomp