Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

VPN network unaccessible with Firefox multiple profiles

  • 1 antwoord
  • 1 heeft dit probleem
  • 5 weergaven
  • Laatste antwoord van john277

more options

Hello,

I have Firefox with two profiles, Personal and Work. I also have a VPN provided by the company which is setup on Windows 10 as a Public Network, on both profiles the network settings are the same and while the Personal has anti ads and privacy plugins, the Work doesn't have a single plugin.

My issue is that the Personal profile is able to use the VPN and access the work network while the Work profile is not. With both network settings matching, are there any settings in the About:config that i can check that would co-relate with the issue that i'm having?

Hello, I have Firefox with two profiles, Personal and Work. I also have a VPN provided by the company which is setup on Windows 10 as a Public Network, on both profiles the network settings are the same and while the Personal has anti ads and privacy plugins, the Work doesn't have a single plugin. My issue is that the Personal profile is able to use the VPN and access the work network while the Work profile is not. With both network settings matching, are there any settings in the About:config that i can check that would co-relate with the issue that i'm having?

Alle antwoorden (1)

more options

After a bit more investigation i've found out there's only some internal domains that i'm not able to access it, mainly because Firefox keeps forcing HTTPS into a internal domain that does not have the HTTPS port available.