SQL Server is listening on... what port

exec master..xp_readerrorlog 0, 1, 'Server is listening on'

is showing

"
Server is listening on [ 'any' <ipv6> 1433].
Server is listening on [ 'any' <ipv4> 1433].
Server is listening on [ ::1 <ipv6> 62098].
Server is listening on [ 127.0.0.1 <ipv4> 62098].
"

as the result set..

how could 2 ports be listening @ same time?

i tried another server and below is what i got there:

Server is listening on [ 'any' <ipv6> 1433].
Server is listening on [ 'any' <ipv4> 1433].
Server is listening on [ ::1 <ipv6> 1434].
Server is listening on [ 127.0.0.1 <ipv4> 1434].
LVL 5
25112Asked:
Who is Participating?
 
Steve WalesConnect With a Mentor Senior Database AdministratorCommented:
Have a read of this article:

http://msdn.microsoft.com/en-us/library/ms175483%28v=sql.90%29.aspx

Looks like by default, 1433 is the port that the listener is using (by default) for incoming connections.

1434 appears to be used by the SQL Server Browser Service (again, by default):
http://msdn.microsoft.com/en-us/library/ms181087%28v=sql.90%29.aspx

The relevant passage from the first link is:
The network administrator should configure the firewall to forward communication to SQL Server for the IP address and TCP port that the instance of the Database Engine is listening on (either TCP port 1433 for a default instance, or the TCP port you configured for a named instance). Also, because Microsoft SQL Server 2005 uses UDP port 1434 to establish communications links from applications, have the network administrator configure the firewall to forward requests for UDP port 1434 on the same IP address. For more information about UDP port 1434, see SQL Server Browser Service.
0
 
ProjectChampionConnect With a Mentor Commented:
As for 'How' they are different ports on different IPs; it's perfectly possible to setup SQL Server to lsiten to different ports on different IPs. As to 'Why' your server has been setup like that my guess is as good as yours.

you can query sys.dm_exec_connections to find out which port you are using in the context of your current connection (e.g. select client_net_address from sys.dm_exec_connections where session_id=@@spid).

Are you experiencing any problem with server?
0
 
25112Author Commented:
did you mean
select local_tcp_port from sys.dm_exec_connections where session_id=@@spid ?

no problems right now.. but need to install another sql instance and need to make sure i won't be installing in another man's ground!

when you run in your environment
exec master..xp_readerrorlog 0, 1, 'Server is listening on'
do you get only one port that you assigned?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.