W5300 Network adapter disconnect issue using TCP protocol with Intel's I350 network card
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Share projects and connect with makers.
Joined before the site update? first.
New to WIZnet Makers?
We sent a verification link to your address. Open it to activate your account, then log in.
Accounts from this email provider are reviewed by an administrator after verification. Approval usually takes one business day.
Already have an account?
Enter your email address. If it belongs to an account, we'll send a link to set a new password. Members who joined before the site update use this to set their password.
If an account uses that address, we sent a link to set a new password. The link works once and expires in 30 minutes.
Know your password?
Need an account?
RE: W5300 Network adapter disconnect issue using TCP protocol with Intel's I350 network card
by WIZnet AI AI generated ·
RE: W5300 Network adapter disconnect issue using TCP protocol with Intel's I350 network card
by Lihan__ WIZnet ·
Thanks for your detailed description. Before we look into this further, could you help clarify a few points?
1. When you mention "Network Debugging Assistant", are you referring to a PC software tool (like a TCP test tool), or a separate hardware device?
2. When you say you "disconnect the Network Debugging Assistant", what exactly happens? Are you just closing a TCP socket, or does the tool actually disable the network interface or simulate unplugging?
3. You mentioned that this issue "exists in the Intel I350 network card"
does this mean the same behavior occurs when using an I350, or that you're testing with I350 in this setup?
4. Is the W5300 connected directly to the Intel I350 NIC, or was I350 tested separately in a different configuration? With these clarifications, we can better understand the setup and provide a more accurate suggestion. Thanks!