Elena,

At 11:05 AM 27/11/2003 +0100, you wrote:

> >
> > you say "when the user doesn't work with it for a while"
> > does this mean one user only or all users?
> > if you mean the former then I would accuse that user's NIC as the likely
> > problem. if you mean all users start the problem, then I would suspect the
> > server's NIC.
> >
> > Alan
> >
>Hi,
>
>thanks for your reply, but if it's NIC (network interface card), is there
>any solution without buying the new network interface cards and replacing
>them?
>When I wrote "user" I meant any user.
>

The contacts NICs and cable-ends are susceptible to corrosion, especially
in damp environments. If they get bad enough to cause problems, you have
to replace them. They are cheap and most shops keep spare NICs and cables.

However, it's not necessarily corrosion that's causing your intermittent
problems. A "noisy" network will cause the errors you report. For
example, if you have both Windows resource sharing and TCP/IP competing for
bandwidth on the same network and the users are hitting the filesystem or
printers heavily...

I noticed that you mentioned CTRL-ALT-DEL and hitting the OFF switch as
attempted "cures" for your network hangups. You certainly need to get your
house network manager to listen urgently. You are running a high risk of
corrupting your database if you're treating your db server this way.

Also, if an IBX application written for InterBase was ported to a Firebird
database, I wonder if the correct client library is being used in every
case. It would be worthwhile getting each user to search their disks for
leftover copies of the IB client library that may be sitting in their
application paths somewhere.

heLen