This will vary depending on the network and route settings for your organization. Cisco and other VPNs advertise certain routes to connected clients. It sounds like the DNS to resolve the r-studio server, or the r-studio server itself, is not on a route advertised by the VPN. When troubleshooting with your system administration team, they may ask you to try to connect by the IP address of the server (do you know this?) or ping the server, or telnet to the server and port combination. In the end, this sounds like a configuration problem that you will need organizational support to resolve.
Make sure that you only have one connection active, and are not on any home networks with a similar IP address to the r-studio one. If an advertised route conflicts with a route to your home router, there might be a conflict. Try changing the IP range offered by your home router, and check for any other virtual networks, such as from virtual machines.
EDIT: I also notice you drew particular attention to the browser. "Anything through a browser" isn't working. By the same principles, check your browser's Proxy setting. If you have previously been accessing a proxy, that proxy may no longer be on an available network. If this is the case, you'll have to change your browser settings not to use a proxy when connected to the VPN.
And remember: Don't Panic.
