Posted 25 August 2008 - 04:16 PM
This is a weird one...
We have a server offering peer-peer file-sharing to three workstations (it's also a workstation, but that doesn't seem to be an issue). All computers are XP Pro, all SP2. Of the three workstations, two exhibit the problem, and one does not. (Actually, it gets worse: of the two with the problem, one was okay, but the P/S went slowly south and screwed up the HDD; a new P/S and HDD were installed and Win XP Pro (re)installed, by local store - also it was upgraded to SP3 while they were at it... with the result that it now also exhibits the problem.)
And the problem is... in a fairly complex piece of accounting software (special, for County Treasurers) written in Cobol, in only one part of one module (payroll), when it opens and also when it exits the payroll data update/inquiry, it takes 60-90 seconds to do so. Once it's in, it's plenty fast, no problems. This, mind you, is on two of the workstations, but not the third. I've examined the RunCobol.exe installation on all three, and it appears that the files are identical and the registry entries are identical. All three have identical properties in their access icons - all three point W: at the server by IP address (i.e. net use w: \\192.168.127.41\apps1 persistent:yes) and all three run the app from their own C: drive while starting in w:\data).
As far as I can see, there isn't any extraneous disk thrashing going on, no wildly blinking lights on the LAN.
I've moved computers around physically, and I'm pretty certain there's no issue with router, switch, or cables.
I've tried it with and without Windows Firewall and with and without the A-V software running.
I checked the services and found two with different settings on the two "bad" computers than on the "good" one, but changing them had no effect (I can't tell you what they were right this instant - my journal is in my bag in the backseat of my car and rain is pouring down...
At this point, I'm pretty sure it isn't a hardware problem, and it shouldn't have anything to do with viruses; I don't think it's a setup problem in the app. I'm fairly well convinced it's some Windows setup issue, tcpip buffer sizes or whatever, but I'm out of ideas... other than seeing if there's some straightforward way to profile the (*&@#$ thing so I can get some handle on what the &*$#% is going on!
How about it... anyone?
Edit: Moved topic from XP to the more appropriate forum. ~ Animal