ADO, TCP/IP Ports & Firewalls

#1

Hi everyone,

Ok, basically I am in the process of trying to sort my app out with unicode
support. A good way of doing this would be to use ADO. However, I have been
told by the powers that be, we originally used ADO but had to remove it
because the connection back when using ADO uses a random port from a range.
This isnt acceptable because of customers wanting to secure servers on both
inbound and outbound ports and they are not willing to open up a port range.

Can this be restricted at all, or do I have to abandon the idea of ADO???

Thanks

#2

Hi and thanks for your reply,

If I have read this MS KB ok...

http://support.microsoft.com/kb/269882

"The firewall must be configured to permit port 1433 incoming (or the port
numbers that SQL Server listens to on TCP/IP), and ports 1024 to 65535
outgoing."

This says that ports 1024 to 65535 are required to be opened outbound. So
is that not the case then?

Thanks

"William Vaughn (MVP)" wrote:

Quote:

Consider that SQL Server is used in some of the most secure sites on the
planet. As suggested you can disable automatic port assignments (for each
instance) so you can open a single port or use named pipes.

--
__________________________________________________ ________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com http://betav.com/blog/billva
__________________________________________________ __________________________________________

"Tristan Leask" <TristanLeask (AT) discussions (DOT) microsoft.com> wrote in message
news:368BF98D-8EBA-407B-B8D6-42A69A44B13C (AT) microsoft (DOT) com...
Hi everyone,

Ok, basically I am in the process of trying to sort my app out with
unicode
support. A good way of doing this would be to use ADO. However, I have
been
told by the powers that be, we originally used ADO but had to remove it
because the connection back when using ADO uses a random port from a
range.
This isnt acceptable because of customers wanting to secure servers on
both
inbound and outbound ports and they are not willing to open up a port
range.

Can this be restricted at all, or do I have to abandon the idea of ADO???

Thanks

#3

Hi and thanks for your reply,

If I have read this MS KB ok...

http://support.microsoft.com/kb/269882

"The firewall must be configured to permit port 1433 incoming (or the port
numbers that SQL Server listens to on TCP/IP), and ports 1024 to 65535
outgoing."

This says that ports 1024 to 65535 are required to be opened outbound. So
is that not the case then?

Thanks

"William Vaughn (MVP)" wrote:

Quote:

Consider that SQL Server is used in some of the most secure sites on the
planet. As suggested you can disable automatic port assignments (for each
instance) so you can open a single port or use named pipes.

--
__________________________________________________ ________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com http://betav.com/blog/billva
__________________________________________________ __________________________________________

"Tristan Leask" <TristanLeask (AT) discussions (DOT) microsoft.com> wrote in message
news:368BF98D-8EBA-407B-B8D6-42A69A44B13C (AT) microsoft (DOT) com...
Hi everyone,

Ok, basically I am in the process of trying to sort my app out with
unicode
support. A good way of doing this would be to use ADO. However, I have
been
told by the powers that be, we originally used ADO but had to remove it
because the connection back when using ADO uses a random port from a
range.
This isnt acceptable because of customers wanting to secure servers on
both
inbound and outbound ports and they are not willing to open up a port
range.

Can this be restricted at all, or do I have to abandon the idea of ADO???

Thanks

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

ADO, TCP/IP Ports & Firewalls

microsoft.public.sqlserver.clients microsoft.public.sqlserver.clients

ADO, TCP/IP Ports & Firewalls - 02-26-2009 , 10:48 AM

Re: ADO, TCP/IP Ports & Firewalls - 03-02-2009 , 03:37 AM

Re: ADO, TCP/IP Ports & Firewalls - 03-02-2009 , 03:37 AM