What ports does SQLMail use to access MS Exchange Server?? We have SQL 7 running on a seperate non-trusted domain(within the same DMZ) from where Exchange Server exists. The only trust we want between the 2 domains is the SQLMail functionality for the DBA's and Administrators to use. I am aware that MS Exchange uses 110 port for POP3 and port 25 for SMTP. Does this apply to SQLMail as well? Thanks in advance for your support.
hi every on am searching for a file which contains information about the instance in my sql server and the ports that this instances are running on ,am sure that there is a file like this but i cant find it please if u know it answer me ,,, and thanks alot for ur time//
Does anyone know what ports are required to be open (non-NT). We are placing the SQL-Server behind a UNIX firewall, and want to minimize the ports open.
Hello,How to determine, which ports do MS SQL Server instances listen to?I want to conect to sql server using PHP and I need to know exact portnumber. I suspect that my SQL (msde) server instances don't listen ondefault 1433 :]--Stefan
I'll have about 5 db's from an instance(server1instance1) mirrored to another server(server2/instance1). Do all of these db's have to have endpoints configured with different ports? I hope I'm clear on my question. Do I have to create a different endpoint for every db or can use the same endpoint? Thank you
Using SQL Configuration Manager, i have set my local instance to use TCP Dynamic Ports by setting the value under IPAll to be 0 (the value TCP Port is blank). However, when i start up the server this value gets set to a specific port. ie Before startup TCP Dynamic Ports = 0, After startup TCP Dynamic Ports = 2832. This value persists throughout SQL Server restarts.
Is this behaviour correct as I would have expected this value to stay 0?
I am using SQL Standard, SP2. SQL Browser is running.
I have two instances of SQl 2005 running on a server. One I'm going to allow outside remote access to. But I don't want to do it on the default port. though I have it allowing remote and that seems to be working. I can seem to find where to change the default listening port.
and I scimmed the help and topics I saw. But didn't see one relevant to this question.
When a ReportViewer control is used to access a report on a remote SQL Server database, on what ports does the communcation occur? Does the control communicate on on the SQL Server ports of 1433 and 1434 or does it communcate as a web service on port 80 (or 443 for HTPPS)?
If I am doing an Index Server query from SQL, such as:SELECTQ.*FROMOPENQUERY(FTIndexPM, ''SELECT path, characterization, rank, hitcountFROM SCOPE('DEEP TRAVERSAL OF .....can anyone tell me which TCP/UDP ports will be used between the SQLServer and the Index server if the Index Server is on another machine?I'm doing the query from SQL so that I can join the results with atable in the database and am not interested in doing the Index queryfrom the app server. I haven't been able to find any info on the netfor which firewall ports are used for this.
I was reading that Net-Library Encryption is an SSL utility. Does thatmean the traffic uses TCP port 443 or does it still use TCP 1433?Thanks.http://msdn.microsoft.com/library/d..._ar_cs_6fu6.asp
I am new to the forum and would like to have a question answered. I want to to install Sql Server Express with advanced services but also want to have IIS installed as well. My question is, how do I install IIS without it opening Port 45? When I installed it, it would not let me finish installation without letting it act as a server. Is there any work around to solve this problem that any of you have managed to use?
With SSL, is all traffic from the client to the database on port 443 ? Or are other ports needed ?
With Windows Certificate Management Snap-in, a request for a certificate assumes that there is a local Certificate Authority. I don't have one and it is my understanding that I should buy a third party certificate to avoid a man in the middle attack. With IIS there is a certificate request process. Is there something similar I should use with SQL ?
When multiple instances of SQL 2005 are installed on a cluster or standalone server, is it best to have each instance configured to listen on a different port or will one port for all do? We don't use port 1433 and the port we do use is blocked at the firewall. I'd like to standardize on one port for all instances but I'm not sure of the ramifications. Any thoughts?
My SQL Server is a shared account at MaximumASP.com a client just deployed my .NET application on GoDaddy.com and they have all there ports blocked and my app cannot connect to the SQL Server. Using "Network Library =dbmssocn" in the connection string did not help and GoDaddy will not help. MY QUESTION IS: how can I get my .NET app to connect to the SQL Server? web service? This is the first time I have run into this problem. There seems like there has to be some way. THANKS IN ADVANCE!
Note: but even the connection string "serverBserverA,2040" also connects to Instance "serverB", when i try to connect from SSMS, In SSMS it shows the wrong instance name like, "serverBserverB", but it actually connects to Instance "serverA"
i.what is the reason behind this? ii.Is there any way to avoid this connection, by performing server property changes, if any ?
We have an internal sql 2000 server that acts as the database backend for our Internet presence. I believe that the sql server can be accessed because of a firewall "exception" (?) that allows the external web server to talk to the sql server using a specific IP address and port (namely that of the sql server.)
Now we need to install a sql 2005 instance on the same box which needs to act as an Internet backend. The sql browser service will resolve all client requests to the default or named instance. But I read that the sql browser service assigns a "dynamic" port to the Instance! If that is the case, it's unlikely that, unless the firewall has all ports open for outgoing traffic, that the sql instance will be able to communicate with the web server.
My conclusion:
Leave the default instance (sql 2000) port at its current value; assign the named instance an unused port; Make sure the sql browser is running on the box! Tell the firewall guys to make an exception for the new port.
I have an existing 2012 default SQL Express. It's set up on a VPS managed by a third party. I have an administrator account on this 2012 Windows server. I'm not much of a sysadmin or a DBA but I get around. ;)
I've installed a new NAMED instance on this VPS and can not connect to it with client tools (SSMS). If I remote in, I can connect this way.
What steps might a seasoned DBA expect to make when getting a new named instance ready for the world.
Assign a port? Check the port?
Open the firewall for the port?
Will this new named instance listen on a different port than the previously installed SQL Express instance?