Access97 error 3043 "Disk or Network error"

[sasha0]

Recently I did migration from NT4 to 2003 Server. There are Access97 databases shared on this server. Since the migration users running Access97 from thin terminals started to get error 3043: "disk or network error". The same error I got when try run from console NT4 terminal server. It's never happens from 98 or XP stations. All other applications are OK. Looks like nona seconds disconnactions which affect Access97 only cause this problem. Anybody knows how to fix this problem?
Thanks,

 

[N0ktar]

Were you getting the same error during 2003 server testing phase before the migration?

 

[sasha0]

We tested it with one user and it was OK. But in reality we got 20 terminal users simulately connected and using access97 database

 

[N0ktar]

This happens because of bad network connection, sometimes when you ping from remote machine you will be able to ping. Hence network connection is established. But actually the network/communication connection is either loose or not able to connect for some nano seconds.

You may try replacing the NIC and most of the time this works out, just check for any network problems.

 

[sasha0]

I have already read this from forums. I've got installed brand new DELL server PowerEdge 2900. I called to their support team and they ran all tests on Broadcom network cards (there are two built in work as team) and they did not find any problem with connectivity.

 

[tordoffm]

Have you checked your Duplex settings - both on your network deivces and within the Teaming Software?
I'm sat on a 100/Full network, and HP Teaming has randomly changed to 100/Half - until we noticed, it caused all sorts of connection problems - randomly - and more often than not, only under a higher load.
Reset to 100/Full - and as if by magic, there have been no problems since...

 

[sasha0]

I have already broken the team connect only one adpter to different switch 100Mb Full but the same problem. From My observation only terminals who connected to NT4 terminal server got this problem.