locked
Cant use powershell remotely to 1 system RRS feed

  • Question

  • Hello,

    We have got an issue with using remote powershell to one specific Domain Controller.

    Our setup:

    S1 in location A   (subnet A)

    DC1 in location A (subnet A)

    DC2 in location B  (subnet B using a Wan link through a 3rd party DC)

    DC1 and DC2 are exact copies in configuration etc.


    We logon to S1 to manager our servers including above DC`s, when we use the command:

     Get-ADComputer –identity DC2 –Server DC2

    we get the following error:

    Get-ADComputer : Unable to contact the server. This may be because this server does not exist, it is currently down, or
     it does not have the Active Directory Web Services running.

    When we perform this command like this:

    Get-ADComputer –identity DC2 –Server DC1

    It works

    When we perform 

    Get-ADComputer –identity DC2 –Server DC2  From powershell logged on to DC2 it works as well, as well as above command using DC1

    We ran Powershell elevated with our admin as well as domain admin account and it still does not work, same thing happens when we start a session using Enter-pssession

    On DC2 we checked the logs and could not find anything that can be connected to this issue.

    ADWS and WRM are both running, we have checked the account rights and they are properly set as well.

    Local firewall is not turned on.

    We have tested the following as well from S1:

    Telnet using ports 9389, 5985 & 5986 are all working

    We have requested our networks team to see if any traffic is being dropped, they checked the logs and they do see the traffic being allowed.

    We have requested the 3rd party as well to check network traffic and they too see the traffic being routed from source to destination.

    Net stat shows DC2 is listening to the above ports

    Ran Get-pssessionconfiguration on both DC`s and this showed that both configurations are identical.

    Tried the command from another server (print server) and from that server it works as well.

    All systems are registerd in the same Domain and are all AD members.

    Anyone have an idea what we are missing?
    Thanks very much in advance.

    Tuesday, October 16, 2018 12:20 PM

Answers

  • Hi,

    Thanks for your question.

    I agree with jrv.

    Besides, I would also suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue. In addition, if the issue has been proved as system flaw, the consulting fee would be refund. You may find phone number for your region accordingly from the link below: 

    Global Customer Service phone numbers  

    https://support.microsoft.com/en-us/gp/customer-service-phone-numbers 

    Best Regards,

    Lee

      

    Just do it.

    • Proposed as answer by jrv Wednesday, October 17, 2018 3:20 AM
    • Marked as answer by B Wolf Wednesday, October 17, 2018 6:31 AM
    Wednesday, October 17, 2018 3:16 AM

All replies

  • This is not a break/fix forum.  You have network issues and need to contact a networking specialist or consultant to help you with this.  You can also contact MS support for assistance.

    The issue is not caused by scripting and not caused by PowerShell. Contact MS support.


    \_(ツ)_/

    Tuesday, October 16, 2018 12:44 PM
  • Hi,

    Thanks for your question.

    I agree with jrv.

    Besides, I would also suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue. In addition, if the issue has been proved as system flaw, the consulting fee would be refund. You may find phone number for your region accordingly from the link below: 

    Global Customer Service phone numbers  

    https://support.microsoft.com/en-us/gp/customer-service-phone-numbers 

    Best Regards,

    Lee

      

    Just do it.

    • Proposed as answer by jrv Wednesday, October 17, 2018 3:20 AM
    • Marked as answer by B Wolf Wednesday, October 17, 2018 6:31 AM
    Wednesday, October 17, 2018 3:16 AM