Terminal Services, Port Bound to APIPA, Not accessbile

Home Forums Server Operating Systems Windows Server 2008 / 2008 R2 Terminal Services, Port Bound to APIPA, Not accessbile

Viewing 1 post (of 1 total)
  • Author
    Posts
  • Avatar
    apeckham
    Member
    #156299

    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

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.