filePro network problem

[Steve Wiltsie]

I have a customer I've been working with for many years through various
operating systems and network configurations.  A few months ago they
purchased a new Nobilis all-Intel Xeon file server running Windows 2003
Server to replace a 4 or 5 year old Nobilis all-Intel Windows 2000 Server.
The conversion from one to the other was done over a weekend and by the next
Monday morning they were up and running.

Shortly after the new server was in place, a couple of the newer Dell XP Pro
workstations started getting error messages such as:

**A System Error Has Occurred** /filepro/filename/key: Bad file number

A System Error Has Occurred, Automatic Processing Line Number : 27, lookup
comp =filename r:rn-e, Error Number -1, Windows error #64, The specified
network name is no longer available.

 ***A System Error Has Occurred*** Fatal Error, /filepro/filename/index B:
Error -1, Windows error #64: The specified network name is no longer
available

These error messages can come during idle times or while they are actively
entering records.  The 2 Dell PCs are used more than any other PC on their
network to access the filePro applications.

To try to fix this problem over the last 2-3 months, I have done the
following:

updated the Intel network drivers on the server (more than once as newer
ones are released)
switched to the second network adapter on the server
updated the firmware in the server
updated the BIOS in the Dell PCs from A00 to A08
installed a PCI network adapter in one of the PCs as a test - same problems
connected the 2 problem PCs and the server with new Cat 5e network jumper
cables
replaced the 10/100 network switch with another one - twice
replaced the 10/100 network switch with a 10/100/1000 switch - the errors
just come faster
removed spyware and adware from the 2 PCs
reformatted and reinstalled XP Pro on the PCs from the recovery disks and
ran all Windows Updates
loaned them a new Nobilis XP Pro PC for a week - no network connection
problems with it
contacted Microsoft for a patch mentioned in a KnowledgeBase article with
these errors as part of the text - the patch files were older than the ones
in the system and the problem was supposed to be fixed already

none of these things have fixed the problem with the 2 Dell PCs.

At this point, the customer thinks I am an idiot for selling them a new
server that has these problems.  I have lots of customers running the same
version of filePro 5.0.x on XP Pro systems from a similar Windows 2003
Server on a 10/100 or 10/100/1000 network with no problems at all.  I really
don't think it is the server but something that loads on the Dell PCs or
something else on their network - they are a county agency and the switch in
their office is connected to the overall county office network.  The county
network guy puts his own anti-virus software on the PCs even though they
ordered the server with Symantec A-V Corporate Edition.  He also loads
something called Log Me In, or something like that, which I assume is
similar to Remote Desk Top or PC Anywhere.  Have you heard of any issues
with that program and Dell PCs?

My next plan is to put an add-in network card in the server and move them
back to the 10/100 network switch but after that, I'm pretty much out of
ideas.   Do any of you network gurus have a suggestion on what else I might
try?

Thanks and Merry Christmas,

Steve Wiltsie
microCONCEPTS Div. multi/user/inc.        Since 1981
(812) 474-0127                          Fax: (812) 474-0147