Hello - I have sucessfully deployed DFS across two w2k3 R2 servers and was\nable to replicate and verify using diagnosic report that data is present on\nboth target paths.\n\nWhen I now try testing failover by removing primary & active target DFS\nserver and then writing a file to the DFS share I get a BSOD ( blue screen of\ndeath ) pertaining to mup.sys and DFS at address 0xB9DEC894, 0xBDED424,\n0x00000000, 0x00000000. I restarted my windows XP pro system that BSOD'd and\nreconnected the primary system. When I check the DFS info on\n\\testcompany.local\share it says that the active target is now the server\nthat was just reconnected. If I check failover by simply disconnecting the\nactive target and looking at DFS info for the share, I do see that the active\ntarget changes. I now can not write files to either active target. Each\ntime I do I get the same BSOD. I saw an article that mentioned the length of\nthe last component being longer than the DFS share and tested it by trying to\ncreate a file 1.txt and got the same BSOD.\n[URL]http://support.microsoft.com/kb/899856[/URL]\n\n\nAny idea's would help.\n\nAlso, the inital data was on the server in a standard share before I created\nthe DFS namespace if that means anything.