SCCM - VPN Client Communication

karthik palani 1,016 Reputation points
2021-09-02T13:37:06.28+00:00

HI All,

I am using SCCM CB 2006 and i am trying to manage VPN client subnets. Seems the ports are all opened but the communication or policy request is not getting updated. I have configured the boundary group with IP range and assigned to primary site. Still it is not showing active in the console. Please suggest. Below are the logs

128752-log1.jpg

128734-log2.jpg

Microsoft Configuration Manager
0 comments
Accepted answer
  1. AlexZhu-MSFT 5,551 Reputation points Microsoft Vendor
    2021-09-03T03:59:37.773+00:00

    Hi,

    Clientlocation.log showing Unable to retrieve AD forest + domain membership may indicate some network/authentication issue, other than sccm itself.

    As yannara suggested, we may check the communication first, by running gpupdate or nltest.

    128890-sccm-communication-01.png

    If it succeeds, we may try the following in a web browser of a client computer to see if the communication with MP is ok

    http://<MPFQDN>/sms_mp/.sms_aut?mplist

    128878-sccm-communication-02.png

    Alex
    If the response is helpful, please click "Accept Answer" and upvote it.

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pavel yannara Mirochnitchenko 11,716 Reputation points MVP
    2021-09-02T13:40:53.62+00:00

    Based on your screens, make first sure that your AD connection via VPN works. What happends if you write gpupdate on a vpn client, will it fail?

    0 comments
  2. karthik palani 1,016 Reputation points
    2021-09-02T13:54:11.35+00:00

    Thanks for your quick reply

    Yes Gpupdate is not happening. Seems all ports are opened like below. Anything missing please advice

    Server Port (DC) Service
    123/UDP W32Time
    135/TCP RPC Endpoint Mapper
    464/TCP/UDP Kerberos password change
    49152-65535/TCP RPC for LSA, SAM, NetLogon ()
    389/TCP/UDP LDAP
    636/TCP LDAP SSL
    3268/TCP LDAP GC
    3269/TCP LDAP GC SSL
    53/TCP/UDP DNS
    49152 -65535/TCP FRS RPC (    )
    88/TCP/UDP Kerberos
    445/TCP SMB (**)
    49152-65535/TCP DFSR RPC (*)

    0 comments
  3. Rahul Jindal [MVP] 9,151 Reputation points MVP
    2021-09-03T04:24:34.513+00:00

    This is clearly a networking issue at this point. You should first get this sorted out with your networks team.

    0 comments
  4. karthik palani 1,016 Reputation points
    2021-09-13T08:11:14.91+00:00

    I will work with Network team

    Thanks for your support

    0 comments