Most of my clients are on Novell, but the principles are the same.
First, find out if you can reproduce the problem on a single station,
without any other stations running. I use program that runs a
continuous loop and keeps track of how many passes it does per hour,
sometimes for 2 days (over a weekend). If the degredation occurs when
running off of the server, but not off a stand alone station, you
probably have a network problem (memory leak, intermittent bad NIC,
etc). If the problem occurs on the stand alone station, then try it on
different stations. I know it's tedious, but intermittent problems are
the worst!
PS: Switch back to Novell!
Hope that helps.
Mike
SHARON LIMA wrote:
>
> I frequently get questions from clients who use my application
> in a network environment using R:Base RUNTIME 6.5 for Windows. I do
> not have any training in network issues so I need some guidelines
> to pass on to my clients. Is there a list of suggested settings
> and recommendations for networks?
>
> A current problem that a clients has called about:
>
> They recently replaced their Novell 3.12 network with a Windows 2000
> server network.
> Now to run the R:Base application across the network it is VERY SLOW.
> The confusing
> thing is that it is not always slow. Rebooting doesn't help.
> The only suggestion I gave was to set the FILES in RBASE.CFG to a higher
> number...did not help. They reinstalled the application and the runtime
> file and it worked better for awhile.
> Now it is SLOW again. Two of six computers are fine while the other
> four are SLOW. One of the slow computers is a new PIII-800 while one of
> the faster computers is a Pentium-166.
> They do not feel that it is a network problem because all computers go
> through the same hub.
> The slowness is evident in both starting up the application and then
> moving around and accessing data once started.
>
> Thanks for any help you can give.
> Sharon Lima
