Server not Found

Server not Found

If Firefox is not able to look up the IP address of the computer it is trying to connect to, it will display an error message that looks like this:

There are several potential causes for this problem:

  1. IP address conflict on the local network.
  2. Incorrect network configuration on the terminal.
  3. Unreliable network.
  4. Problems with DHCP

IP Address Conflict

Each device that is connected to a local network needs a unique IP address. When two or more devices are configured to use a single IP address, at least one of these devices will not be able to maintain its connection to the network. Symptoms of an IP address conflict may include no network connectivity, intermittent connectivity, or extremely poor performance.

Incorrect Network Configuration

Subnet mask

If the subnet mask is not configured correctly on the terminal, it will be able to communicate with some, but not all, of the other devices on the local network. It is very difficult to predict which devices the terminal will not be able to communicate with. It is highly dependent on how the local network is configured and on the specific error (i.e. mistake) made while configuring the subnet mask on the terminal. There is no way to calculate or derive the subnet mask; it must be provided by the network administrator.

Default Gateway

If the default gateway is not configured correctly on the terminal, it will only be able to communicate with devices on the local network.

DNS Servers

 If the terminal is not able to resolve the hostname of the FullCount server via DNS, Firefox will not be able to connect to the server. This may happen if the DNS server that the terminal is configured to use is down, or if the DNS server stops responding to DNS queries for some reason.

Unreliable Network

If the network between the device and the FullCount server is not functioning properly, Firefox may not be able to connect to the server.

Problems with DHCP

If the terminal is not able to get an IP address via DHCP, it will not be able to resolve the hostname of the FullCount server via DNS. This can happen if the scope (i.e. the range of IP addresses) that the DHCP server is configured to use is full (i.el when all the IP addresses in the scope are already in use), or when two devices on the network are trying to use the same IP address.

References

  1. Subnetwork
  2. IP Subnetting and Addressing for New Users
  3. Subnet Calculator

    • Related Articles

    • Print Server Troubleshooting Guide

      Print Server Troubleshooting Guide After receiving an alert notification of “Unable to Process Online Order – Print Server is Down” or a customer calls stating Samsung tablets are failing to print please follow the following steps: Request a ...

    • Print Server

      Print Server Objectives Set print server settings so printing via non-FullCount terminals can routed through a different machine. Prerequisites Access to back office Instructions Overview The print server allows for non-FullCount terminals (typically ...

    • Remote Server Decommission Process

      Remote Server Decommission Process The purpose of this document is to track the process for decommissioning a FullCount remote server as part of the transition for the client to be centrally hosted or if the client is leaving FullCount. The first ...

    • SFTP Server Summarization & Communication to Customer

      Subject: Setting up an SFTP Server for Your Team Dear [Customer], I hope this email finds you well. I'm writing to follow up on our recent conversation about setting up an SFTP server for your team. As discussed, I would like to provide you with a ...

    • Use PuTTY to log into a Server or Terminal

      Objectives Log into a server or terminal via SSH. Prerequisites A copy of the PuTTY program installed on your computer. Your computer is powered on and connected to the network. Server or terminal is powered on and connected to the network. Username ...