Vista is running slowly on multiuser app (Pdox9 RT)

#1

Greetings, all.

I've got a problem running Vista (shocker!), using Pdox 9 Runtime sp3. On
a 2 computer network, with both running Vista, my app runs great as a single
user from either machine. As soon as the second one is started, however,
the 'client' workstation slows to a near lockup. The 'server' (which hosts
the data) also slows, but not as dramatically.

I've run Ethereal's network monitor, and the Vista performance monitoring
tools, and while the slowdown is happening, there isn't an obvious cause
- no resources are pinned at 100%, and very little network traffic is happening.

To me, it seems like there is some sort of delay built into the file sharing
or locking, but that's just a WAG.

Does anyone know of a magic bullet to speed up Vista? I checked all the
old XP tricks - no offline printers, etc., but could not speed it up.

Note that I have hundreds of clients running all previous versions of Windows
without a problem.

TIA,
Jim Moseley

#2

I would first look to turn off oplocks and disk caching, if possible.

Just a guess.

Liz

Jim Moseley wrote:

Quote:

Greetings, all.

I've got a problem running Vista (shocker!), using Pdox 9 Runtime sp3. On
a 2 computer network, with both running Vista, my app runs great as a single
user from either machine. As soon as the second one is started, however,
the 'client' workstation slows to a near lockup. The 'server' (which hosts
the data) also slows, but not as dramatically.

I've run Ethereal's network monitor, and the Vista performance monitoring
tools, and while the slowdown is happening, there isn't an obvious cause
- no resources are pinned at 100%, and very little network traffic is happening.

To me, it seems like there is some sort of delay built into the file sharing
or locking, but that's just a WAG.

Does anyone know of a magic bullet to speed up Vista? I checked all the
old XP tricks - no offline printers, etc., but could not speed it up.

Note that I have hundreds of clients running all previous versions of Windows
without a problem.

TIA,
Jim Moseley

#3

Since this is peer-to-peer...

What protocol does Microsoft have you running?

Do you use a hub or switch?

--
------------------------------
Tony McGuire

#4

Tony,

Quote:

What protocol does Microsoft have you running?

Not at the computers now, but think it had tcpipv6 for local & tcpipv4 for
net. also had 2 discovery(?) protocols so comps could be seen on network.
finslly, on the adapter properties, i think it mentioned 'netbios over tcpip'
being active.

Quote:

Do you use a hub or switch?

Not sure, it's a remote client's computer I logmein.com'd into.

Thanks,
Jim Moseley

#5

Virus scanner?

It sounds like a timeout of some kind to me.

Jim Moseley wrote:

Quote:

I've got a problem running Vista (shocker!), using Pdox 9 Runtime sp3. On
a 2 computer network, with both running Vista, my app runs great as a
single
user from either machine. As soon as the second one is started, however,
the 'client' workstation slows to a near lockup. The 'server' (which
hosts the data) also slows, but not as dramatically.

I've run Ethereal's network monitor, and the Vista performance monitoring
tools, and while the slowdown is happening, there isn't an obvious cause
- no resources are pinned at 100%, and very little network traffic is
happening.

To me, it seems like there is some sort of delay built into the file
sharing or locking, but that's just a WAG.

Does anyone know of a magic bullet to speed up Vista? I checked all the
old XP tricks - no offline printers, etc., but could not speed it up.

Note that I have hundreds of clients running all previous versions of
Windows without a problem.

----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com

#6

Quote:

Virus scanner?

It sounds like a timeout of some kind to me.

They don't have a virus scanner active, nor a firewall.

I agree that it sounds like a timeout. The strange aspect is that it works
great from either machine as a single-user, even though it is pointing to
the same data. It is only when 2 users are in at once that it slows to a
crawl - like 20 minute response times at least! Something's got to be hanging
the file locking.

Here's what I've tried so far, to no avail:
1. Turn off indexing.
2. Turn off Remote Differential Compression.
3. Turn off Windows Defender on my :work: &

riv: folders.

Haven't tried yet:
1. Remove TCPIPv6.
2. Turn off TCPIP auto-tuning via 'netsh interface tcp set global autotuninglevel=disabled'
3. Turn off Windows Defender completely

So, if anyone's got any good ideas, let me know!

Thanks,
Jim Moseley

#7

How about wayward printers?

Any showing that aren't actually there?

------------------------------
Tony McGuire

#8

Tony,

Quote:

How about wayward printers? Any showing that aren't actually there?

Nope, I've run through all the WinXP tricks already.

I had a similar problem when I first started using XP. It would take forever
to run over a network. Using Ethereal, I found out the opening a form like
'f.open("form1")' would cause it to search the entire directory for 'form.'.
Then, it would do it again for 'form.fdl', and finally 'form.fsl'. I changed
all my code to use the extension (fdl then errorclear & fsl) and it worked
great.

Unfortunately, in this case, I'm not seeing a lot of network traffic in Ethereal.
It just seems to sit there waiting on something. Every 120 seconds or so,
I see '[TCP Keep-Alive] NBSS Continuation Message' followed by an ACK.

Thanks,
Jim Moseley

#9

On 28 Jun 2007 00:32:22 -0400, Jim Moseley wrote:

Quote:

Virus scanner? It sounds like a timeout of some kind to me.
They don't have a virus scanner active, nor a firewall.

Malware. I bet it's malware. Some sort of Trojan or keyboard logger.

I have examined a dozen or so SOHO networks without adequate protection
(three to five stations, p2p, everyone on it completely clueless). All,
without exception, were clogged with serious malware. We ain't talking
tracking cookies here -- we are talking Trojans, loggers, viruses,
hijackers installed and running *simultaneously*.

Of course that was XP Pro, and Vista is supposed to prevent this natively.
Then again, XP Pro was supposed to prevent this natively.

My 2 cents,

Jim Hargan

#10

Jim,

Quote:

Malware. I bet it's malware. Some sort of Trojan or keyboard logger.

I don't think so. It was like this right out of the box. These are brand
new machines that haven't worked right since day 1. But, you make a good
point, so I'll have them check.

There's definitely some setting in Vista that doesn't like sharing.

Thanks,
Jim Moseley