Actually, I'd probably let the players just do what they want - if they know where Cragmaw is and want to go right to it, more power to them.
But I would do two other things. First I would also take a look at the threat level of the encounters in the castle and compare it to where they are. And if they're substantially below the power level I think would be needed to hit the castle, I'd try to find a way to telegraph that to them. In game by making sure that the first encounter is actually representative of the rest of the encounters they'll be seeing (i.e. if it's an easy one comparatively, make it tougher), or out of game by saying "guys, just FYI - the castle is pretty difficult and assumes you'll have leveled up on some of these side quests" (it really depends on the dynamic of your group and what they prefer at the table). If after being telegraphed that it's really damn hard they keep pushing anyway, well, that's D&D - TPKs are part of the game - but chances are a tough first encounter will have them scurrying back to build up their power level a bit before coming back.
Which leads into the second thing I would do, which is take a look at the player and character motivations for your group and try to fold, spindle and mutilate the side-quests into things that either the player would want to do or that the character would want to do. If they're not the "heroic" type then maybe they're the "mercenary" type - have someone pay them to go do one of the side quests. Or if they're the greedy type, spread some rumors of magic items around and see if they bite (I might even throw an extra magic item into the side quest to pay off one of the rumors, because hey why not? It makes it easier to lead the PCs where you want them if they think there's a good chance of a magic item they might want at the end, and if you never pay out they'll stop biting at the bait). This actually works pretty well with the "scare them with a tough encounter" tactic above, because that can lead to "ok, the castle is too tough - but there are rumors of a magic sword/armor/whatever over here, and maybe if we find that we'll be able to tackle the castle" and that again makes it their decision to go off and do it instead of just a plot hammer.
This attacks the "problem" from two places - it has the potential to turn the side quests into character-driven events instead of plot-driven ones, and it lets the players feel like they're making their own decisions with good information in front of them and have a narrative reason for delaying the frontal assault that they could have done right after chapter 1.