---
title: "W5500 Stops Communicating with Server until Switch is rebooted"
url: "https://maker.wiznet.io/forum/14372"
markdown_url: "https://maker.wiznet.io/forum/14372/md"
type: "Forum topic"
category: "Ethernet Chips"
author: "MikeOC1966"
created: "2021-10-25T12:13:29+09:00"
last_activity: "2021-10-25T12:13:29+09:00"
language: "en"
views: 360
replies: 0
source: "WIZnet Makers forum (https://maker.wiznet.io/forum/)"
---

# W5500 Stops Communicating with Server until Switch is rebooted

## Question

Asked by MikeOC1966 on 2021-10-25 in Ethernet Chips.

Hi All,

We manufacture a module that uses the W5500 and it is used to send small packets of data (30 bytes or so) using TCP/IP or UDP to a remote server. We have used the W5500 for the last 3 years without any issues. We have a customer that uses our module and from time to time for no reason the server stops receiving the messages from one or more of the modules, the customer has 100+ modules installed. You can ping the module and it responds fine, the firmware in the module will also perform a full reset and initialize on the W5500 if it fails to deliver the packet of data after x number of attempts.

The only way that communication can be re-established is to power down the switch that the module is connected to. The customer uses a wide variety of switches (Netgear, TP-Link etc). What would make the switch block/blacklist the W5500?

---

Source: https://maker.wiznet.io/forum/14372