Announcement

Collapse
No announcement yet.

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

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

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

    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

  • #2
    If there's no process or service listening on that port then telnet can't connect to that port.

    Comment


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

      Comment


      • #4
        can you telnet from serverA to itself on port 389?
        what service are you expecting to be on port 389?
        Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

        Comment

        Working...
        X