> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-troubleshooting-list/000001287.md).

# Troubleshooting Network errors during run setup on the NovaSeq 6000

The following types of network errors can occur during run setup on the NovaSeq 6000.

**1. Unable to browse to the output folder location**

The NovaSeq 6000 platform requires the designation of an output folder path to a network location prior to the start of a sequencing run in Manual mode. For more information on how to configure the output folder path in File-Based mode, refer to the [NovaSeq 6000 Sequencing System Guide](https://support.illumina.com/downloads/novaseq-6000-system-guide-1000000019358.html).

Important Notes:

* If the run uses BaseSpace Sequencing Hub for both analysis and storage, setting a network output folder location is optional.
* A mapped network drive should be configured by a network administrator.
* The Universal Name Conversion (UNC) path for the network drive is required for setting the output location. Using a mapped letter, such as `Y:\`, results in an Invalid Drive error message.
* Example of a UNC path: `\\servername\share-directory`. For more information, see [How to identify the UNC path of a network server or location.](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000002274.md)

To specify a default output location in the NovaSeq Control Software:

1. From the **Main Menu**, select **Settings.**
2. Select **Manual.**
3. Select **Browse** (next to the Output Folder field).
4. Type or copy and paste the UNC path into the address bar.
5. Select **Enter** on the keyboard, and input network credentials if prompted.
6. Designate the desired folder and select **Select Folder.**
7. Select **Save.**

Once the default output location is designated, the output folder field will automatically populate on the Run Setup screen for future runs. To change the output location for a single run, follow steps 3-7 on the Run Setup screen.

For additional information on networking requirements or run setup procedures, refer to the following resources.

[NovaSeq 6000 System Guide](https://support.illumina.com/downloads/novaseq-6000-system-guide-1000000019358.html)\
[NovaSeq 6000 Site Prep Guide](https://support.illumina.com/downloads/novaseq-site-prep-guide-1000000019360.html)

**2. Unable to verify the network connection. Check that all network cables are connected and retry.**

This error can occur during pre-run checks.

* Confirm the network drive is connected in File Explorer and verify that the correct network UNC path was used.
  * The UNC path for the network drive is required for setting the output location. Using a mapped letter, such as `Y:\`, results in an Invalid Drive error message.
  * Example of a UNC path: `\\servername\share-directory`
* **Note**: As a workaround, the run can be saved to an external drive, but data transfer times may take longer.
* Make sure there is sufficient space locally. Clear runs via Process Management in NovaSeq Control Software (NVCS).
* Verify that there is sufficient space in the output folder. Delete older runs from the output folder location.
* Contact I[llumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) if the issue persists.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #1287), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000001287%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-troubleshooting-list/000001287.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
