unable to telnet port 389 on a newly installed windows 2012 server

Home Forums Server Operating Systems Windows Server 2012 / 2012 R2 unable to telnet port 389 on a newly installed windows 2012 server

This topic contains 3 replies, has 4 voices, and was last updated by  Dext 11 months, 3 weeks ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts

  • lvaibhavt
    Member
    #167348

    Hi All,

    In my home lab on VMware workstation, I’ve deployed two new servers 2012. Server A & B

    On both the servers I have enabled telnet client. There is no application running on them. When I try to telnet port 389 it does not connect.

    These are datacenter edition trials. not core editions. Windows firewall is disabled and even its service.

    I am unable to telnet port 389 from Server A to B and vice versa

    Will telnet only go through if there is an application which is using port 389 or if there is no application installed then too port 389 should connect (as the ports are open) ?

    Thanks


    joeqwerty
    Moderator
    #304613

    If there’s no process or service listening on that port then telnet can’t connect to that port.


    Dext
    Member
    #379158

    Netstat -a will tell you whats listening if its within the output you should be able to telnet if its not then you wont.


    tehcamel
    Moderator
    #360141

    can you telnet from serverA to itself on port 389?
    what service are you expecting to be on port 389?

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.