Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Getting cooperation

Getting cooperation

Getting cooperation

I work for voice services and have to rely on Network guys to complete my trouble tickets sometimes... There is definate attitude from them and they try to come on as some kind of Savior when they are asked to do something ie check to make sure a switch port is set up with the right v-lan... any similar experiences or suggestions to make thing improve

Thanks in advance

RE: Getting cooperation

At most companies I have worked with recently the telephony guys were the same team as the networking team.  Especially since most companies have/are planning to migrate to some sort of VoIP system.  That certainly seems to be the trend going forward.

Generally speaking, I have found that MOST of the time the networking teams at larger enterprises are pretty reliable.  They usually do a pretty good job of getting configurations right when asked, etc.  Unfortunately, troubleshooting the network is typically an important step in diagnosing an issue, and often times you aren't able to properly diagnose an issue unless you can get a packet capture, etc.  This leads to the network teams spending a great deal of time helping other people troubleshoot issues that "aren't their problem."  That can be very frustrating, and if the network team spends a lot of time doing this then it can impact their ability to get their other work done.

I try to keep this in mind when dealing with network teams (and really any other team outside of my own) and try to minimize my impact.  I'll double and triple-check my designs and make sure that they are in as clear and concise format as possible before handing them off to the network team to implement.  Likewise, I double and triple check my troubleshooting before asking them to get involved in the process.  Rather than asking "is that port on the correct VLAN" or "is it configured for trunking rather than switchport access" I tend to approach it as "I'm having an issue with X on such-and-such port.  I'm seeing Y.  Can you tell me what you're seeing?"  Then instead of coming across as accusing them of making a mistake I sound much more neutral.

Really you should probably be doing this with any external teams or organizations that you're dealing with.  Soft skills can go a long way.

CompTIA A+, Network+, Server+, Security+
MCTS:Windows 7
MCSE:Security 2003
MCITP:Server Administrator
MCITP:Enterprise Administrator
MCITP:Virtualization Administrator 2008 R2
Certified Quest vWorkspace Administrator

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close