Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Not able to use Static RPC Port number 49152 and 49154 on Domain Controllers

$
0
0

Hi

I just want to confirm that on Windows Server 2008 R2 (or later) Domain Controllers, whether we can use Port Number 49152 and 49154 as Static ports for NTDS and Netlogon or not ?

We have set these Ports for NTDS and Netlogon (KB224196) but they won't be used. Seems like these Port numbers have been hard coded for other Services - WinInit.exe is using 49152 and Multiple Services for49154, as depicted below.

Services associated registrations/entries in EPMAP on 2008 R2 Domain Controller looks like:

UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncacn_ip_tcp:127.0.0.1[49152]



UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncacn_ip_tcp:127.0.0.1[49154]

UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncacn_ip_tcp:127.0.0.1[49154]

UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API
ncacn_ip_tcp:127.0.0.1[49154]

UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncacn_ip_tcp:127.0.0.1[49154]

UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_ip_tcp:127.0.0.1[49154]

UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_ip_tcp:127.0.0.1[49154]

UUID: 8c7daf44-b6dc-11d1-9a4c-0020af6e7c57
ncacn_ip_tcp:127.0.0.1[49154]

So if we really do have some these Services hard coded to use 49152 and 49154, please provide  me some URL stating so.

In Windows Server 2003, we didn't have any issues using these Static Ports on Domain Controllers but not anymore.

Please assist


OS ... VirTuaLiZaTioN ... MaxiMuS ... Fair, Good, Better, Best




Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>