> For the complete documentation index, see [llms.txt](https://help.sbtinstruments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sbtinstruments.com/troubleshooting/other-problems/cannot-connect-to-access.md). # Cannot connect to Access Access does not open in your browser. You followed [Connect to Access](/more/software/connect-to-access.md), but the browser shows *This site can't be reached*. The code under the message tells you what to check. ## *ERR\_CONNECTION\_REFUSED* The cable works, but something blocks the connection. 1. Type **** in the address bar, with *http* and not *https*. Press Enter. 2. Try another computer. A setting on yours may block the connection. 3. Ask your IT department to allow connections to 10.20.30.40 on port 80 over TCP. A company firewall can block it. ## *ERR\_CONNECTION\_RESET* The cable connection may be broken, or there is a software issue. 1. Look for your BactoBox® as a USB drive in Windows Explorer, for example `D:\`. If it is there, the cable works. If not, check that the USB cable sits firmly at both ends, and look for damage near the plugs. 2. Test the USB port on your computer with another device, for example a USB stick. 3. Check that the drive holds both *SBT Access.html* and *summary.csv*. If one is missing, [contact support](/troubleshooting/contact-support.md) and tell us which file. --- # 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://help.sbtinstruments.com/troubleshooting/other-problems/cannot-connect-to-access.md?ask=&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.