Announcement

Collapse
No announcement yet.

Terminal Services, Port Bound to APIPA, Not accessbile

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

  • Terminal Services, Port Bound to APIPA, Not accessbile

    Good Afternoon,

    I have an issue terminal services that has stumped me.

    We recently deployed two domain controllers, one member and one primary.

    We are currently unable to access Term Services at the IP addresses, even tho the bindings are correct (started out multi homed, deactivated one of the ports / set the proper bindings). When I run a 'netstat -anp -tcp' I see the service listening on the proper port, 3389, but it is bound to an automatic private IP address and we are unable to locate that APIPA - anywhere...

    Has anyone experienced this before? The Google has not found a single article regarding what I've described.

    Thanks
    AP

  • #2
    Re: Terminal Services, Port Bound to APIPA, Not accessbile

    restart the service?
    beter yet.. disable all the other nics, restart the server?
    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