Some commenters, and possibly the author, want this advice to extend to job interviews, but the reason an interviewer is pushing you to answer a question isn't that they want you to be right or wrong. A good interviewer wants to get a look into how you think and how you approach a problem. An even better interviewer will make that clear, by telling you "there's no trick here", "I don't know the answer myself, let's s…
I am not convinced that throwing INTERCAL at a candidate is a good way to roll. ;)
But seriously, I think that you are spot-on with this approach. Interviewing, done effectively, is about getting a fleshed out idea of the capabilities of the candidate, not just getting correct answers. Perhaps the best response to give or expect, when the interview gets stuck, is "I don't know, but..." Even on questions that aren't coding questions, these are often good responses: "I don't know, but [this is how I would find out]" or "I don't know, but [this is a topic or problem that I believe is related]" .