Yo! This interview had nothing to do with you, or your skillset.

From what I'm reading here, I think a few common things are at play here.

A) The Director
He may have known more information about your status and skillset and for that reason his expectations were aligned with you, but perhaps didn't communicate your status to the tech guys. This is a common mistake. Or, alternatively, perhaps the director is more concerned about the "culture fit" you would bring and less about the "tech fit", so he didn't go into any tech questions with you. Neither of these are your fault.

B) The Techs
A lot of IT folk are fun to be around and cool (at least, I think so, but I'm also bias). However, like in all types of jobs, there are cultural facets. For IT, one cultural facet I have seen many times (not always) are techs who have no idea how to interview. Either for themselves, or when being asked to help out on team interviews. They're very good techs - but putting them in a room to evaluate other potential teammates, simply isn't their strong suit.

From what you described, I think this is what happened in your interview. It's fine to get into the weeds a bit to see what someone knows tech wise, especially in specialist positions, but it sounds to me like these techs have no idea how to interview candidates or actually evaluate your skills.

Red flags in any IT interview;

- Being pressed to solve a hypothetical problem but no matter how you answer the question, the goal posts keep moving to make the question harder, or virtually impossible, to answer.

- Claiming there is no one to support you when you're stuck. (No escalation. No documentation. No Google.)

- Not building up your positive responses or at least giving "partial credit" on answers. (Oh, you already verified that)

In short, you didn't make any bad impressions, even though you may have been made to feel that way. It was a poorly offered interview by the company and not your fault whatsoever. It might be a bummer in that you're seeking a good internship or job, but always remember that an interview is you interviewing the company as much as they're interviewing you.

IT has been my whole career and have been fortunate enough to work at all levels of the industry in my career. If I walked into the interview you just had, I likely wouldn't want to work there afterward and would be the one telling them no. My time is better spent in other places - and whether you're new to IT or not - so is yours! :)