hello,
we have developers working from home. when using the sophos connect client and they attempt to deploy a report using Visual Studio to an internal server they have set in the configuration properties they get a 400 bad request from within Microsoft Visual Studio. The report is being deployed to an internal server running SSRS using the format servername.domain.local/reportserver
The tunnel/FW rules allow access to all our local networks and I can see the traffic being allowed in the log viewer to the server, and they can RDP to the specific server hosting the report without any issues. there are no restrictions on what they can access over the VPN.
the strange thing is if they use our old VPN tunnel and attempt to deploy the report in the same manner it works just fine.
here are the differences between the two the old vpn uses RRAS on a windows server that hands out IP address to anyone that uses it so those clients get local network address so it appears that they are connected to the local network.
Sophos connect vpn is using a 10.x.x.x for clients and is set on the FW in the Sophos Connect Configuration. the users authenticate with sophos connect using there domain credentials so it is using AD to authenticate them
i have had them try using sophos connect using different means for the server such as http://server/reportserver http://server.domain.com/reportserver and http://serverip.domain.com/reportserver in order to deploy the report
the other odd thing is that if they open a browser while on sophos connect vpn and attempt to connect to the url of the server they are deploying the report to it prompts for credentials and works fine that way
any insight would be greatly appreciated.
This thread was automatically locked due to age.
