Accessing On-Device Data via Windows File Explorer
Accessing the shared data drive of a Q.station controller, Q.monixx device, or Q.core Data Server using Windows File Explorer.
Access to the shared drive on a Q.station, Q.monixx, or Q.core device requires the SMB (Server Message Block) and Common Internet File System (CIFS) protocols to be enabled on the PC. If it is disabled (as may be the case on some Windows installations), refer to the troubleshooting section for instructions.
-
To access recorded data stored on a Q.station, Q.monixx, or Q.core device, including data located on attached storage media (SD card or USB drive), use Windows File Explorer and enter the device’s IP address, for example
\\192.168.1.200
and press Enter to establish a connection to the device’s shared resources. -
Navigate to the shared Data directory by double-clicking it. When prompted for authentication, enter the following credentials to gain access:
-
Username: data
-
Password: ginsdata
ℹ️ If the PC is domain-joined, specify the username as "\data" during authentication to ensure credentials are validated against the device instead of the domain.
-
-
Once authenticated and connected to the Data share, you will have access to the hd0 directory (and any attached directories). These locations can be accessed and managed in the same way as a local hard disk drive within Windows Explorer.
-
Optionally, the Data directory can be mapped as a persistent network drive in Windows File Explorer. To do so, right-click on the Data folder and select “Map network drive…”, then follow the prompts to assign a drive letter and establish a permanent connection.
Troubleshooting
Enable SMB 1.0/CIFS on Windows 10/11
To enable SMB 1.0/CIFS on Windows 10/11, open Control Panel → Programs → Turn Windows features on or off, enable SMB 1.0/CIFS File Sharing Support, and restart the PC.
“You can't access this shared folder because your organization's security policies block unauthenticated guest access"
Access may be blocked by security policies, refer to the corresponding Microsoft troubleshooting guide for further guidance.