Hot Downloads

Welcome, Guest
Username: Password: Remember me

TOPIC: Network Troubleshooting

Network Troubleshooting 10 years 4 months ago #14737

I am a cisco rookie....still trying to get my feet situated properly in the field. I just completed a CCNA training, though coming from a Unix background, everything feels different to me. I need resources on troubleshooting, how do i approach a downed network, what should be my troubleshooting guidelines?
The administrator has disabled public write access.

Re: Network Troubleshooting 10 years 4 months ago #14739

  • The_Geek
  • The_Geek's Avatar
  • Offline
  • New Member
  • Posts: 18
  • Karma: 0
I am a cisco rookie....still trying to get my feet situated properly in the field. I just completed a CCNA training, though coming from a Unix background, everything feels different to me. I need resources on troubleshooting, how do i approach a downed network, what should be my troubleshooting guidelines?

Well, for starters:

(1) Can anyone connect to the internet, or it it only limited to one or two people?

(2) Does the internet router supply NAT/DHCP, or is it in bridged mode to an internal router/firewall?

(3) Can you ping the internal gateway address? Can you ping the external IP address?

(4) If you connect a PC directly into the internet router, can you access the internet?
Powered by
The administrator has disabled public write access.

Re: Network Troubleshooting 10 years 4 months ago #14740

  • d_jabsd
  • d_jabsd's Avatar
  • Offline
  • Distinguished Member
  • Posts: 153
  • Karma: 0
Your troubleshooting methods are going to vary from issue to issue.

In its basic form, you have 3 options:
1. troubleshoot from the outside in
2. troubleshoot from the inside out
3. split the difference and start in the middle, working your way out/in, then go the other direction.

In general, networks don't usually just die. The problem can usually be traced back to Carrier issues, Misconfigurations, bad cables, or 'acts of god' -ie: storms causing power outages.

-In the case of a misconfiguration, back out everything you just did and see if the problem goes away.
-In the case of carrier issues, once discovered, call your ISP.
-Bad cables are usually an issue right away. Replace it or remake it if you roll your own.
-Acts of god need to be evaluated on a case by case basis and will vary based on the damage done.
The administrator has disabled public write access.

network troubleshooting 10 years 4 months ago #14744

  • Arani
  • Arani's Avatar
  • Offline
  • Moderator
  • Posts: 745
  • Thank you received: 10
  • Karma: 4
hi there,
again from my archives, here's a link which you can use as a guide to network troubleshooting
http://support.3com.com/infodeli/tools/netmgt/tncsunix/product/091500/c1ovrvw.htm
Picking pebbles on the shore of the networking ocean
The administrator has disabled public write access.

Testing 10 years 4 months ago #14745

  • TheBishop
  • TheBishop's Avatar
  • Offline
  • Moderator
  • Posts: 1719
  • Thank you received: 8
  • Karma: 5
Great advice from Arani
One thing to add; approach your network before it breaks. Survey and document it. That way when it does break you'll have a good grasp of the topology and you'll be able to select logical places to test and break the problem down. And also you'll know what 'normal' looks and feels like so the abnormal will be obvious.
You can faultfind without these extras but they really do help speed things up
The administrator has disabled public write access.
Time to create page: 0.082 seconds

CCENT/CCNA

Cisco Routers

  • SSL WebVPN
  • Securing Routers
  • Policy Based Routing
  • Router on-a-Stick

VPN Security

  • Understand DMVPN
  • GRE/IPSec Configuration
  • Site-to-Site IPSec VPN
  • IPSec Modes

Cisco Help

  • VPN Client Windows 8
  • VPN Client Windows 7
  • CCP Display Problem
  • Cisco Support App.

Windows 2012

  • New Features
  • Licensing
  • Hyper-V / VDI
  • Install Hyper-V

Linux

  • File Permissions
  • Webmin
  • Groups - Users
  • Samba Setup