Pointing the Finger: Email Server Telnet Test
90% of your job as a network guy/gal is spent proving that it's not your fault (no...it's not the network!). A quick test email servers (SMTP - from a host outside the network):
C:\>telnet mail.tekcert.com 25
220 ****************************************************************************
helo
250 box447.bluehost.com Hello [38.101.10.67]
As soon as you see that reply, send that trouble ticket back from whence it came. Keep in mind that there are plenty of additional commands you can send to the SMTP server for further testing - here's a sample.
Comments
Another Great Post
I am with you...I seems that people, more so the Microsoft folks, always point the finger at the network guy first. I tend to reference the 7 layer OSI Model....all the way back the layer 7.....hmm seems the network is just fine! Jermey shoot me an e-mail at some time I would like to speak with you.
Thanks,
Chad Spears
OSI layers
You forgot to troubleshoot 8th layer of OSI model: Political. That's where users belong to ;-)
And rumors say there is also 9th layer - Religious: that's if you can't explain it, but rely purely on beliefs and dogmas.
Top Tip
Using telnet as a part of the troubleshooting process is invaluable.
It's worth noting that using the "telnet test" works even when a firewall is blocking / dropping ping and trace and that the response isn't always as crystal clear as your example.
Say I run "telnet a.b.c.d 8080" from a command shell then the response I'd expect (for a working IP, port and service) is that the cmd shell would clear and I'd be left with just a flashing cursor.
Like in your example - this is time to send the ticket back.
I Disagree
Jeremy, I know that this is post probably in jest but... I disagree with the attitude of finger pointing or "sending the ticket back" etc.
After all, we are in customer service... and granted we all get annoyed with the Windows-Pukes (my term of endearment for the Windows guys) always politely suggesting that the problem is in the network.
My suggestion is to educate and work with the Windows-Pukes to resolving the issue to the satisfaction of the customer. After all... dont let all the credit go to the Windows-Pukes!