Yours,
Andreas Meyer
me...@glamus.de
--------------------------------------------------
GLAMUS Gesellschaft fuer moderne Kommunikation mbH
Auguststr. 1 - 53229 Bonn - Tel +49.228.97617.0
Fax +49.228.97617.55 - Web http://www.glamus.de
--------------------------------------------------
Andreas Meyer wrote:
--
Randy Boback
Omnitech Migrations International
bob...@nbnet.nb.ca
Andreas Meyer <me...@glamus.de> wrote in article
<34E9A03D...@glamus.de>...
If your primary network protocol is IPX/SPX, try changing to TCP/IP.
There's a KB article about this concerning NT 3.51 servers and Win 95
clients, but I suspect it's a problem with NT 4.0 as well.
Regards,
S.Y.
I am considering swapping the protocol back to Netbeui... While we had a
small (2 station) network on Netbeui, this was not an issue...
Could this be a solution?
There was an extensive thread on this problem just a few days ago on
another newsgroup. Search Dejanews for "Disk Network or Human Error
Access" and you should see the entire thread. Cheap unmanaged hubs
contribute to this problem. Check out the thread, if I can be of any
help email me.
--
Steve Johnston
The Access Web ( http://home.att.net/~dashish ) Get yer questions
answered!
Access FAQ http://www.hammerdata.com/Newsgrp/ Right Here Right Now!
http://www.dejanews.com - Ask here first!
http://www.microsoft.com/kb/default.asp You paid for it - Use it!
pssssst! Here spammer spammer spammer
pyr...@ftc.gov, bbr...@ftc.gov, jche...@uspis.gov, fr...@uspis.gov
If you are not using DHCP to set your IP addresses check your machines
LMHOSTS file and your IP addresses in properties for your protocol,
(hopefully Netbeui and TCP/IP with TCP/IP being the default protocol
checked) and make sure that the IP addresses are the correct subnet and
that they match your LMHOSTS file.
You don't mention whether or not you have service packs installed on
your NT Server, Service pack 3 is required for stable performance. NT
had a serious memory corruption problem before SR-1 was released.
>this error (DISK OR
>NETWORK ERROR) , requireing a RECOVERY of the back end in order to continue
>normally, happens from 1 to 10 times a day!!!
I've also heard of a bad network card causing these kinda troubles.
If nothing else works try turning off each work station for a day one
by one and then, if nothing else, move the mdb off the server in case
it's network card is bad.
Tony
----
Message posted to newsgroup and emailed.
Tony Toews, Independent Computer Consultant
The Year 2000 crisis: Will my parents or your grand parents still be receiving
their pension in January, 2000? See www.granite.ab.ca/year2000 for more info.
Microsoft Access Hints, Tips & Accounting Systems at www.granite.ab.ca/accsmstr.htm