Open mmattel opened 6 years ago
@mmatte for the record; which VPN client are you using?
The other day I was checking https://central.owncloud.org/t/does-someone-try-to-hack-my-owncloud-desktop-client/11145 and, if confirmed, together with yours might point out at some lower-level/upstream networking issue.
It is a Cisco VPN and soon the native W10 VPN. The domain owncloud runs is registered with a fixed IP (no DDNS).
This means that there is no domain/IP resolution issue. It is the owncloud client which does not recognize the change from direct to proxy and vice versa. = eg if direct is not available try the other one according the setting (use system proxy) If I terminate the client and restart it, it immediately recognizes the network access and things run fine.
The client gets confused because on VPN there is a proxy (by system settings) which is not the case when using direct access. Sometimes he recognizes the switch, most times not.
Expected behaviour
Beeing in a VPN with a proxy (ok), disconnecting the VPN and do some work (ok), start VPN again, the client confuses and does not connect to the server - no connection. Windows seamless continues to work, browsing ect has no problems beeing in the VPN or not. It seems that the client does not recognize the changed connection state properly.
Actual behaviour
The client must be terminated and restarted to connect.
Client configuration
Client version: 2.4.0 (build 8894)
Operating system: W10x64
OS language: German