传统FOXPRO应用程序无法正常工作2012r2 DC将被引入2003功能域 [英] Legacy FOXPRO App not working once 2012r2 DC's are introduced to a 2003 functional domain
问题描述
我们有一个Windows 2003的功能域，其中包含3个域控制器和2个通过WAN链接连接的站点。我们的遗留应用程序位于站点A中的某些2003终端服务器上。
We have a functional domain of windows 2003 with 3 domain controllers and 2 sites connected by a WAN link. Our legacy application sits on some 2003 Terminal servers in site A.
站点A：192.168.23.0网络
Site A: 192.168.23.0 Network
ZDC01 - （PDC - 架构 - 域命名主人）
ZDC01 - (PDC - Schema - Domain Naming Master)
ZDC02 - （RID - 基础设施）
ZDC02 - (RID - Infrastructure)
网站B 192.168.20.0网络
Site B 192.168.20.0 Network
ZDC03 - （没有角色）
ZDC03 - (No roles)
使用上述配置一切正常
我在网络中引入了2个新的2012r2 DC
I introduced 2 new 2012r2 DC's into the Network
网站A：
YDC04 - （无角色）
YDC04 - (No roles)
网站B：
YDC03 - （没有角色）
YDC03 - (No roles)
我做了一些测试，一切似乎都很好。 5天后，遗留应用程序停止工作。用户报告他们可以登录到终端服务器，但旧的遗留应用程序停止工作。遗留应用程序基于
fox pro （win32应用程序），可能是10到15年（在我现在工作的公司之前建立）。我们控制登录以及用户可以看到的内容以及他们可以通过NTFS安全权限访问哪些数据。
I did an amount of testing and everything seemed fine. 5 days later the legacy application stopped working. Users reported they could logon to the Terminal Servers but the old legacy application stopped working. the legacy app is built on fox pro (win32 app) and is probably 10 to 15 years old (built before my time at the company I now work for). we control the logon and what the user can see and what data they can access via NTFS security permissions.
我们一旦关闭了站点A中的新DC： - YDC04 - （没有角色）.......网站B： - YDC03 - （没有角色）。该应用程序栩栩如生，我们已经没有问题了（只要新的2012r2 DC关闭了）
As soon as we switched off the new DC's in both Site A: - YDC04 - (No roles).......Site B: - YDC03 - (No roles). the application sprung to life and we have had no more problems (As long as the new 2012r2 DC's are switched off)
我理解我对遗留应用程序没有太多帮助，但是我自己也不多。
I understand Im not giving much away with regards to the legacy application, but I dont no much about it myself.
我现在希望有人在technet土地上提供建议。
Im now hoping someone out there in technet land can offer advice.
干杯
Lex
推荐答案
您应该更多地报告正在发生的错误，但是关于从2003服务器切换到更新的问题的原始信息，如oplocks问题，SMB2或更高版本的网络协议引入了性能提升缓存策略，但它
不适用于DBF和Access dbs。而2003年是最后一台只有SMB1的服务器操作系统。
You should really report more on what errors are occurring, but the raw info about switching from 2003 server to something newer smells like a oplocks issue, SMB2 or later network rotocols introduced that as performance raising caching strategies, but it doesn't work well with DBFs and also Access dbs. And 2003 was the last server OS with SMB1 only.
您可以关闭oplocks，但需要切换到SMB1，这对今天来说不再是个好主意。您最好的选择是通过调低缓存时间来间接转换该功能以最小化其效果，主要是：
You would switch oplocks off, but need to switch to SMB1 and that's not a good idea anymore, today. Your best option is to indirectly turn that feature down to minimize its effect by turning down the caching time, mainly:
[HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet \services \ LandmanWorkstation \Parameters]
" FileInfoCacheLifetime" = dword：00000000
" FileNotFoundCacheLifetime" = dword：00000000
" DirectoryCacheLifetime" = dword：00000000
这将需要应用于运行该foxpro应用程序的所有客户端。其中客户端也表示终端运行传统foxpro软件的服务器。
This will need to be applied for all clients running that foxpro application. Where client also means the terminal servers running the legacy foxpro software.
作为旁注：谁在运行2003年服务器到2017年？一个非盈利组织？
As a side note: Who's running 2003 servers up to 2017? A non profit organisation?
Bye，Olaf 。
Bye, Olaf.
这篇关于传统FOXPRO应用程序无法正常工作2012r2 DC将被引入2003功能域的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
