Adding remote workgroup user into the Domain using Fortisase VPN

[ganesh_karale]

Hi, Can someone please guide whether we will be able to add remote user into the domain who is connected to HO network using Foritsase SPA.

Regards,

Ganesh

[Jean-Philippe_P]

Hello ganesh_karale, 

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible. 

Thanks, 

[Jean-Philippe_P]

Hello,

We are still looking for an answer to your question.

We will come back to you ASAP.

Thanks,

[Jean-Philippe_P]

Hello ganesh_karale,

I found this solution. Can you tell us if it helps, please?

To add a remote workgroup user to a domain while they are connected to the head office (HO) network using FortiSASE SPA, you would generally follow these steps:

1. Ensure Connectivity: Confirm that the remote user is properly connected to the HO network through FortiSASE SPA. This may involve checking VPN settings or any specific configurations required for FortiSASE.
   
   

2. Access Domain Controller: You will need access to the domain controller where the user accounts are managed. This might require remote desktop access or management tools that allow you to interact with the domain controller.
   
   

3. Create User Account:

   • Open the Active Directory Users and Computers (ADUC) console on the domain controller.
   • Right-click on the appropriate organizational unit (OU) where you want to create the user.
   • Select "New" > "User" and fill in the required details (username, password, etc.).
   • Set the user properties as needed, including group memberships and permissions.
     
     

4. Configure Remote Access: If the user needs specific permissions or access to certain resources, ensure that these are configured in their user profile.
   
   

5. Notify the User: Once the account is created, inform the user of their new credentials and any steps they need to take to log into the domain. They may need to restart their device or re-establish their connection to the network.
   
   

6. Testing: Have the user log in to ensure that their account is functioning correctly and that they have access to the necessary resources.

[ganesh_karale]

Hi Jean, no it didn't work.

Actually here we are able to ping to AD server, we have allowed required services but unable to nslookup to the domain name.

Regards,
Ganesh

[Jean-Philippe_P]

Hello ganesh_karale,

I found this answer to your reply:

If you can ping the Active Directory (AD) server but are unable to perform an nslookup to the domain name, it suggests there may be issues with DNS resolution. Here are some steps you can take to troubleshoot and resolve the problem:

1. Check DNS Settings: Ensure that the DNS settings on the remote user's device are correctly configured to point to the DNS server that hosts your Active Directory. This is typically the IP address of your domain controller.
   
   

2. Test DNS Resolution:

   • Use the command line to perform a direct query to the DNS server. For example:

     nslookup <domain_name> <dns_server_ip>
     

   • This will help determine if the DNS server itself is reachable and functioning correctly.
     
     

3. Verify DNS Service: Ensure that the DNS service is running on the domain controller. You can check this by logging into the domain controller and using the services.msc tool to confirm that the DNS Server service is active.
   
   

4. Firewall Settings: Verify that there are no firewall rules blocking DNS traffic (port 53) between the remote user and the DNS server. This includes checking both local firewalls on the user's device and any network firewalls.
   
   

5. Hosts File: As a temporary workaround, you can add an entry for the domain in the hosts file of the remote user's device. This is located at C:\Windows\System32\drivers\etc\hosts on Windows. However, this is not a long-term solution.
   
   

6. Check Network Configuration: Ensure that the FortiSASE configuration allows for DNS queries to be forwarded properly. Check any policies or settings that may be affecting DNS traffic.
   
   

7. Consult Logs: Review the logs on both the client device and the domain controller for any errors or messages that might indicate where the problem lies.
   
   

8. DNS Cache: Clear the DNS cache on the remote user's device using the command:
   
   

   ipconfig /flushdns
   

If these steps do not resolve the issue, you may want to consult with your network administrator or IT support team for further assistance, as they may have more specific insights into your network configuration and policies.