• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 904
  • Last Modified:

Connecting a Active Directory Domain Controller on a specific port

Heyas,

One of the PC on the network can't connect to the Windows DC it can ping with no issues, but when I try telnet through to it on the port 389 the PC is rejected. This is the only PC on the network that is doing this I have tried rejoining it to the domain with no success.

Any other ideas, bare in the mind I am a novice with AD.
0
Zack
Asked:
Zack
  • 4
  • 3
  • 3
1 Solution
 
SandeshdubeyCommented:
Disable the window firewall and antivrus if any and reboot the cleint machine and check.If any thirdy part security application is installed then disable the same too.
0
 
MaheshArchitectCommented:
can you please if PC is able to telnet itself on any well known port ?
For example, TCP 135, 445
If not,
Please disable firewall and antivirus software if any to check if installed antivirus is blocking him from communicating with DC ?
Also check how many network cards does this PC has ?
If you found multiple, then please disable all unnecessary cards and check ?
0
 
ZackGeneral IT Goto GuyAuthor Commented:
Heyas,

Done all of these, anything on the DC I should check.

Thank you.
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
SandeshdubeyCommented:
Disable all the third part service i.e try clean boot and check.
0
 
ZackGeneral IT Goto GuyAuthor Commented:
Nothing again, update I can't access the PC itself via telnet from the DC. Does this provide any further insight?
0
 
MaheshArchitectCommented:
Please try to telnet PC from same PC only instead of DC and check if its able to telnet itself
Please download PortQueryUI tool from microsoft and check if you are able  to telnet domain controller
Thnaks
0
 
ZackGeneral IT Goto GuyAuthor Commented:
What do you mean? "Please try to telnet PC from same PC only instead of DC and check if its able to telnet itself."

Thank you.
0
 
SandeshdubeyCommented:
You can also use wireshark tool to check the same.
0
 
MaheshArchitectCommented:
You need to check if PC is responding to telnet protocol
Please logon to affected PC and open up command prompt and try "telnet ownIP 135"
If its unable to telnet itself, then there might be your problem root cause.
If this is win7 machine then you may need to install telnet feature first.
Hope that helps
Thanks
0
 
ZackGeneral IT Goto GuyAuthor Commented:
Thank you.
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

  • 4
  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now