What would be the cause of this?

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
FASPAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lanboyoCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
lanboyoCommented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking Hardware-Other

From novice to tech pro — start learning today.