locked
Connecting to Windows Server 2016 via RDP RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello!

    I have a testing domain environment that consists of several multi-homed testing servers: each of them has at least two network adapters - one for connecting to the test domain (TestEnterprise.com) and the second - for connecting to those servers from the productional network via RDP:

     I can connect to 10.10.10.11 from 10.10.10.0/24 subnet  via RDP while this server is connected to the TestEnterprise.com by means of its 20.1.1.16 network adapter - so far so good - for WinServer 2012R2.

    Today I installed WinServer 2016 onto one of these servers (with the IPs depicted above) and can no longer connect via RDP to the management adapter (10.10.10.11),  I can only connect to its "domain-based" IP (20.1.1.16) - from other members of TestEnterprise domain (from 20.1.1.0/24 subnet): RDP client says "The password is incorrect", no events get registered in the security log inspite of this audit configuration:

    Q1: What can prevent connecting to the IP that is from the non-domain subnet (firewall is completely turned off for all profiles) ?

    Q2: Why Windows Server 2016 does not register unsuccessfull connection attempt?

    P.S. I failed to find a forum for Windows Server 2016 (not Preview) - does it exist at all?

    Thank you in advance,

    Michael



    • Edited by MF47 Monday, November 14, 2016 1:55 PM
    Monday, November 14, 2016 1:53 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    What is the output of ipconfig /all for the Windows Server 2016 server?  Can it ping anything on the 10 network?

    . : | : . : | : . tim

    • Marked as answer by MF47 Wednesday, November 16, 2016 10:10 AM
    Monday, November 14, 2016 10:19 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    What is the output of ipconfig /all for the Windows Server 2016 server?  Can it ping anything on the 10 network?

    . : | : . : | : . tim

    • Marked as answer by MF47 Wednesday, November 16, 2016 10:10 AM
    Monday, November 14, 2016 10:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    ...awfully sorry... should have been using 20.1.1.6 instead of 20.1.1.16 - thank you very much, Tim, for ipconfig!

    Regards,

    Michae


    • Edited by MF47 Tuesday, November 15, 2016 8:06 AM
    Tuesday, November 15, 2016 8:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You're welcome.  ipconfig is generally the first thing to look at for any networking issue.

    . : | : . : | : . tim

    Tuesday, November 15, 2016 2:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    "ipconfig is generally the first thing to look at for any networking issue." - yes, of course, but I thought looking at ipconfig's output would be excessive given that I was looking at TCP/IP Properties window at that moment :(

    What about the second question - is there any Windows Server 2016 (not preview) forum on technet?

    Wednesday, November 16, 2016 10:15 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    As far as I know, there is no Windows Server 2016 forum temporary.

    For the problem, you could try to post network forum below.

    https://social.technet.microsoft.com/forums/en-us/home?forum=winserveripamdhcpdns

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverNIS

    Best Regards,

    Jay

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, November 16, 2016 10:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you for the help, Jay!
    Wednesday, November 16, 2016 11:34 AM