/build/static/layout/Breadcrumb_cap_w.png

Cannot client push over DirectAccess

I'm running DirectAccess on Server 2012 R2. The endpoints are all Windows 8.1 Enterprise. DirectAccess is working properly - I can ping and RDP into offsite machines. However, when I try to push the SCCM client, nothing happens. The SCCM server can ping the client and it returns the correct IPv6 address. I believe the client-side incoming firewall settings are correct, but I'm not sure because it doesn't seem to be even getting that far. Here's what I see in CCM.log on the server: http://pastebin.com/tdbUeFGZ

It doesn't seem to recognize that the computer is on the network, even though it can ping it. Is this a boundary problem? I have set a boundary with the IPv6 prefix, although I am not sure it's the correct prefix (I'm a total noob with IPv6) - I stole it from the computer properties of another computer with DirectAccess connectivity. To be clear, it's only client push that seems to be failing. Client machines can pick up deployments and everything, but I understand that client-initiated actions are a bit different, and that client push is server-initiated.

Are there any SCCM/DA experts who can help with this?


0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ