WDS over VPN

Så fandt jeg en løsningen, og ville blot informere om hvad løsningen var, da jeg har skamsøgt nettet uden at finde noget svar på problemet, men mange der havde det.

Im gonna write the next part in english, since this is a world wide problem, and i have seen lots of people having this problem, but no one had a solution.

The problem was regarding WDS, and PXE boot, over VPN. Because of the VPN ipsec headder, the packages got too big, for the MTU, which ment the packages got fragmented. This was caused by a microsoft update, that changed the default MTU from 512 to 1456. And that the PXE client does not support assembling of fragmented packages.

To resolve this issue, i had to make sure the packages wasnt getting fragmented, due the MTU.
I was not able to solve this, untill i found this HOTFIX from microsoft
http://technet.microsoft.com/en-us/library/cc731245(WS.10).aspx#BKMK_41

Call microsoft and get them to send the hotfix to your mail.
After applying the patch, remember to add the Dword key in the regedit, as described in the microsoft link above.
After you have added the regestry key(I used 1410 Decimal value, since that keeps it just under the mtu), restart the WDS service or restart the server.

You should now be able to PXE boot on your client.
I hope this have ben informative for you.

KEYWORDS:
WDS OVER VPN (Solution above)
PXE OVER VPN (Solution above)
WDS FRAGMENT ISSUE (Solution above)
WDS BOOT OVER VPN ISSUE (Solution above)
PXE BOOT VOER VPN ISSUE (Solution above)
WDS FRAGMENT PACKAGES (Solution above)

WRONG LINK!!!!!
This is the right one!

http://support.microsoft.com/kb/975710

Sorry!