# Troubleshooting socket errors on the MiniSeq

Initialization of MiniSeq Control Software (MnCS) can fail with one of the following errors.

* “While attempting to initialize communication with firmware prior to reading device settings from NVRAM. (System.Net.Sockets.SocketException)."
* "Socket error on TCP port 192.168.113.2:5555 (System.Net.Sockets.SocketException)."
* "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.113.2.5555Error code is “10060”."

  ![](/files/VKcDGcLx4XcuG2RDL5aR)

This can occur if the Network Interface Card (NIC) for the internal network is configured incorrectly. (The MiniSeq has 2 NIC--one connects the instrument to the network, and the other is for SBC to hardware control computer MPCA communications.)

**Troubleshooting steps:**

* Close the MiniSeq Control Software (MnCS).
* Navigate to Control Panel > Network and Sharing Center > Change adapter settings (or Windows mark > Settings > Network and Internet).
* To determine which network is the NIC and which is the outside network, unplug the Ethernet cable from the instrument and see which of the 2 networks goes down--the one that goes down is for the internet or the outside network. It will list as "network cable unplugged."\
  \*
* Select the other NIC which is for internal communications: “unidentified network” > Properties.
* Networking should be TCP/IPv4 enabled (IPv6 should not be selected) > Properties button.
* Update Static IP address.
  * If the instrument is on Windows 10 / MiniSeq 2.0+, update IP address to 192.168.113.3
  * If the instrument is on Windows 7 MiniSeq 1.x, update IP address to 192.168.113.7
* Set subnet Mask to 255.255.255.0
* Leave Default gateway blank.
* Select OK in all dialog boxes and close.
* If there is a notification about an adapter with duplicate settings, select "Proceed" to use the settings that were just selected.
* Close all setting panel windows. If starting MnCS without an Ethernet cable, the instrument will not show any error.
* Power cycle\* the MiniSeq, plug the Ethernet cable back while the instrument is off, and open MnCS again.
  * \*For further information, search for Knowledge Base article **How to Power Cycle the MiniSeq**.

\
\
\ <br>

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


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://knowledge.illumina.com/instrumentation/miniseq/instrumentation-miniseq-troubleshooting-list/000001219.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.