Hard-coded port numbers are a bad idea, particularly if you later find a port conflict with another application and need to change yours. Typically high numbers port are available and I would suggest them but they could be blocked by firewalls. Basically, because most of the system level listener does not implement port sharing its much safe to use the those ports which are not used at all.Tags: Reflection On A EssayDissertation Conscience SujetTerm Paper HeadingUpenn Supplement Essay 2013 HelpResume Letter CoverGoldsmiths Creative WritingSteps For Writing A Research PaperMultiple Integrals Solved ProblemsDissertation Medical Physics
Ports 1024-49151 are the User Ports and are the ones to use for your own protocols.
Ports 49152-65535 are the Dynamic ports and should not be prescribed to a protocol.
Some firewalls allow selective configuration of UDP or TCP ports with the same number, so it's important to know the type of port you're configuring.
For example, NFS can use TCP 2049, UDP 2049, or both.
But be aware that by picking a port number from those unassigned ranges there is no guarantee whatsoever that the port you choose will not be a reserved port in the future.
Tcp Ip Port Assignments Cover Sheet For A Essay
This will avoid headaches in case some other 3rd party you-cannot-touch software is using your port number.
There is no way to guarantee that a port in this range will always be free for your protocol.
Short answer: Avoid anything up to and including 1023, or over 49152, and test the chosen port against services on your network.
That port will be embedded in the config files for the service and the clients that are consuming the service. This is the range from where you SHOULD pick a port for your in-house applications.
Of course any port belonging to one of the unassigned ranges on the published list can be used.