Support Board
Date/Time: Thu, 16 Oct 2025 01:28:38 +0000
Post From: DTC Protocol Server Not Accepting Connections
| [2025-10-15 16:27:49] |
| Meta Trading VR - Posts: 33 |
|
Issue Summary Sierra Chart logs indicate "DTC Protocol Server listening on port 11099" but external applications cannot connect to it. Connection attempts result in "Connection refused" errors despite the server appearing to be enabled and running. Environment Sierra Chart Version: 2800 64-bit License: Advanced Features 2 OS: Windows 10 Data Feed: Denali Real-Time Exchange Data Feed (working correctly) Trading Service: Teton CME Routing (connected and functioning) Configuration DTC Protocol Server Settings (confirmed via Server Settings UI): Enable DTC Protocol Server: Yes Listening Port: 11099 Listen IP Address: 0.0.0.0 (all addresses) DTC Protocol Server is Listening (Read Only): Yes ✅ Encoding: Binary with variable length strings Observed Behavior Sierra Chart Message Log Shows: 2025-10-15 12:04:53.254 | Created the DTC Protocol server. 2025-10-15 12:04:53.254 | DTC Protocol Server listening on port 11099. Address: 0.0.0.0 External Application (KAIROS Platform) Attempting Connection: 2025-10-15 09:07:08.307 | INFO | Connecting to DTC server 127.0.0.1:11099... 2025-10-15 09:07:10.310 | ERROR | DTC connection error: [Errno 10061] Connect call failed ('127.0.0.1', 11099) Error Code: 10061 = Windows WSAECONNREFUSED (Connection refused - nothing listening on port) Troubleshooting Steps Performed ✅ Verified Settings: Confirmed DTC Protocol Server enabled, port 11099, UI shows "Listening: Yes" ✅ Applied Settings Multiple Times: Clicked "Apply All" button, restarted Sierra Chart completely ✅ Port Change Test: Changed port from 11099 → 11100 → 11099 to force socket rebind ✅ Firewall Check: Windows Firewall not blocking (other Sierra Chart services working fine) ✅ Client Application: Using standard DTC protocol client (Python asyncio), tested with Binary VLS encoding, Protocol Version 8 ✅ Historical Data Port: Confirmed port 11098 (Historical Data Server) IS listening and accessible Evidence of Issue Sierra Chart's own internal client connections work: Teton CME Routing successfully connects using DTC Binary VLS to external server Historical Data Server (port 11098) is listening and accessible Message log shows proper DTC handshake when Sierra Chart acts as CLIENT External connections fail: Any attempt to connect TO Sierra Chart's DTC server on port 11099 is refused netstat shows no LISTENING socket on port 11099 Only SYN_SENT attempts from client visible (connection never established) Question for Support Why does Sierra Chart log "DTC Protocol Server listening on port 11099" but the TCP socket is not actually bound/listening, preventing external applications from connecting? Is there: A specific Windows permission required? An additional setting that must be enabled? A known issue with the DTC Protocol Server feature? A diagnostic log that shows why the server failed to bind to the port? Expected vs. Actual Expected: DTC Protocol Server binds to 0.0.0.0:11099 External applications can connect and perform DTC handshake (ENCODING_REQUEST → LOGON_REQUEST) Similar behavior to Historical Data Server (which works correctly on port 11098) Actual: Sierra Chart logs success message No TCP socket actually listening on port 11099 All connection attempts refused with WSAECONNREFUSED Thank you for your assistance. |
 Screenshot 2025-10-15 112142 -Sierra log.png / V - Attached On 2025-10-15 16:24:17 UTC - Size: 173.22 KB - 6 views Screenshot 2025-10-15 092243.png - Terminal Log.png / V - Attached On 2025-10-15 16:24:26 UTC - Size: 627.28 KB - 7 views |