Connection failure

Tutorials showing methods of fixing connection failures

Connection failure

Postby Ablyss » Fri Jul 26, 2013 10:22 am

Connection Failure


If you run CMS over a network a connection failure can occur for a number of reasons.
Firstly it may be worth checking the following:

  1. Check that the server machine is turned ON, if it is turned off, turn it on and retry CMS when it has booted up.
  2. Check that all the cables are plugged in and the machine has a connection to the network
In the following guide Server refers to the machine where the database was installed and client represents any other machine on your network.

1. Server Name
When installing the client it is possible that you entered the incorrect name for the server or the server itself may have been renamed.
In the image above the client is trying to connect to a machine called 'computername' (ignore the \ablyss).

    To determine if this is the correct go to the server and perform the following:
  1. Open the Start Menu.
  2. Click on All Programs, Accessories, and on Command Prompt
  3. When the Command Prompt has opened type 'hostname' and press enter

  4. The name returned, in this case servername, is the name of your server
  5. If the name of the server does not correspond with the name of the machine the client is trying to
    connect to, you will have to alter the configuration file. (see article on changing the configuration file)

2. Firewall
In most cases it is the firewall that prevents a client from connecting to the server. To determine if this is the cause of your problem:
  1. Disable Windows Firewall on your server. If you have third party software such as Kaspersky or Norton, you will need to temporarily disable these as well.
  2. If the client can still not connect, repeat the process on the client machine.
  3. If the firewall is the cause of your connection problems you will need to enable certain features (see article on how to create exceptions in windows firewall)
3. Network Address
It is possible, particularly where network is wireless that your server and client are running on two different networks. To determine if this is the case
Follow the steps in Point 1 (Server Name) to open the command prompt.
Type 'ipconfig' and press enter. You will receive similar results to the following.

Windows IP Configuration

Ethernet adapter Local Area Connection:

IP Address. . . . . . . . . . . . :
Subnet Mask . . . . . . . . . . . :
Default Gateway . . . . . . . . . :

Take note of the IP Address and the Subnet Mask

Repeat this process on the client machine. On the client machine the first 3 sets of numbers of the IP address must match
that of the server (in the above example 192.168.1) and the subnet mask must match in its entirety.
If this is not the case your client and server are connected over different networks.
Site Admin
Posts: 23
Joined: Thu Jul 25, 2013 3:53 pm

Return to Connection Failure

Who is online

Users browsing this forum: No registered users and 0 guests