I’ve now duplicated most of that policy’s settings in a new policy on my Server 2012 installation. The policy "Windows SBS Client – Windows XP Policy" opens File and Printer Sharing. This goes back to a group policy that I failed to copy from SBS 2008. I have to admit this was unexpected-when outbound connections are not working, I know to check the firewall on the target computer, but I wouldn’t usually think about checking the firewall on the source computer. Once I opened those ports (137, 138, 139, and 445), MS DTC was immediately able to communicate with the target server and the write transactions succeeded. See MSKB 899115, this StackOverflow question, and this MSDN blog post.) But DNS was okay, and the server’s firewall is disabled, so why couldn’t it get through? Solved: Client Firewall File and Printer SharingĪfter installing WireShark, I finally stumbled onto the problem: MS DTC was not able to use RPC because the File and Printer sharing exception was not open in the client computer’s firewall (Windows XP). MS DTC tracing showed the transaction timing out on the client, but never connecting to the server. The registry change just made it take longer to fail. The primary MSKB article on the first error, 922430, didn’t help. MS DTC also makes sense as the culprit since my app only invokes a transaction, and thus MS DTC, when writing data. “Supplied provider is different from the one already in use.”.“New transaction cannot enlist in the specified transaction coordinator.”.I narrowed this down to an MS DTC issue fairly soon with the help of the messages I was getting: Most things went smoothly, but one issue took a lot of work to resolve: on an XP development machine, I could read from but not write to the SQL 2000 server running on Server 2003. I recently transitioned from SBS 2008 to a clean install of Server 2012 Essentials.
0 kommentar(er)
