Windows Server 2012 Direct Access clients connecting but not showing in the monitor

Unanswered Windows Server 2012 Direct Access clients connecting but not showing in the monitor

  • Monday, November 12, 2012 10:26 AM
     
     

    I have set up direct access on my network, the windows 7 client connect and can browse the network shares etc, but I have two issues.

    1. The clients do not appear in the monitoring section not sure why?

    2. I have to disable the firewall to get them to be able browse the network, obviously some ports need opening up buit which?

All Replies

  • Friday, December 07, 2012 12:17 PM
     
     

    Hi There

    I have also setup Direct Access only with Windows 8 at the moment.

    The Remote Client Status section is not working for me either.

    With regards to firewalls you will need to open ports between your DA server and your file servers depending on what file shares you are using ports will vary, but SMB (standard windows file sharing) is port 445, that should allow browsing shares, bear in mind DNS resolution also needs to be working.

    Thanks

  • Thursday, December 13, 2012 2:02 PM
     
     

    We also have the same problem. Everything appears to work great, no problems at all - connectivity working as it should both internally and externally etc. Although like you've said, the Remote Client status information page never shows any clients connected - at any point.

    We are running Windows 7 clients.

    Would really like to get the statuses to show up correctly as staff are quite eager to get their hands on such a great feature!



    • Edited by KyleWhite21 Thursday, December 13, 2012 2:03 PM
    • Edited by KyleWhite21 Thursday, December 13, 2012 2:04 PM
    •  
  • Thursday, December 13, 2012 2:57 PM
     
     
    same here. any insight?
  • Thursday, January 31, 2013 7:01 AM
     
     

    Same here for me... Direct Access for Win7 clients are working but nothing is showing up in the monitoring section.

    I also have an issue where the ISATAP router on the DA server is not working, this despite already having a working isatap.domain.local DNS record. Any ideas?

    PS C:\Windows\system32> Get-RemoteAccessHealth

    High Availability    localhost            Disabled        1/29/2013 3:41:27 PM
    Isatap               localhost            Disabled        1/29/2013 3:41:27 PM
    Vpn Connectivity     localhost            Disabled        1/29/2013 3:41:27 PM

  • Wednesday, May 15, 2013 6:34 PM
     
     
    same here cannot see connected client on dashboard....dont know why!