# TCP IN node not receiving data

**URL:** https://discourse.nodered.org/t/tcp-in-node-not-receiving-data/88605
**Category:** General
**Created:** [10 June 2024 17:30 UTC](https://discourse.nodered.org/t/tcp-in-node-not-receiving-data/88605 "2024-06-10T17:30:48Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![tek2000](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tek2000/32/91866_2.png) [@tek2000](https://discourse.nodered.org/u/tek2000)
#### Post date: [10 June 2024 17:30 UTC](https://discourse.nodered.org/t/tcp-in-node-not-receiving-data/88605/1 "2024-06-10T17:30:48Z")

</div>

Hello,  
I am trying to receive XML response data back from a Printer over TCP connection.

I am able to connect to the printer and successfully send XML commands using the TCP Out node at 192.168.1.105 port 9900. I can see the XML data being sent and the XML response from the Printer using Wireshark, but the TCP IN node never shows anything incoming.

I should have the TCP In node set to Listen On port 9900 correct?

I setup a test TCP response flow in Node-Red on a separate computer and the Raspberry Pi received the response.

I tried setting up tcpdump to relay all traffic coming from 192.168.1.105 to localhost port 9901 and setup a TCP In node listening to port 9901. This doesn't seem to work very well because there is a long delay (30 seconds or more) and it doesn't seem to capture all incoming data.

**Any suggestions or ideas are greatly appreciated!!**

Running Node-Red version 3.1.9 on Raspberry Pi 4  
Operating System: Debian GNU/Linux 12 (bookworm)  
Kernel: Linux 6.6.20+rpt-rpi-v8

Node-Red flow

 ![node-red TCP flow](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/a/2aee8d27f5abf735b504fd46314bd16934b531a2.jpeg)

Wireshark screenshots:

 ![wireshark screenshot 1](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/8/98dd2a4377c5da95ea232178d13a1e176d06d2e1.jpeg)  
 ![wireshark screenshot 2](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/7/e7df9fd7727d8310aba1d29677b3c8cf7d9c66f3.jpeg)  
 ![wireshark screenshot 3](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/e/7e717d255e48c450ee100cd203267410fdcc8de3.jpeg)

---

<div class="post-metadata">

### Author: ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [10 June 2024 22:04 UTC](https://discourse.nodered.org/t/tcp-in-node-not-receiving-data/88605/2 "2024-06-10T22:04:29Z")

</div>

Did you try the tcp-request node, rather than the out and in nodes, as it is meant for more this command/ response type of interaction

---

<div class="post-metadata">

### Author: ![tek2000](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tek2000/32/91866_2.png) [@tek2000](https://discourse.nodered.org/u/tek2000)
#### Post date: [11 June 2024 00:13 UTC](https://discourse.nodered.org/t/tcp-in-node-not-receiving-data/88605/3 "2024-06-11T00:13:36Z")

</div>

I did try using the TCP Request node, but I didn’t see any response using debug nodes with that either. Maybe I didn’t have it setup correctly.  
I’ll do some more research and testing with the request node.

Any advice on the request node?

Thanks for the response!

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [9 September 2024 00:14 UTC](https://discourse.nodered.org/t/tcp-in-node-not-receiving-data/88605/4 "2024-09-09T00:14:12Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.