Connect to SQL Server through an cable modem client

Hi, I'm connecting some clients via Internet to a named instance of SQLServer
(port 1433). All the clients conected to internet via DSL works just great,
but all the clients connected to internet via an cable ISP, just can't find
the server.
I saw some of the cable ISPs block the 1433 and 1434 ports...it's possible
the cable users connect to my sql server using a different port, and the dsl
users still using the 1433? ... or what collateral damage could happen if I
just change the current port on the remote server?
If you change the port on which the SQL instance is listening, just make sure
that you also change the port to which the clients are configured to connect.
I'm assuming that you are specifying the port number in your connection
string.
Linchi
"Ruben" wrote:

> Hi, I'm connecting some clients via Internet to a named instance of SQLServer
> (port 1433). All the clients conected to internet via DSL works just great,
> but all the clients connected to internet via an cable ISP, just can't find
> the server.
> I saw some of the cable ISPs block the 1433 and 1434 ports...it's possible
> the cable users connect to my sql server using a different port, and the dsl
> users still using the 1433? ... or what collateral damage could happen if I
> just change the current port on the remote server?
|||Hi Linchi, I'm not specifying the port in the connection string, I'm setting
a Server Alias (with the client network utility) and the port is set to
determine it dinamically ... and reading your post I assume there isn't any
problem if I change the port at the main server, right?
"Linchi Shea" wrote:
[vbcol=seagreen]
> If you change the port on which the SQL instance is listening, just make sure
> that you also change the port to which the clients are configured to connect.
> I'm assuming that you are specifying the port number in your connection
> string.
> Linchi
> "Ruben" wrote:
|||You can change the port that the SQL instance is listening on, or you can
specify the port after the server name (or the IP address) after a comma. You
can also specify the port number when you specify your alias. If the UDP port
1434 is blocked, you may not have a choice but to specify the port number on
the connection string. Note that when the SQL instance is the deafult
instance, the default port of 1433 will be tried evne if you don't specify a
port number.
Linchi
"Ruben" wrote:
[vbcol=seagreen]
> Hi Linchi, I'm not specifying the port in the connection string, I'm setting
> a Server Alias (with the client network utility) and the port is set to
> determine it dinamically ... and reading your post I assume there isn't any
> problem if I change the port at the main server, right?
> "Linchi Shea" wrote: