>Hello any help will be greatly appreciated.,
>
>Dell server: PowerEdge 2900
>Dual Xeon Quad Core CPUs 2.66Ghz
>8Gb RAM
>Storage: 4 SATA 500gb drives configured as single volume via RAID5. Two partitions: system & data
>
>OS: Microsoft Windows Server 2008 Standard x64
>NIC: Intel EXP19402PTBLK 10/ 100/ 1000Mbps PCI-Express Two Gigabit Copper Server Connections – OEM
>
>Network Switches:
>Dell PowerConnect 2724 Managed Gigabit Switch (10/100/1000 24-port switch currently configured as UNMANAGED)
>
>also
>
>Linksys EtherFast 4124 Network switch, EF4124 (10/100 24-port unmanaged switch)
>
>Clients get an error reading from a shared drive that all workstations are mapped to, and then the workstations screens go blank and the VFP app hang and they have to reboot the server.
>
>The same application was running on Windows 2000 without any problems.
>
>They are accessing the application and data via Terminal Services as well.
>
>Unfortunately, I'm having a tough time understanding the Dell tech's description due to his accent, but he's indicating something about when the VFP application fires up their having problems with the share ...
>
>I haven't been able to get in via WebEx or LogMeIn to view the problem directly.
>
>I guess the first question: Is VFP 9 SP1 compatible with Windows Server 2008 running in 64 bit mode?
>
>Second question, has anyone had any problems running VFP 9 SP 1 with 2008. Anything I should look at with the above hardware configuration?
>
>Our app isn't doing anything special, just running in a normal local area network configuration, with the same app being run by all workstations (ie, the app isn't residing on the workstation, it's located on the network file server).
>
>They claim that there isn't any error message thrown on the server or the workstation.

Was this just a server replacement (Windows 2000 to 2008), or was other infrastructure replaced/upgraded as well e.g. wiring, switches, client computers? IOW are you reasonably sure it's related to the server, or could it be something else?

I'm kind of surprised they'd need to reboot the server once your VFP app crashes. Can you elaborate why?

You say "workstation screens go blank" - this should not happen with a desktop app. Could it be that's what just the TS users are seeing? (that would be believable)

One potential cause of problems like this is antivirus software. Is it possible, at least for test purposes, to configure AV on the server to exclude your application and data files from real-time scanning? For testing you could do the same on the workstation(s), or temporarily turn it off completely.

Also, if there is any 3rd-party firewall in place e.g. as part of a security suite on workstation(s), try disabling that as well.

In the header of this message it shows your workstation OS being XP. If it were Vista, that might be defaulting to SMB2 rather than SMB for communicating with the server. Early in Vista's history it had significant problems working with flat-file databases such as VFP and Access over SMB2: http://support.microsoft.com/kb/935366/en-us I don't know whether all issues with SMB2 have been fixed.

Ref: http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm

VFP strongly stresses LANs. If there is any weakness or misconfiguration, it will likely manifest itself as a problem in a VFP app. If you don't find an easy, obvious problem, you may need to do a full audit to make sure all hardware and software are functional and properly configured.