Hot answers tagged

4

tcp/53 DNS tcp/88 Kerberos tcp/135 RPC tcp/445 sysvol share tcp/389 LDAP tcp/464 Kerberos password (Max/Unix clients) tcp/636 LDAP SSL (if the domain controllers have/need/use certificates) tcp/1688 KMS (if KMS is used. Not necessarily AD, but the SRV record is in AD and clients need to communicate with the KMS). tcp/3268 LDAP GC tcp/3269 ...


3

The client port number is independent of server running on port 12345. Usually the client when uses connect to any server, the system assigns a random port number for connection on its side. You need not worry about client side port numbers. They will have to configure their IP tables to be able to reach you. If any rule in IP tables on client side that ...


1

The client will need to access Kerberos so that's TCP 88 Then there is the Global Catalogue service so that's TCP 3268 There is the KPassword service TCP 464 (this allows password changes) Then there is LDAP port TCP 389, clients still need to access this to help locate domain controllers. There are also UDP ports for Kerberos (88) and KPassword (464) I am ...


1

As stated in previous reply's, you can't access your server with domain:port because your hosting provider has that port blocked. Before you contact them and ask to allow access to your server's IP from port 8025, test connection with telnet: telnet domain 8025 You should get error that looks like this: telnet: Unable to connect to remote host: Connection ...



Only top voted, non community-wiki answers of a minimum length are eligible