NETWORK ISSUES IN TIMESCAN


All issues are mentioned here

How to configure TimeScan in a Network ?
The procedure for configuring Network Setting in TimeScan unit.
1.In case you have an existing TCP/IP network at the installation site then allocate a cable for the terminal and a free IP address.

2.In case you do not have an existing TCP/IP network at the installation site then you can use a cross-cable to connect the unit with the PC on which RM is installed.

3.To set the network settings for the terminal go inside the menu by pressing Menu Key on the keypad of TimeScan.

4.In the menu list select Menu number 7 which is "Network".U can go to this option by using "up" "down" arrow key on the keypad or u can directly press key 7.

5.When u enter inside this menu number 7 u will see 4 sub options.

6.Select sub-option number 1 which is "Terminal ID"

7.Set a unique non-zero terminal id for the terminal and press enter.

8.Select sub-option number 2 which is "TCP/IP" and press enter.

9.Keep DHCP off and press enter.

10.Set the Terminal/TimeScan IP address (free on the network)press enter to move ahead.

11.Set the Gateway if TimeScan and Server are connected on two different networks.Press enter to move ahead.

12.Set the server IP address (IP address of the PC on which RM is installed).press enter to move ahead.

13.Use utilities like ping from the PC to detect the terminal.

14.On successful network settings the terminal will show the "009 Contact Master" status only if the RM software & TimeScan is ON.

15.At the same time Software will show "Unregistered" Status.

16.After this enroll this terminal with RM.



Configuration is OK but still not getting connected?

Check following things if the network configuration is OK but still the TimeScan unit is not getting connected with the RM server.

Check Cross or Straight Network Cable:-
Cross Network Cable is used when u r connecting TimeScan directly to the PC.But if the TimeScan is connected in a existing network then straight cable should be used. So check wether cross or straight network cable is used.

Check the LAN cable.:-
This can be checked by pinging the units TCP/IP address from the server.The pinging should be checked by connecting LAN cable.If u dont receive the reply from the TimeScan unit that means that network cable might be faulty.

•TCP/IP address conflict:-
In large network it might happen that the IP address given to the TimeScan might be already present in the network given to some other PC.In that case IP conflict will appear on the PC whose IP address is assigned to the TimeScan. Such a case will neither allow TimeScan to get connected in the network nor it will allow that PC to remain in the network.
To avoid this conflict problem always ping the IP address which u r palnning to assign to TimeScan.If the IP address is getting pinged then it only means that IP address is already asigned to some other device in a network.

•Network Card not configured properly:-
In many cases it happens that the network card is not configured properly due to which the terminal does not connect server. To check this u can ping the Tcp/IP address of the same PC from the same PC.If the response is received that means that the Network card is configured properly.

If u do not receive the reply after ping then it only means that the network card is not configured properly. Contact your Computer Hardware engineer to configure the Network card.


When to use Cross & when to use straight cable?

Cross Cable:
• Cross Network Cable is used when u r connecting TimeScan directly to the PC.
• Using cross cable u can connect only single TimeScan to the Server PC.
• .The distance limitation comes into picture.U can connect the TimeScan upto approximately 6 mtrs.

Straight Cable:

• If the TimeScan is connected in a existing network then straight cable should be used.
• If u want to connect multiple TimeScans to the PC then u will require to use a Hub/switch and now in this case communication cable should be straight
• There is no distance limitation in this case .U can connect the TimeScan upto 100 mtrs.


How to check whether Network cable is working or not?

Any one of the method can be used for checking the quality fo the LAN cable.:
•This can be checked by pinging the units TCP/IP address from the server.The pinging should be checked by
connecting LAN cable to the TimeScan.TimeScan should be kept ON during this process.If u dont receive the

reply then use some other working Cable and then ping the unit.If u receive the reply then it only means that
previous cable is faulty.
• Using continuity meter check the continuity between each cable.
• Check for the physical discontinuity between the cable.


Terminal pings even after removing the network cable?

In large network it might happen that the IP address given to the TimeScan might be already present in the network given to some other PC.In that case IP conflict message will appear on the PC whose IP address is assigned to the TimeScan.

Such a case will neither allow TimeScan to get connected in the network nor it will allow that PC to remain in the network.To avoid this conflict problem always ping the IP address which u r planning to assign to TimeScan.If the IP address is getting pinged then it only means that IP address is already assigned to some other device in a network.


How to check if the network card in computer/server is configured or not?

In many cases it happens that the network card installed in ur PC is not configured properly due to which the
terminal does not connect to the server. To check this u can ping the TCP/IP address of the same PC from the same PC.If the response is received that means the Network card is configured properly.
If u do not receive the reply after ping then it only means that the network card is not configured
properly.Contact ur "Computer Hardware Engineer" to configure the Network card.


Unit comes in the network and goes off the network?
This issue might arise due to various things as mentioned below,pls check and rectify them:

1>The Lan cable is not inserted properly in the RJ45 port.

2>The Lan connector clip is not crimped properly.

3>The broken LAN connector clip, due to which the connector did not get lock when inserted in the RJ45 port.

4>The Existing Network is too busy. In this particular case the solution can be providing a dedicated PC to the device.

If none of the above case is present or even after rectifying the above problems, the actual problem is not getting solved then it can be the problem related to the hardware.

Please contact support Team in that case.


TimeScan is not ping from the server?

Check Following things:

1>Wether the LAN cable is connected at both ends.i.e the LAN cable is connected to server as well as TimeScan.

2> TimeScan must be powered ON.

3> Valid & unique TCP/IP address is given to the terminal.

4> LAN Card of the server is configured properly or not.(This issue can be checked by pinging the same server TCP/IP address from same machine.)


Distance limitation between server and terminal?
Terminal can be considered as PC in a network. Hence all those limitations that are applicable for PC in a network will be applicable to TimeScan .
In case of network, if "Active Hub" is used, the distance upto which PC/TimeScan can be connected is approx. 100mts. In case if the distance between server and TimeScan is more then 100mts, we can connect one more "Active Hub" after 100mts to strengthen the signal.
If a PC is dedicated to TimeScan, distance between PC and TimeScan unit should be as less as possible. TimeScan support 10 Base-T Ethernet network. TimeScan can communicate with max. speed of 10Mbps which is more then sufficient for its data transfer. Most computers today can communicate with upto speed upto 100MBps.
Active Hub should be called standard Switch/Hub
For easy understanding, network administrators should consider TimeScan as any other computer on network.
Also remember that in order to establish communication with BioSecure Remote manager software an extra setting called "Server IP" should be done in TimeScan. "Server IP" means IP address of the server/computr on which BioSecure Remote manager is installed.
Gateway: Gateway should be standard network gateway like used in all your network computer settings. The Server/Computer where BioSecure Remote manager is installed is considered as Server and not as Gateway.


Can we manage the terminal using WAN network? If yes how?


It is possible to run TimeScan in WAN network. Gateway of the TimeScan must be configured properly as per WAN network requirements. If done properly it should be also possible to connect TimeScan on the internet. Firewalls are the major problems as TimeScan uses non-standard ports for communication which might be banned in your firewall.
In case you think you have any corporate networking related issues, you are first suggested to test TimeScan using across over LAN cable directly with your PC. Do not tamper with the unit or network connector, this may damage the unit.