Forum Discussion

Oussama_Rahmani90's avatar
Oussama_Rahmani90
Copper Contributor
Aug 09, 2023

Domain connectivity issues

Hello , 

 

I have a User who is attempting to log in into Windows,the User account is Active in Active directory (AD) ,He Has successfully logged into the VPN, but He encountered an error Message indicating He is  not connected to the available Domain and need to connect to their organization tobe added to the domain.

Could anyone offer assistance with this issue ? 

 

Thank you 

 

3 Replies

  • Hi Oussama,

    My questions:
    - Please provide the exact error message.
    - Only one remote user experiences this issue?

    Action plan:
    - Make sure that fast start-up has been disabled on the user's machine.
    - Restart the user's machine.
    - Establishing the VPN-connection.

    - Can one of the domain controller's IP-addresses be pinged successfully from the user's machine?
    - Can the domain (e.g. domain.local) successfully be pinged from the user's machine?

    Thanks!
    • Oussama_Rahmani90's avatar
      Oussama_Rahmani90
      Copper Contributor
      Thanks for your swift reply.

      The error message is you can't logged with these information, because your domain is not available, be sure you're connected with your organization Network. Yeap only for 1 remote User.
      The fast startup has been disabled on User Machine.


      No the Domain controller Ip adress could be not successfully pinged also the user can't ping the Domain Ip Adress.

      Thanks in advance.
      • MathieuVandenHautte's avatar
        MathieuVandenHautte
        Iron Contributor

        Hi Oussama,

        Thank you for the info.

        What is the exact output of the failed pings?

        On the user's device:
        - Uninstall the VPN client + reboot + reinstall the VPN client + install the VPN certificate (reinstalling the client will cleanup the device's internal route table)
        - Initiate the tunnel
        - Try pinging the domain controller's IP-address

        - Try pinging the domain controller's hostname

        - Check the IPv4 route table for the subnet of the domain controller: Command Prompt > route print -4

        On the firewall (VPN server):
        - Check the configured user and device permissions
        - Check the configured firewall rules
        - Check the firewall-logs

Resources