I mostly agree with j , but I would never build walls by establishing a "Do Not Disturb" rule. People come to me all the time because they have questions, trouble with their work, want to chitchat or want me to do something (the "shortcut-process"). I like my colleagues, and I like talking to them. As long as I get my work done, everything is fine. By doing so, I also get some necessary knowledge for my work (what software is used on which servers, how is stuff interconnected, etc.) and social networking is going very well. It allows me to go to my colleagues later on when I need something (and believe me, when I need something, it usually is not a simple thing to solve, or it is a bit urgent).
So, what kind of people do I avoid? I don't like people who stick 99.99999% to all of the processes and stop thinking themselves. They are hard to work with, usually distanced, focused on work only, snobby (so not really team-players) and, in my experience, very single-minded (there's more than one story behind this). While processes are very useful, it is important to not forget the human aspect and networking-factor. We are not cold machines which execute a program from top to bottom. So, I try to avoid them. I don't think that has anything to do with me being an engineer, though :D
Other than that? Always stay clear of production-guys. They are nitpickers and always angry about the IT and infrastructure and your programs being so slow and unreliable. Really, try to avoid a job which puts you in a mediating position between them and IT or any kind of development. You will suffer and you can't blame them, since it's their job to be like that.