RE: ADO, TCP/IP Ports & Firewalls
- From: Mohit K. Gupta <mohitkgupta@xxxxxxx>
- Date: Thu, 26 Feb 2009 08:52:01 -0800
Random port?
For SQL Server the port is 1433, yes it can be different if the server the
instance resides on has multiple instances. In which case on the server side
you can force port configurations.
Far as I know you don't have to worry about ports from client side ... I
have used ADO for many years. And only port I ever gotten anyone to open is
1433.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCITP: Database Administrator
MCTS: SQL Server 2005
http://sqllearnings.blogspot.com/
"Tristan Leask" wrote:
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
- References:
- ADO, TCP/IP Ports & Firewalls
- From: Tristan Leask
- ADO, TCP/IP Ports & Firewalls
- Prev by Date: ADO, TCP/IP Ports & Firewalls
- Previous by thread: ADO, TCP/IP Ports & Firewalls
- Index(es):
Relevant Pages
|