Can't hide non-default or non-standard ports for SharePoint

%3CLINGO-SUB%20id%3D%22lingo-sub-1078748%22%20slang%3D%22en-US%22%3ECan't%20hide%20non-default%20or%20non-standard%20ports%20for%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1078748%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20created%20a%20new%20web%20application%20(SharePoint%202019%20on%20Premise)%20on%20port%2044444%20as%20we%20already%20have%20one%20web%20application%20on%20port%2080.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20two%20web%20front%20servers%20and%20I%20am%20using%20F5%20for%20load%20balancing.%20To%20hide%20port%2044444%2C%20I%20used%20DNS%20entry%20(A-NAME%20record)%20and%20created%20AAM%20in%20SharePoint%20Central%20Admin%20to%20hide%20ports.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20browsing%20the%20default%20site%20under%20this%20web%20application%20with%20user%20friendly%20name(http%3A%2F%2Fmblinternal)%2C%20browser%20sends%20response%20back%20with%20port%2044444%20(http%3A%2F%2Fmblinternal%3A44444%2F..)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInternal%20URL%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Public%20URL%3C%2FP%3E%3CP%3Ehttp%3A%2F%2Fmblinternal%3A44444%26nbsp%3B%20%26nbsp%3B%20http%3A%2F%2Fmblinternal%20(default%20zone)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMblinternal%20is%20a%20virtual%20server%20in%20F5%20pointing%20to%20A-NAME%20in%20DNS.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tried%20to%20add%20binding%20in%20IIS%20for%20ports%20with%20host%20header%20as%20mblinternal%20at%20port%2080%20but%20no%20luck.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20appreciate%20if%20you%20could%20point%20me%20to%20the%20right%20direction.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1078748%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%202019%20On%20Premise%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

I have created a new web application (SharePoint 2019 on Premise) on port 44444 as we already have one web application on port 80. 

 

We have two web front servers and I am using F5 for load balancing. To hide port 44444, I used DNS entry (A-NAME record) and created AAM in SharePoint Central Admin to hide ports.

 

On browsing the default site under this web application with user friendly name(http://mblinternal), browser sends response back with port 44444 (http://mblinternal:44444/..)

 

Internal URL                          Public URL

http://mblinternal:44444    http://mblinternal (default zone)

 

Mblinternal is a virtual server in F5 pointing to A-NAME in DNS.

 

I have tried to add binding in IIS for ports with host header as mblinternal at port 80 but no luck. 

I appreciate if you could point me to the right direction.

 

Thanks

1 Reply
We don't have technical support contract with Microsoft to log a case. But I am hoping that Microsoft might have tech support for customer without support contract to log a case by paying a standard fee to get some help to resolve the issue. Does anyone know if Microsoft provide such technical service to customer? Or any other third party consulting company who can help me in this matter.