I
IT-Alex_W
Guest
I am using the latest version of Edge browser (Version 83.0.478.56 (Official Build) (64-Bit)) installed on a Windows 10 1909 client.
In our company we are using multiple proxy servers for each site.
F.e.:
10.1.8.2/24 -> Germany
10.2.8.2/24 -> Italy
10.3.8.2/24 -> France
...
10.23.8.2/24 -> USA
The proxy settings for windows are configured by a group policy which sets the script address to http://proxy.domain.com/proxy.pac.
The domain name proxy points to all IP addresses of the proxys in the branches (total 23 entrys).
The DNS server has round robin and netmask ordering enabled.
If a client is trying to access a website, the DNS should tell the client the "network closest" proxy server.
F.e.:
Client Germany (10.1.8.99/24) should get the German proxy
Client Italy (10.2.8.99/24) should get the Italian proxy
Client USA (10.23.8.99/24) should get the US proxy
If f.e. a German client uses "nslookup proxy" in cmd, it always tells the correct/"network closest" proxy server.
If f.e. a German client tries to browse to a website in Edge, it often tries to connect to a random proxy server. After - in worst case 22 mistrial - it connects to the correct server and the internet is working.
We had the same problem with the Google Chrome browser a few month ago (Proxy.pac file not loaded correctly - Google Chrome Community) and got no answer/help/solution.
Browsers like Firefox or Internet Explorer are working well with these settings.
What can I do to solve this issue?
More...
In our company we are using multiple proxy servers for each site.
F.e.:
10.1.8.2/24 -> Germany
10.2.8.2/24 -> Italy
10.3.8.2/24 -> France
...
10.23.8.2/24 -> USA
The proxy settings for windows are configured by a group policy which sets the script address to http://proxy.domain.com/proxy.pac.
The domain name proxy points to all IP addresses of the proxys in the branches (total 23 entrys).
The DNS server has round robin and netmask ordering enabled.
If a client is trying to access a website, the DNS should tell the client the "network closest" proxy server.
F.e.:
Client Germany (10.1.8.99/24) should get the German proxy
Client Italy (10.2.8.99/24) should get the Italian proxy
Client USA (10.23.8.99/24) should get the US proxy
If f.e. a German client uses "nslookup proxy" in cmd, it always tells the correct/"network closest" proxy server.
If f.e. a German client tries to browse to a website in Edge, it often tries to connect to a random proxy server. After - in worst case 22 mistrial - it connects to the correct server and the internet is working.
We had the same problem with the Google Chrome browser a few month ago (Proxy.pac file not loaded correctly - Google Chrome Community) and got no answer/help/solution.
Browsers like Firefox or Internet Explorer are working well with these settings.
What can I do to solve this issue?
More...