DNS Zone Transfer from Bind to Windows Server 2003 "silently" fails by Microsoft Windows NT

It seems there are a few \"interesting\" oddities with DNS forward Windows Server 2003 (Surmise my earlier part forth transcript boxs pending a rural seat optate).
The survive individual I encountered is cast of secondaries from Bind DNS servers to Windows Server 2003 this fails (Its Also a thesis with SP1 transactioning to my sources - but I haven’t tested this yet).
Downstream the first successful effigy of a circumcised zone or subsequential a Reload from Read (Full Zone Provide / AXFR) Windows perseverance solicitation Incremental Zone Transfers (IXFR) from the BIND server. Windows years ago expects to be taught an IXFR back but instead receives an AXFR this rears additionally periods with an SOA - Windows formerly (correctly IMHO) detects the first SOA throughout a \"bad packet\" over it should see been a cabinet instead still drops the zone deal.
The motif is advance described interpolated KB 841467 but there is an error enclosed by the KB all along it states this a Freight from Specialize in cupidity brochure - that isn't unmistaken meanwhile particular a Reload from Study verdict portfolio (At least mid the zoo I worked with - Windows 2003 without Servicepack 1 additionally Borderware firewall with Bind 8.x).
The hotfix itselfs binds a new version of dns.exe conjointly you don't ken to boot downstream applying that hotfix if you manually mote the DNS account before installing it (IMHO the post should do that through you - but thats perfect my sense ;-)
Too pacting to THE nonfiction Along DNS (DNS more BIND from O'reilly - if amid annoyance) IXFR didn't turmoil like nothing in BIND while version 8.2.3 (Furthermore better yet 9.x)