Several comments:
Sometimes, it's not about what you've done at past jobs, it's about how you present what you did. If your job was at a fortune 100 company re-imaging PC's, you could say "Provided client restoration services via XXX wide area network / metro area network". If you answered tech support for an ISP, you "provided network support services for thousands of customers".
Certs are good and all, but there's nothing to beat experience. Decide what you want to focus on and try to find something that will take you there.
Networking is a huge, diverse field that means something different to everyone. I still consider myself a network guy, but my main responsability is providing infrastructure architecture services with emphasis on web traffic flow, proxy services and load balancing for a big bank. There's lots of guys with great experience on here in small-to-medium sized companies that are responsable for their whole infrastructure - routers, switches, servers, firewalls, messaging, file services, databases, the works. Then, you have the PURE network guys (Like Spidey) who do almost nothing but switches and routers, with a few firewalls thrown in for fun.
Decide what you like and go from there.
One piece of advice - If you can find a reseller or system integrator to work for as an engineer it's a fun job. It can be long hours, but you'll learn 10X more (about TECHNOLOGY) than you will in your average "run-a-network-for-a-50-person-company" kind of job. I did it for about three years and really enjoyed it. You'd be building servers and designing networks on a daily basis, all great experience. You might have to start out in a more low-level position, but if you prove yourself competent, you'll gain ground quickly.
Candidly, certs are important for companies who need to sell your services (like the aforementioned reseller). Most other companies like them, because they indicate that you've got aptitude. Some don't care too much, knowing that you'll learn what you need to about their systems or you won't be able to cut it and move on.
Whenever someone asks me for advice like this, I always tell them to decide what they like to do and find a job that helps them move in that direction. If you don't KNOW what you like, find a job that lets you do a bit of everything. If you are just starting out, Helpdesk is a good one, especially for a medium-sized company where you can go out and DO stuff, not just sit and answer the phone. A second or third tech for a medium-sized company is also a good job with lots of learning potential. Just be sure you don't get stuck on a phone job, those suck.
- G