Topics Map > ResearchDrive
ResearchDrive - Connecting From a Windows Computer
This document describes how to connect to ResearchDrive storage from a Microsoft Windows computer.
ResearchDrive Account Overview
Account Naming Convention
- ResearchDrive storage accounts are named based on the PI's NetID such as \\research.drive.wisc.edu\[PI NetID]
- Restricted ResearchDrive accounts use the naming convention \\restricted.drive.wisc.edu\[PI NetID]
- Replace references to [PI NetID] with the PI's NetID username.
- Replace references to [NetID] or [NetID password] with your NetID username and password.
Restricted Data
ResearchDrive aligns with the Secure Storage Request process and compliance requirements on the Cybersecurity Risk Management and Compliance website.
- Any UW–Madison endpoint used to access restricted data must be maintained and supported by trained IT staff to ensure they are secure and not vulnerable to malware.
- External collaborators will need to complete an endpoint security checklist to document the security controls in place at their institution.
- Access to restricted data from any other unauthorized endpoint is prohibited.
- Please refer to the ResearchDrive FAQ for additional details.
Connectivity Options
There are several ways to access ResearchDrive storage from a Windows computer.
option | requires campus network or vpn | protocol | comment |
---|---|---|---|
Mapping a network drive using My Computer | yes | smb | Recommended Option for UW-Madison Windows computers |
Access ResearchDrive with Globus | no | gridftp or https | Recommended Option for external collaborators |
Mapping a network drive using the Command Prompt | yes | smb | Windows Command Prompt |
Mapping a network drive using Windows Powershell | yes | smb | Windows Powershell |
Mounting ResearchDrive in Windows Subsystem for Linux (WSL) | yes | smb | Windows Subsystem for Linux (WSL) |
Mapping a Network Drive using My Computer
- If you are off campus or using wifi then you will need to connect to WiscVPN. before using ResearchDrive.
- Open the Windows Start Menu and right-click on Computer or This PC. Click Map Network Drive.
- Select the a drive letter and enter \\research.drive.wisc.edu\[PI NetID ]
- Ensure that the Reconnect at logon box is checked.
- Check the box labeled Connect using different credentials.
- Click Finish.
- User name: [NetID]@ad.wisc.edu or ad.wisc.edu\[NetID]
- Password: [NetID password]
- Check the box labeled Remember my credentials if desired.
- Click OK.
- If the connection was successful, Windows Explorer will open the mapped network drive. Refer to the Common Problems / Troubleshooting section if you have problems connecting.
Connect to ResearchDrive with Globus
Please refer to Globus - Access ResearchDrive or SharedDrive Stoage with Globus.
Mapping a Network Drive using the Command Prompt
- If you are off campus or using wifi then you will need to connect to WiscVPN. before using ResearchDrive.
- Click the Start button and type cmd in the Search field.
- Click cmd.
- Type the command
net use r: \\research.drive.wisc.edu\[PI NetID] /savecred /persistent:yes
- Hit Enter.
- Enter your username and password at the prompt:
- User name: [NetID]@ad.wisc.edu
- Password: [NetID Password]
- Hit Enter.
- Click the Computer icon in the Start enu. The recently mapped network drives will now appear in the Network Location section. Refer to the Common Problems / Troubleshooting section if you have problems connecting.
Mapping a Network Drive using Powershell
- If you are off campus or using wifi then you will need to connect to WiscVPN. before using ResearchDrive.
- Click the Start button and type powershell in the Search field.
- Click Windows Powershell.
- Use the New-PSDrive PowerShell command to connect to Research Drive.
- If you are connecting to ResearchDrive from a Windows computer that is joined to Campus Active Directory then use this command:
New-PSDrive -Name R -PSProvider FileSystem -root \\research.drive.wisc.edu\[PI NetID] -Persist
- If you are connecting to ResearchDrive from a Windows computer that is not joined to Campus Active Directory then use these commands:
$credential = Get-Credential $user=$credential.GetNetworkCredential().UserName New-PSDrive -Name R -PSProvider FileSystem -root \\research.drive.wisc.edu\$($user) -Credential $credential -Persist
- If you are connecting to ResearchDrive from a Windows computer that is joined to Campus Active Directory then use this command:
- Click the Computer icon in the Start Menu. The recently mapped network drives will now appear in the Network Location section. Refer to the Common Problems / Troubleshooting section if you have problems connecting.
Mounting ResearchDrive in Windows Subsystem for Linux (WSL)
- If you are off campus or using wifi then you will need to connect to WiscVPN. before using ResearchDrive.
- Make a directory for the ResearchDrive mount point in WSL
$ sudo mkdir -p /mnt/researchdrive/mplayde
- Install kerberos user tools in WSL
#Ubuntu $ sudo apt install krb5-user #CentOS $ sudo yum install krb5-workstation
- Add the ad.wisc.edu Kerberos servers to /etc/krb5.conf
$ sudo vi /etc/krb5.conf [libdefaults] default_realm = AD.WISC.EDU dns_lookup_realm = false dns_lookup_kdc = false ticket_lifetime = 10h renew_lifetime = 7d forwardable = true rdns = false [realms] AD.WISC.EDU = { kdc = ad.wisc.edu admin_server = ad.wisc.edu } [domain_realm] .ad.wisc.edu = AD.WISC.EDU ad.wisc.edu = AD.WISC.EDU
- Restart WSL with Powershell.Start -> Run -> Open powershell
PS C:\Users\mplayde> wsl.exe --shutdown
- Re-open WSL and get a kerberos ticket
$ kinit mplayde@AD.WISC.EDU Password for mplayde@AD.WISC.EDU:
- Verify that you got a kerberos ticket with klist
$ klist
- Mount ResearchDrive with drvfs
$ sudo mount -vvv -t drvfs //research.drive.wisc.edu/mplayde /mnt/researchdrive/mplayde
- Verify that you can access ResearchDrive
$ ls -alh /mnt/researchdrive/mplayde
- Refer to the Common Problems / Troubleshooting section if you have problems connecting.
Common Problems / Troubleshooting
For more information on common problems that can occur when mapping drives and how to troubleshoot them, please refer to the following resources: