Client Remote Desktop issue with SCCM Server in an Direct Access Environment
Hi,
I have setup an Direct Access Environment (with two adapter configured with NAT 64)with SCCM server 2012. I am unable to take remote to a DirectAccess Client Machine, although it's pinging from my SCCM Server. Normal Ports are enabled on the SCCM server.
Can anyone suggest me what to do..
Thanks,
Roshan
September 4th, 2015 6:29am
Are you sure all the port are open properly?
Take a look at this guide here might help
http://www.concurrency.com/blog/firewall-exceptions-to-allow-sccm-remote-control-for-directaccess-clients/
September 4th, 2015 7:30am
hi,
I have made all the changes mentioned on this link but unable do take the remote.
September 4th, 2015 8:34am
Hi frederick,
I have enabled the following ports.
TCP 3389
IPv6
ICmpv6
and all the file and sharing printers ports on my SCCM, DA Server and DA Client machine. I am able to share files from my DA Server to DA Client And take the remote from DA Server to DA Client.
The Changes done by me on SCCM server is giving Static IPV6 Address based on Default IPv6 address of DA Server and Pinging is working on the SCCM Server to DA Client Machine and the rest of the server is working on static IPv4 address only. But i am unable
to share file and take remote from SCCM Server to DA Client Machine. What can be the solution for this.
Thanks.
roshan
September 11th, 2015 6:50am
Hello, I resolve this issue for this you have to enable the ISATAP on the server from which you want to take remote to DA Client machine.
Follow the link:
http://directaccess.richardhicks.com/2013/06/24/isatap-recommendations-for-directaccess-deployments/
http://blogs.technet.com/b/jasonjones/archive/2013/04/19/limiting-isatap-services-to-directaccess-manage-out-clients.aspx
thanks.
-
Marked as answer by
roshan kr
57 minutes ago
September 12th, 2015 2:48am
Hello, I resolve this issue for this you have to enable the ISATAP on the server from which you want to take remote to DA Client machine.
Follow the link:
http://directaccess.richardhicks.com/2013/06/24/isatap-recommendations-for-directaccess-deployments/
http://blogs.technet.com/b/jasonjones/archive/2013/04/19/limiting-isatap-services-to-directaccess-manage-out-clients.aspx
thanks.
-
Marked as answer by
roshan kr
59 minutes ago
September 12th, 2015 2:48am
Hello, I resolve this issue for this you have to enable the ISATAP on the server from which you want to take remote to DA Client machine.
Follow the link:
http://directaccess.richardhicks.com/2013/06/24/isatap-recommendations-for-directaccess-deployments/
http://blogs.technet.com/b/jasonjones/archive/2013/04/19/limiting-isatap-services-to-directaccess-manage-out-clients.aspx
thanks.
-
Marked as answer by
roshan kr
Saturday, September 12, 2015 6:47 AM
September 12th, 2015 6:47am
Hello, I resolve this issue for this you have to enable the ISATAP on the server from which you want to take remote to DA Client machine.
Follow the link:
http://directaccess.richardhicks.com/2013/06/24/isatap-recommendations-for-directaccess-deployments/
http://blogs.technet.com/b/jasonjones/archive/2013/04/19/limiting-isatap-services-to-directaccess-manage-out-clients.aspx
thanks.
-
Marked as answer by
roshan kr
Saturday, September 12, 2015 6:47 AM
September 12th, 2015 6:47am