Skip to main content

Network Troubleshooting Guide

Troubleshoot network connection issues in DaySmart Desktop when a client computer can’t connect to the server, including checking the server name, firewall settings, ping testing, and common SQL Server components.

Kyle Goodman avatar
Written by Kyle Goodman
Updated this week

📝 Overview

Learn how to reconnect client computers when they lose connection to the server computer. These steps assume the software is installed and working on the server computer.

⚠️ Before you start

Networking can be complex, and connection issues are often related to Windows settings, firewalls, or your local network setup. If you’re unsure about any of the steps in this guide, or would like help confirming your setup, please reach out to our Support team. We’re happy to assist.

🛠️ Troubleshooting Steps

Learn how to check your connection settings, rule out firewall/network issues, and resolve common SQL Server-related causes.

🧭 Step 1: Confirm the correct server name

If you’re connecting from a client computer and it can’t find the database, confirming the server name helps ensure you’re pointing to the correct computer.

⚠️ Please Note: If your server and a client computer share the same computer name, the client may not be able to connect. Rename one of the computers in Windows before continuing.

Click the arrow to learn how to confirm to server name

  1. On a computer that is working (the server or another connected client), open the software.

  2. Go to File → Database Settings → Connection Settings.

  3. Locate and write down the Server Name shown in that window.

🔌 Step 2: Reconnect from the client computer

If the client computer shows “No Database Open,” “SQL Server could not be found,” or similar connection errors, use these steps to reconnect to the server database.

Click the arrow to learn how to reconnect to the server from a client computer

  1. Go to the client computer that is not connecting and open the software.

  2. If you see “SQL Server could not be found,” select Continue without Connecting (you should see No Database Open).

  3. Go to File → Database Settings → Connection Settings (or Edit Connection Settings, depending on what you see).

  4. Choose This is an additional computer (client) and select Continue.

  5. Choose Manual Setup, then enter the server name you recorded (Step 1) in the Connect to field.

  6. Select Continue/Connect.

  7. If prompted, enter your database password (if one was set).
    ​

🧱 Step 3: Check for firewall blocks on the server

If you get errors like “SQL Server was not found,” the most common causes are a server-side firewall or a network communication issue.

Click the arrow to learn more about firewall conflicts

  1. On the server computer, temporarily turn off Windows Firewall (and any antivirus firewall such as Norton/McAfee).

  2. Try connecting again from the client computer.

  3. If the client connects with the firewall off, turn the firewall back on and set up firewall exceptions instead of leaving it disabled.

📡 Step 4: Run a ping test (client → server)

A ping test confirms whether the client computer can communicate with the server over your network.

Click the arrow to learn how to run a ping test

  1. On the client computer, open Command Prompt (Windows Start → Accessories → Command Prompt).

  2. Type: ping [server computer name] and press Enter.

    • Example: if the server name is THOMAS\\CMJ, you would ping THOMAS.

  3. If ping is successful, it’s likely not a network visibility issue (go back to firewall checks or proceed to “Other Suspects”).
    ​

  4. If ping fails, try these basics:

    • Restart both client and server computers

    • Confirm both computers are connected to the same router (check cables/Wi-Fi signal)

    • Restart the router (unplug for several seconds, plug back in)
      ​

🧷 Step 5: Temporary workaround — connect using the server IP address

⚠️ Please Note: This is not recommended if your server is assigned an IP address dynamically (the address may change and break connections again).

Click the arrow to learn how to connect to the server IP

  1. On the server, open Command Prompt and type ipconfig.

  2. Locate the IPv4 Address (or “IP Address” on older Windows versions).
    ​

  3. On the client, go back to the Select Server screen and replace the server name with the server’s IP address, then select Connect/OK.

  4. If needed, try pinging the IP address from the client the same way you pinged the server name.

🧩 Step 6: Uncommon Suspects

Roughly 99% of client connectivity issues are caused by server-side firewalls or network problem, only try these after exhausting the steps above.

Click the arrow to learn more about other potential issues

  • Client-side outbound firewalls: Some antivirus tools include outbound firewalls. Disable them or configure exceptions.

  • SQL Server Browser is disabled:

    • Windows Start → Microsoft SQL Server 2012 → Configuration Tools → SQL Server Configuration Manager

    • Go to SQL Server 2012 Services and ensure SQL Server Browser is Running and set to Automatic.

  • TCP/IP is disabled for the SQL instance:

    • SQL Server Configuration Manager → SQL Server Network Configuration → Protocols for your instance

    • Ensure TCP/IP is Enabled. If you change it, restart the SQL instance.
      ​

  • SQL Server install issues: If all clients are unable to connect and you have verified backups, a reinstall of SQL Server may be required.

❓ FAQs

Find answers to common questions or additional details that may not be covered in the main instructions.
​

Click the arrow to view frequently asked questions
​

What’s the most common cause of client computers not connecting?

Click the arrow to view the answer

Most connection issues are caused by server-side firewall blocks, internet connection, or the client not being able to see the server on the network.

Should I leave Windows Firewall turned off?

Click the arrow to view the answer

No. Turning it off is a good temporary test. If that resolves the issue, turn it back on and configure firewall exceptions instead of leaving your firewall disabled

Can I connect using the server IP address?

Click the arrow to view the answer

Yes, but it should be temporary unless your server has a static IP address. If your IP is dynamic, it may change and break the connection again.

Related Articles
Network Setup
Using AVG Internet Security in a Network Environment
Using Kaspersky in a Network Environment
Using Windows Firewall in a Network Environment
Using McAfee in a Network Environment
Did this answer your question?