?
Solved

What would be the cause of this?

Posted on 2009-05-12
2
Medium Priority
?
194 Views
Last Modified: 2013-11-09
I've been working on a networking problem where multiple workstations have a brief interruption in their network connection, (as indicated by a timeout on a ping -t.)  To make a long story short, I was watching wireshark when this happened and I was wondering if someone could point me in the right direction as to what would cause this.

I was using wireshark on a laptop plugged into my switch.  The switch is managed and I had port mirroring from one of my network printers ports so that I could monitor traffic going to the port belonging to the printer.  The reason I chose the printers port on the switch is because when this anomaly  happens the printer will usually not respond to  pings for 30 sec to 1 min.  So I wanted to see if a jabbering nic someplace is causing it.

What is strange about this, (and I attached a screenshot of the wireshark capture while this was happening,) is that the printers static ip is 192.168.1.145.

If you notice in the screenshot, ( at time of 1140,) i'm sniffing traffic destined for 192.168.1.39, (which is a time card program kiosk at my facility.)  Wny was the printer at 192.168.1.145 receiving traffic destined for 192.168.1.39?  

Is this a bad switch?  A bad nic in the server that transmitted the packet? Is it something else entirely.  Any help would be appreciated.
WsharkCapture.jpg
0
Comment
Question by:FASP
  • 2
2 Comments
 
LVL 10

Accepted Solution

by:
lanboyo earned 2000 total points
ID: 24366949
A switch that has not learned the destination port for a particular mac address will send packets destined for that mac address out all ports in the vlan in which it was received.

So as the mac-addresses time out of the vlan table they will need to be sent to all interfaces.
0
 
LVL 10

Expert Comment

by:lanboyo
ID: 24367223
Now if this is simultaneous to the timeouts then you might have a problem. Usually I suspect spanning tree topology changes for this type of thing.....

The mac-address timeout is usually set for 300 seconds, you can increase it if you get a lot of this.

mac address-table aging-time 600

 makes it 10 minutes.

What really might be occuring is that the link between the switch that .39 is on and the switch that the server.firstaidandsaf is on went down or into blocking mode and the network is color storming the packet  out all interfaces except the one it came in on, and your switch is doing the same.
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you’re involved with your company’s wide area network (WAN), you’ve probably heard about SD-WANs. They’re the “boy wonder” of networking, ostensibly allowing companies to replace expensive MPLS lines with low-cost Internet access. But, are they …
This month, Experts Exchange’s free Course of the Month is focused on CompTIA IT Fundamentals.
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question