I'm having a problem with Remote Desktop over my VPN connection.
We've been using Remote Desktop and the same VPN for over 4 years. Recently I changed the IP of our firewall from 10.0.0.9 to 10.0.2.9. Everything seems to route properly within the Lan. I have three networks 10.0.0.0, 10.0.1.0. and 10.0.2.0. Most VPN users are on the 10.0.0.0 network. VPN users are now getting a dhcp address from the Sonicwall 10.0.2.100 through 10.0.2.200.
Since the change every time a user tries to access the their desktop at work from home using Remote desktop, remote desktop crashes frequently with this error "Because of an error in data encryption, this session will end. Please try connecting to the remote computer again." I tried using VNC also with the same problem but I get this error "ZlibInStream: inflate failed. DO you wish to attempt to reconnectto". It seems like it happens more when there are a lot of screen updates. The problem only happens when a VPN user tries to access a computer 10 the 10.0.0.0 network. All is well when trying to access a computer on the 10.0.2.0 network.
Has anyone run into this problem?
We've been using Remote Desktop and the same VPN for over 4 years. Recently I changed the IP of our firewall from 10.0.0.9 to 10.0.2.9. Everything seems to route properly within the Lan. I have three networks 10.0.0.0, 10.0.1.0. and 10.0.2.0. Most VPN users are on the 10.0.0.0 network. VPN users are now getting a dhcp address from the Sonicwall 10.0.2.100 through 10.0.2.200.
Since the change every time a user tries to access the their desktop at work from home using Remote desktop, remote desktop crashes frequently with this error "Because of an error in data encryption, this session will end. Please try connecting to the remote computer again." I tried using VNC also with the same problem but I get this error "ZlibInStream: inflate failed. DO you wish to attempt to reconnectto". It seems like it happens more when there are a lot of screen updates. The problem only happens when a VPN user tries to access a computer 10 the 10.0.0.0 network. All is well when trying to access a computer on the 10.0.2.0 network.
Has anyone run into this problem?
