External Connections - Port number?

Question

Post reply

External Connections - Port number?

amy26

SSCrazy Eights

Points: 8926
More actions
November 2, 2017 at 2:06 pm

#326037

Hi, I dunno if this is a dumb question or not but my SQL Server has the Oracle client installed on it so I can make Linked Server connections to external Oracle databases.
The tnsnames file of course has the host name and the port. This "port" is the external systems port right?
What port does my oracle client go out from my machine on? Is it the port in the tnsnames file?
Thanks!

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Joe Torre SSChampion Points: 10248 More actions · Answer 1

The port in a TNSNAMES.ORA listing is the port the Oracle Listener is listening on.

amy26 SSCrazy Eights Points: 8926 More actions · Answer 2

Right ok - exactly what I thought. How do I know what port my connection is going out on? Does it matter?

My network admins are trying to tell me I have to give them the port numbers that I need to connect with but I'm trying to tell them the ports are on he otherside and not our side.

Joe Torre SSChampion Points: 10248 More actions · Answer 3

I don't know if this helps:
Managing Oracle Database Port Numbers

Sue_H SSC Guru Points: 90860 More actions · Answer 4

amy26 - Thursday, November 2, 2017 6:57 PM
Right ok - exactly what I thought. How do I know what port my connection is going out on? Does it matter? My network admins are trying to tell me I have to give them the port numbers that I need to connect with but I'm trying to tell them the ports are on he otherside and not our side.

Usually you just need to open up the Oracle listening port to allow inbound connections (or clients access) to that Oracle port.
You might be asking the same thing as discussed in this thread - different scenario, same concept:
Outbound port to open

Sue

crow1969 Hall of Fame Points: 3001 More actions · Answer 5

For most client-server applications, the server's port is fixed (such as port 80 for web servers, or by default 1433 for SQL Server). The port that the client picks is usually a random port above 32000. A TCP/IP connection is defined by 4 attributes. Client IP, Destination IP, client port, and destination port. Three of these are fixed for any one client, so the fourth one (client port) is flexible to allow you to connect to a server from the same client multiple times. Does this help?