

I realized I messed up when I went to rejoin the domain I added a "LocalAdmin" - but didn't set the type to admin. I had to remove the machine from the domain Before doing that. I decided to let MS install the 22H2 build.

So, first interaction here, so if more is needed, or if I am doing something wrong, I am open to suggestions or guidance with forum ettiquette. Windows Server 2022 not shutting down Windows.The file will be placed inside the same folder: C:\Program Files\Fortinet\FortiClient\Įdit and search for network and add the IP Address (as I said before) for your connection.Īfter that just go to Forticlient click in the lock to unlock the configurations, and in settings restore de configuration and connect, it will work just fine.Īny questions let me know I´ll be happy to help. The command to export settings.xml from Forticlient is:įirst of all, configure your connection normally and do Inside of C:\Program Files\Fortinet\FortiClient\ (u need to be an administrator to do that) execute the command:įcconfig -p11111111 -f settings.xml -m all -o export exports (1111111 is your password) I don't know why but as soon the connection is established, I searched in routes and there is nothing about the host 1.1.1.1.

To import the file, the file needs to have the same name e needs to be in the same folder ( C:\Program Files\Fortinet\FortiClient\) Imported it again and boom! worked just fine, I was able to access my email get the token e to fill it up to establish the connection, and another benefit of it is I just need to pass the settings.xml password and the file itself to the client and I don't need to pass the pre-shared key, the client just needs to import the configuration to Fortclient and he will be ready to connect. What I´ve done was put some IP instead of leaving it with 0.0.0.0, like 1.1.1.1, the configuration looks like this: I´ve found a workaround, so I don't know why but when a exported the settings.xml of the Forticlient I noticed there are network configurations on it with the address 0.0.0.0, and I think when we try to connect using Forticlient it binds this address who is the same as the machine default GW.
