network environment, best practice?

[deepwater]

We have a custom FM app running on FMSA9 on a Dell PowerEdge 1950 Win Server 2003. The network consists of point-to-point redundant T1's from ATT. The server sits 100 miles away on the same subnet, everything static.

Im getting data corruption and weird behavior with status icons not showing up, reports not printing to PDF that did... This is a system under development, so were not live until issues are crushed. Currently we have 5 users accessing the sys.

The Developer is saying their solution needs to be accessed via Terminal Services. I called FM support and they said our setup should work just fine.

Is this a situation where the custom app is not conforming to standards within FM or just the nature of FMSA applications?

Our old DB is running on FMS5.5 on a Mac. Ive had not one issue in 13 years. well maybe one.... someone plugged in a carpet cleaning machine and tripped the circuit.

Thanks!

[Wim Decorte]

Do you have the full T1 bandwidth to yourself or is it shared? What about the rest of the network? T1 to the closest backbone node, then the cloud then T1 again to the endpoint? Did you do any latency testing on the circuit? Bandwidth testing?

Starting with FMS7 FMI made significant improvements on the bandwidth usage but the communication between FMS and FMP is still very intensive. Any latency or dropped packets will create problems.

A terminal server / citrix deployment is much better in this respect since the latency or dropped packets will only affect screen display and not data communication.