bobmanuk

Answer from ESS is to remove the 2 registry keys found: HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections So even though manually turning the proxy off showed that it was empty I guess the system still thought it was set. Updates have now downloaded and deployed. Thanks for the suggestions everyone.

I was really hoping that would have fixed it, Double checked that it is now showing NULL in the database and it is, but it is still refusing to download any of the updates. Ive had the Sims support company log a ticket with ESS anyway, its just neither of them are particularly quick. I'll just have to wait until I hear something back. Thank you so much for your help anyway.

Thanks for this, I can see the proxy_address is empty, not NULL, port is NULL, domain name, username and password are all empty not NULL. I know that sometimes, empty does not necessarily mean NULL, but I'm not sure in this case.

We don't need a proxy and there was no proxy set in the Solus3 GUI anyway. I have tried to set then clear the proxy information but it still will not download any updates

I saw another post that suggested checking with netsh winhttp show proxy and it definitely says its empty, I tried the command in your quote and it still says that no proxy is set. But thanks for the thought. Ive also been going through the log files as someone else said they could see Solus still trying to use the proxy, But the log files just don't show anything other than they weren't able to access the PKG URL. Im tempted to dip into the Solus database to see if I can find anything related to proxys, but ill be honest, I don't really want to. I don't know enough about SQL to fix it if I break it.

We have, they are still at the stage of telling us that there are new URL's to use and to whitelist them, we have gotten back to them but are still waiting for a response. Right now I'm clutching at straws, so I will try your suggestion and let you know.

Im with you on the browser thing, however... IE is useless and I needed something test with... which in this case, proves that the server is capable of accessing the site and that Sophos is allowing the server through... I'd say that justifies the resources, once I've finished, it'll be removed. Sophos doesn't have a proxy setting, proved by the fact the rest of the system is able to access sites without issue, it seems to me that this is a Solus thing, but I'm not that familiar with it, So I was hoping that there is another setting that I've missed.

Ive never used Fiddler before but I have heard of it. I believe I've turned on HTTPS stuff (it installed its own cert) Ive restarted Solus and told it to check for updates. I see an entry where it checks capitasolus.co.uk (it seems to have gone back to the old site after restarting Solus) But its currently trying to download the Sims update and keeps failing, but not showing anything in the Fiddler App...

I have already whitelisted the new site, both the site exactly as it is and *.ess-solus.co.uk (IE any subdomain) and as I said, I can take the entire URL that Solus tries to download copy/paste into chrome and it downloads it without issue.

We recently upgraded a schools internet connection and set them up with a Sophos XG firewall. They were using RM SafetyNet. We have removed all mention of a proxy in My Site-> Proxy Settings. Removed it from Internet Explorer Settings and removed it from the Sims Services Manager. Services have been restarted and server has been rebooted. I have entered rules that the Sims server is not subject to any filtering and just for good measure, added ess-solus.co.uk and capitasolus.co.uk to the exceptions and bypass rules. I can take the URL that Solus tries to access and paste it into a browser and the PKG downloads just fine, So I don't suspect that the firewall is to blame. Until recently, asking Solus to check for updates resulted in none available, to now saying 10 updates available. but still cannot download the 7.198.31 update, saying (with a pink bubble at the top) unable to connect to S3dl.ess-solus.co.uk and similarly, If I try to deploy an update I get "A connection Attempt Failed because the connected party did not respond...." Have I missed something? Everything I can see points to Solus3 not being able to access it, but the server seems to be able to just fine.