synaesthesia Posted October 6, 2015 Posted October 6, 2015 Howdy, Trying to set up remote access to SIMS via our ISP's VPN. All works well, however to do that the connect.ini files on the client need pointing to the server's IP address rather than the DNS name. That works well, inside school and out, however Solus3 tries to be clever and constantly replaces connect.ini with what it thinks is correct. Is there a way to override SOLUS3's behaviour with this? I can send out connect.ini via group policy with ease however would rather SOLUS3 did it. Any help much appreciated.
Jawloms Posted October 6, 2015 Posted October 6, 2015 Can't you just make the connect.ini file read only?
Steve21 Posted October 6, 2015 Posted October 6, 2015 Override for just the remote server or all? In solus there's an option for what connect ini to deploy if you want a different one you can change what it's pointing to etc, but then it'll deploy for all machines Steve
synaesthesia Posted October 6, 2015 Author Posted October 6, 2015 Doesn't really matter what machines get it, changing the hostname to the IP makes no odds to anything. The issue is that although I can tell Solus3 what connect.ini file to use and push it out to the clients, it always overrides with the information entered below and I can't see any option to use one or the other. There's no remote server; the VPN runs from their staff laptops and connections directly to the network. DNS doesn't work over the VPN hence the requirement of the IP rather than hostname. I tried the read only thing when sending it out via GPO and it didn't seem to make a difference. Might try again though in case muppet-mode engaged!
mrwoberts Posted October 6, 2015 Posted October 6, 2015 (edited) Is the IP address of your server dependent on whether the client is internal/external. What I mean is, when the laptop is internal, the server is 10.10.10.20, but when the client is at home, the server is 212.212.212.5 (for example... ) Some options... Add an entry to your "C:\Windows\System32\drivers\etc\hosts" file for your server, assuming it stays the same between internal/external (just make a note that you've done this for future IP changes...) ICACLS block write access to the connect.ini file Example icacls C:\Path\to\connect.ini /deny Everyone:(D,WD) Edit: just corrected my deny permission mistake! Edited October 6, 2015 by mrwoberts 1
synaesthesia Posted October 6, 2015 Author Posted October 6, 2015 (edited) Hmm that's a good point. I shall have a try at that now. Setting the file read only worked fine, however if I can get that to work without modifying them at all then win-win. ** Small update - Looks like DNS should be doable with the VPN, hopefully Schools Broadband will be able to help with that. Edited October 6, 2015 by synaesthesia
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now