Re: Access To SQL Server Behind Firewall
From: Ulysses (ubrown_at_manh.com)
Date: 06/20/03
- Next message: Andrew J. Kelly: "Re: sql server connections"
- Previous message: bryn: "Re: builtin\administrators in the db_owner role"
- In reply to: Mandar Naik[MSFT]: "Re: Access To SQL Server Behind Firewall"
- Next in thread: Bronek Kozicki: "Re: Access To SQL Server Behind Firewall"
- Reply: Bronek Kozicki: "Re: Access To SQL Server Behind Firewall"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 20 Jun 2003 05:03:31 -0700
Using the Client Network Utility on the SQL Client to
configure the client side communication ports that it will
use to contact SQL Server only actually configures the
destination port for the client side connection. (i.e.,
you tell the client what port the "listening" SQL Server
is on). The Client Network Utility does not configure the
source port that the client will use to initiate the three-
way handshake. Thus the client can initiate communication
on a source port that is different than the destination
port.
I had previously read the document that is referred to in
the reply from Mandar, and it states that the "Client
Source Port In Use Is Random". I was hoping that someone
listening in this group will be able to demonstrate how to
force the client source port to communicate only through a
particular specified port.
>-----Original Message-----
>You can use the Server Network Utility to configure the
Server to Listen on
>a particular port. Also, you can use the Client Network
Utility on the
>Client to configure the client side communication ports
that it will use to
>contact SQL Server.
>
>That being said, please refer to the link for more
details on what ports SQL
>Server requires for connection through a firewall,
>
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;287932
>
>
>
>--
>Regards,
>Mandar Naik
>
>
>This posting is provided AS IS with no warranties, and
confers no rights.
>"Ulysses" <ubrown@manh.com> wrote in message
>news:07f801c336c7$7efcbbb0$a101280a@phx.gbl...
>> Is there anyway to force the SQL Server client source
>> connection to use a particular port when accessing a SQL
>> Server that is listening on a certain non-default port
>> inside a locked down firewall.
>> We have a firewall with all ports blocked to incoming
>> traffic from the outside except port 5403 which is the
>> port we have our SQL Server inside the firewall
listening
>> on. We have a SQL Server Client outside the firewall
that
>> needs to access that inside SQL Server. In order to do
>> this we need to have the client connect on a
>> specific "source" port. We want to assign the client
>> connection to "source" port 5403.
>> We have not been able to accomplish this using Client
>> Network Utilities and the other available tools. Is
there
>> anyone out there that knows how to accomplish this?
>
>
>.
>
- Next message: Andrew J. Kelly: "Re: sql server connections"
- Previous message: bryn: "Re: builtin\administrators in the db_owner role"
- In reply to: Mandar Naik[MSFT]: "Re: Access To SQL Server Behind Firewall"
- Next in thread: Bronek Kozicki: "Re: Access To SQL Server Behind Firewall"
- Reply: Bronek Kozicki: "Re: Access To SQL Server Behind Firewall"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
