Issue with batigest network
Khwandj
-
Khwandj -
Khwandj -
Hello,
I currently have a network with a Livebox Pro and static IPs for my three computers.
To work more easily and simultaneously, we opted for a network setup of the Batigest software.
This software is installed on all workstations and the database is located on a networked hard drive.
The main computer runs Windows Vista while the others are on Windows XP.
The network drive is directly managed by the main computer (internal disk) and the two other workstations are connected either via Wi-Fi (laptop) or via Ethernet (workstation 2 as the main workstation).
Today, a problem arises because as soon as we launch the application on a workstation different from the main workstation, we are ejected from the network and lose all communication with the network drive after a few minutes.
I would like to know if this is due to Batigest or to Windows and its countless various problems.
Khwandj
I currently have a network with a Livebox Pro and static IPs for my three computers.
To work more easily and simultaneously, we opted for a network setup of the Batigest software.
This software is installed on all workstations and the database is located on a networked hard drive.
The main computer runs Windows Vista while the others are on Windows XP.
The network drive is directly managed by the main computer (internal disk) and the two other workstations are connected either via Wi-Fi (laptop) or via Ethernet (workstation 2 as the main workstation).
Today, a problem arises because as soon as we launch the application on a workstation different from the main workstation, we are ejected from the network and lose all communication with the network drive after a few minutes.
I would like to know if this is due to Batigest or to Windows and its countless various problems.
Khwandj
3 réponses
Same problem with Batigest on a 2008 server and 3 clients accessing it on XP.
After a few minutes, the client computers can no longer communicate with the server!!!
After a few minutes, the client computers can no longer communicate with the server!!!
Good evening,
We have been using the Apibat Batigest PME, Financier, Compta products for many years, and we have developed software related to these products.
In the company where I work, we have 20 Batigest PME users with a 900 MB database. The problem you describe resembles an issue we encountered in our early days.
Several points need to be checked:
_ screensavers must be disabled
_ the power-saving modes for network cards must be disabled
_ the power-saving modes for hard drives must be disabled
_ Check the power management settings on your client workstations
_ Disable power-saving modes or energy-saving settings on network hard drives.
Otherwise, another option is to try installing the executable on the network drive and point your client workstations to it.
If you receive a Batigest error message, please let us know.
We have been using the Apibat Batigest PME, Financier, Compta products for many years, and we have developed software related to these products.
In the company where I work, we have 20 Batigest PME users with a 900 MB database. The problem you describe resembles an issue we encountered in our early days.
Several points need to be checked:
_ screensavers must be disabled
_ the power-saving modes for network cards must be disabled
_ the power-saving modes for hard drives must be disabled
_ Check the power management settings on your client workstations
_ Disable power-saving modes or energy-saving settings on network hard drives.
Otherwise, another option is to try installing the executable on the network drive and point your client workstations to it.
If you receive a Batigest error message, please let us know.
Hello,
Thank you for the help provided.
According to my information, the current version of Batigest installed (version 6) is incompatible with Vista and 2008 Server. We will need to migrate to version 7.
Indeed, previously, with the same configuration but with Windows XP as the server, there were no issues. After switching from XP to Server 2008, network disconnection problems have arisen.
Best regards,
Thank you for the help provided.
According to my information, the current version of Batigest installed (version 6) is incompatible with Vista and 2008 Server. We will need to migrate to version 7.
Indeed, previously, with the same configuration but with Windows XP as the server, there were no issues. After switching from XP to Server 2008, network disconnection problems have arisen.
Best regards,
Thank you for all this information. As I thought, whether or not being on a network makes no difference, and the idea of installing the executable on the server is a problem due to the fact that the server is nothing but a network hard drive.
After trying the various solutions, I can conclude two important things:
- For Batigest and any software from the APIBAT collection, you should not use computers running different versions of Windows.
- Version 6 of Batigest is not designed to work on Vista, as I set up another network solely based on computers running XP, and the problem does not arise.
However, a solution exists because I implemented it in the company: you should not operate as a network drive with all the files but only share them over the network.
With this solution, the network is more stable because it does not operate on virtual drives, and the connection/disconnection problem no longer exists (if there is nothing to disconnect, it won't do it!!!).
One more thing to clarify, if you are on Vista, you must specify who has access to what and in what way; otherwise, it leads to problems regarding network sharing (data and hardware).
Today, my three computers work perfectly well on the network, but this file sharing solution is only a temporary fix because it is unmanageable beyond three computers!!!
Best regards
After trying the various solutions, I can conclude two important things:
- For Batigest and any software from the APIBAT collection, you should not use computers running different versions of Windows.
- Version 6 of Batigest is not designed to work on Vista, as I set up another network solely based on computers running XP, and the problem does not arise.
However, a solution exists because I implemented it in the company: you should not operate as a network drive with all the files but only share them over the network.
With this solution, the network is more stable because it does not operate on virtual drives, and the connection/disconnection problem no longer exists (if there is nothing to disconnect, it won't do it!!!).
One more thing to clarify, if you are on Vista, you must specify who has access to what and in what way; otherwise, it leads to problems regarding network sharing (data and hardware).
Today, my three computers work perfectly well on the network, but this file sharing solution is only a temporary fix because it is unmanageable beyond three computers!!!
Best regards