# Bug Report: Quick Desktop 1.0.3490 Network Sandbox Blocks Local Network MCP Server Resolution (\[Errno -2\]) **URL:** \ **Category:** Q&A\ **Tags:** MCP, amazon-quick, desktop, error, integrations, business-user, quick-sight\ **Created:** [September 23, 2026, 9:14am UTC](https://community.amazonquick.com/t/bug-report-quick-desktop-1-0-3490-network-sandbox-blocks-local-network-mcp-server-resolution-errno-2/53748 "2026-09-23T09:14:04Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![gsharma36](https://avatars.discourse-cdn.com/v4/letter/g/3e96dc/32.png) [@gsharma36](https://community.amazonquick.com/u/gsharma36)\ **Post date:** [September 23, 2026, 9:14am UTC](https://community.amazonquick.com/t/bug-report-quick-desktop-1-0-3490-network-sandbox-blocks-local-network-mcp-server-resolution-errno-2/53748/1 "2026-09-23T09:14:04Z")
Hello, After updating **Amazon Quick Desktop version 1.0.3490 i am not able to connect to my existing remote (https) based MCP server**, the application looks completely isolated from the host operating system’s native network routing layer. The application failed to resolve or connect to a local remote Model Context Protocol (MCP) server hosted on a separate Linux instance within the same corporate subnet, throwing a strict **`[Errno -2] Name or service not known`** error. Before updating to this version , i was able to connect my MCP server to amazon quick desktop via windows 11 . error screenshot is attached. Can you assist how to fix this issue ? ![MCP_error](https://d1wl4jav5dp96l.cloudfront.net/original/3X/8/7/8741652bd846b72067876f851e80b48f7e2a6f4c.png) Thanks & Regards Gourav ---
**Author:** ![WLS-Luis](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/wls-luis/32/36723_2.png) [@WLS-Luis](https://community.amazonquick.com/u/WLS-Luis)\ **Post date:** [September 23, 2026, 5:07pm UTC](https://community.amazonquick.com/t/bug-report-quick-desktop-1-0-3490-network-sandbox-blocks-local-network-mcp-server-resolution-errno-2/53748/2 "2026-09-23T17:07:58Z")
Hi @gsharma36, Welcome to the Quick Community! This behavior can definitely occur when receiving new updates. Based on your description and the image below, this indeed appears to be a bug/error, so I will make sure to keep this post marked as such so that the AWS Team may address this overall behavior for future updates. It is definitely possible that this issue may resolve itself shortly after, so feel free to keep trying within the next few days. If this still occurs, however, I would definitely recommend [creating a support ticket](https://docs.aws.amazon.com/awssupport/latest/user/case-management.html) with AWS Support in the meantime. Thank you! ---
**Author:** ![Xclipse](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/xclipse/32/20455_2.png) [@Xclipse](https://community.amazonquick.com/u/Xclipse)\ **Post date:** [October 10, 2026, 3:10pm UTC](https://community.amazonquick.com/t/bug-report-quick-desktop-1-0-3490-network-sandbox-blocks-local-network-mcp-server-resolution-errno-2/53748/3 "2026-10-10T15:10:10Z")
Hi @gsharma36, It’s been a while since we last heard from you, did you have any additional or follow up questions regarding your initial topic? Were you able to try out the second approach that was shared? If we do not hear back within the next 3 business days, I’ll go ahead and mark the solution to close out/archive the topic. Thank you! ---
**Author:** ![gsharma36](https://avatars.discourse-cdn.com/v4/letter/g/3e96dc/32.png) [@gsharma36](https://community.amazonquick.com/u/gsharma36)\ **Post date:** [October 10, 2026, 3:37pm UTC](https://community.amazonquick.com/t/bug-report-quick-desktop-1-0-3490-network-sandbox-blocks-local-network-mcp-server-resolution-errno-2/53748/4 "2026-10-10T15:37:55Z")
Hi, It is still not connecting via remote http, i am getting same error, however as workaround i have connected through npx (-y mcp-remote https://) locally, if you have any fix or workaround to connect MCP via remote directly, please help. Thanks Gourav