Solution to drive/client/server issues in a Workspace

Solution to drive/client/server issues in a Workspace

Introduction

Some of the workspaces have manually configured the proxy to allow domain whitelisting. Earlier, we received messages concerning the visibility of the I: and Z: drives when the proxy was configured. We have updated the article Manual proxy configurations to fix this issue. This involves adding an exception address. Currently, we received other messages that it is not possible to connect to internal servers (for instance VMs that function as Galaxy or RedCap servers) after configuring the proxy.

Solution

Follow the instructions in Manual proxy configurations and add another exception address specific to your internal server.

In short:
  1. Navigate to the manual proxy setup settings.
  2. Add the exception address for the visibility of the I: and Z: drives.
  3. Add the exception address for the internal server you want to connect to.


    • Related Articles

    • Z:-drive not available in newly created VM from image

      Bug description A VM based on an image does not mount the Z-drive for those who were part of the VM from which the image was created. However this is visible: Related to: Create VM-templates for your Workspace Creating VM images for Shared Gallery ...

    • Proxy configurations for connecting to a server or blob

      Version: 2022-11-02 Update: 2022-11-14 Introduction Domain allowlisting is a selfservice feature that is now available on myDRE. As the name implies, domains on the allowlist can be accessed from within the Workspace (you can request specific domain ...

    • Z:/ Drive Not Visible

      20th September 2024 Dear myDRE users, We are aware that some users are having trouble accessing the Z:/ drive in their Workspace. The main reason for this issue is that many applications have shifted to using TLS 1.2 for security. Azure's management ...

    • I cannot see the Z:-drive or I:-drive

      The problem It can happen for some reasons you don't have access to your z:-drive or I:-drive. The main reason for this issue is that many applications have shifted to using TLS 1.2 for security. Because of this, please follow the instructions in Z:/ ...

    • [Resolved] Data drive not accessible

      Version:  2022-12-12 Updated: 2022-12-13 TL;DR TL;DR: Some myDRE Workspaces experienced an issue regarding the availability of the data drive. It has been resolved, the workaround is no longer needed. We apologise for any inconvenience this might ...