Skip to content
  • There are no suggestions because the search field is empty.

Fix "Remote Name Could Not Be Resolved" for portal.webgility.com

You are seeing the error "The remote name could not be resolved: portal.webgility.com" when Webgility Desktop tries to reach the Webgility Portal. This is a DNS lookup failure on your Windows computer, not a Webgility outage — your internet works for other sites but this specific hostname cannot be looked up.

Why this happens. Windows uses a DNS server (usually provided by your router or internet provider) to translate hostnames like portal.webgility.com into IP addresses. When that DNS server is slow or misconfigured, some hostnames fail to resolve while others work fine. Switching Windows to Google's public DNS gives a reliable lookup path.

  1. Open Windows Network and Sharing Center, click your active connection name, then click Properties. A dialog opens listing the network protocols this connection uses.
  2. Find Internet Protocol Version 4 (TCP/IPv4) in the list, select it, and click Properties. A new dialog opens with radio buttons for DNS server settings at the bottom.
  3. Select Use the following DNS server addresses. In Preferred DNS server enter 8.8.8.8. In Alternate DNS server enter 8.8.4.4. These are the addresses for Google Public DNS.
  4. Click OK to close both dialogs, then reopen Webgility Desktop and retry — the Portal connection should complete without the error.

If the error persists after the DNS change, the block may be at your router or your workplace firewall. Contact your IT administrator with the exact error text, or contact Webgility Support if you are not part of a managed network.