Hallo,
with Windows 7 i could connect in open VPN to Customer and work in my Applications through Citrix Receiver.
Now we have Windows 10 and always my Connection to my internal Working place with the Citrix Applications is broken.
Can i do some Settings , to fix this ?
Greets
Ralf
With Windows 10 cant work in Citrix Receiver
Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech
-
- OpenVpn Newbie
- Posts: 6
- Joined: Wed Jan 11, 2017 7:35 am
-
- OpenVPN Protagonist
- Posts: 11137
- Joined: Fri Jun 03, 2016 1:17 pm
Re: With Windows 10 cant work in Citrix Receiver
Probably your w10 firewall needs something configured.
-
- OpenVpn Newbie
- Posts: 6
- Joined: Wed Jan 11, 2017 7:35 am
Re: With Windows 10 cant work in Citrix Receiver
Hello,
no the Customers. When we connect. We are not behind an Firewall !
Greets
Ralf
no the Customers. When we connect. We are not behind an Firewall !
Greets
Ralf
-
- OpenVPN Protagonist
- Posts: 11137
- Joined: Fri Jun 03, 2016 1:17 pm
Re: With Windows 10 cant work in Citrix Receiver
With such little detail it is impossible to provide further assistance.
Please see:
HOWTO: Request Help !
Please see:
HOWTO: Request Help !
-
- OpenVpn Newbie
- Posts: 6
- Joined: Wed Jan 11, 2017 7:35 am
Re: With Windows 10 cant work in Citrix Receiver
I tried now with Ovpn 2.4 but than we habe error like this
Options error: Unrecognized option or missing or extra parameter(s) in Buchs RZ.ovpn:6: tls-remote (2.4.0)
Use --help for more information.
Options error: Unrecognized option or missing or extra parameter(s) in Buchs RZ.ovpn:6: tls-remote (2.4.0)
Use --help for more information.
-
- OpenVPN Protagonist
- Posts: 11137
- Joined: Fri Jun 03, 2016 1:17 pm
Re: With Windows 10 cant work in Citrix Receiver
RalfThomas wrote:Options error: Unrecognized option or missing or extra parameter(s) in Buchs RZ.ovpn:6: tls-remote (2.4.0)
The Manual 2.3 wrote:Please also note: This option is now deprecated. It will be removed either in OpenVPN v2.4 or v2.5. So please make sure you support the new X.509 name formatting described with the --compat-names option as soon as possible by updating your configurations to use --verify-x509-name instead