Qualcomm interview questions

The recruiter had set up for 2 telephonic interviews back to back. The first one was a managerial interview where the person introduced about the kind of work available to me if they hire me. The second was a technical interview. The questions were put up based on the stuff in my resume. They were related to TCP/IP, OS, everything. Also a questions based on memory access was posed.

I had a phone interview for the same area. The first question was about my clearance and how long it was good for. The next question was to tell about myself and my job history. Next they dived into each job and asked me to explain the highlight of something I accomplished (some technical adversity and how it was overcome). They then asked about the purpose of vlans, the difference between a switch and router (Layer-wise), firewall questions, how to detect protocols, different ways to monitor a network (passive vs active), subnetting (need to study up on that - usually use a calc), programming experience (vbscript/wmi for ntwk admin stuff), had I ever had to deal with an angry customer and how I handled it, had I ever had to influence a decision and give an example, how to change a local machine password in AD 2003, how to change a dynamic account in AD 2003, what variables could be changed on an account by a sysadmin, what was the difference between a static address and dynamic address, descript dhcp and how scopes work, describe dns, how many DC's can be on a network (ans: infinite - however I pointed out that you want to limit it due to the overhead that each DC would use on the network), how to map a printer, how to promote or demote a DC (dcpromo), what fsmo (pronounced "fizmo" is (something about flexible services - not sure). That was my phone interview. There were more questions but I don't remember all of them. I know it lasted about an hour of me pacing back and forth. My onsite interview is Wednesday and I'm really nervous. I've been in the Navy for almost 20 years, and I'm more a jack of all trades than a specific area. I've had to learn new things for each facet of my job, then dump it to learn something else. I'm good at someone giving me a problem and telling me to figure it out, as long as I have the resources to do it (internet, library, hands-on). So I'm probably going to fail the onsite interview but I'll take out of it quite a bit as far as the questions and how qualcomm is ran. So far everyone that I've dealt with has been very professional and even pretty friendly! Even if I don't get the job, it will be a GREAT learning experience. I'll post everything I can remember from the onsite that I learn in hopes that it will help someone here get the job.