Port 81 81

Nicogou2103

Hello Daniel,
I am contacting you with regards to the same issue which was raised in Sept’25 in this community discussion….

For some reason, there seems to be the same problem as before where the port 8181, does not seem to connect (pls see attached).

At some point @Xydocq presented me with a fix that worked. I have rechecked the “host” file which was modified and saved and it seems to still keep the changes that were made (pls see attached).

I am not sure where the problem might come from and how to fix it. Would greatly appreciate your assistance.

Regards,

Nicolas

Xydocq

hello Nicogou2103

Since you mentioned my name, I’ll gladly help with your problem. Looking at your screenshots I assume there’s a problem with the Connection-specific DNS Suffix, usually that should be blank.

My screenshot is in german but it’s the first line on it.

To remove the DNS Suffix follow this instructions:

Press Win + R, type ncpa.cpl, and press Enter to open Network Connections.
Right-click on your active network adapter and select Properties.
Double-click on Internet Protocol Version 4 (TCP/IPv4).
Click on Advanced in the new window.
Navigate to the DNS tab.
Locate the DNS suffix field and remove the old DNS suffix if listed.
Ensure Append primary and connection-specific DNS suffixes is selected.
Check Register this connection’s addresses in DNS and click OK to save changes.
Open Command Prompt as Administrator.
Run the command ipconfig /flushdns to clear the DNS cache.
Restart your computer to apply the changes.

Please let us know, if it solved your issue.

Kind regards
Xydocq

Nicogou2103

Xydocq

Hello,

Hope you are well. Indeed, you were able to help me with the same port issue back in Sept25.

With regards to the different steps, before changing anyting I wanted to show a printscreen of what I have in fron tme:

Did I understand correctly? Do I remove the numbers in the first box above? Or was it the second box which does not show any list. (Pls see print screen)

Points 7 and 8 seem to be checked and selected.

So not quite sure, How to go forward from this. Would appreciate your feedback on the printscreen and how it looks at the moment.

Kind Regards,

Nicola

Xydocq

Nicogou2103

hello Nicola

I’m doing ok, thank you for asking.

Looking at the screenshot, it seems my guess with the DNS Suffix, leads in the wrong direction. localhost is a NetBIOS-name and localhost-tradingtechnologies.com is a full qualified domain name.

I would like to have some more information.

What happens if you use the command telnet localhost-tradingtechnologies.com 8181 or telnet 127.0.01:8181, does it show the same result as telnet localhost 8181?
What is the result when you use the command ping localhost? The ping result isn’t what I am interested in, it’s more the IP address shown on the ping. Is it ::1 or 127.0.0.1?

If it shows ::1, your computer is set to prefer ipv6 over ipv4. You can try to edit the hosts-file and add the line 127.0.0.1 localhost.

Kind regards
Xydocq

Nicogou2103

Xydocq

Hello,

Thank you for your feedback.

You will see through the printscreen, the results on your query.
I see ::1: follwoing the ping….
You would have to lead me step by step as to what you would like me to try further.

Kind Regards,

Nicola

Nicogou2103

Xydocq

If you look at my 1st message on this topic, you will see a printscreen I made on the “Hosts” file, which you helped me change last September, in order to fix the issue at the time.
I see the 127.0.0.1 localhost on it. It does not seem to have changed.

Xydocq

Nicogou2103

Thank you for the additional information.

Your computer prefers IPv6 over IPv4. This can lead to problems regarding ports. It also seems your ssh isn’t listening on port 8181

Please open Command Promt and enter netstat -n | findstr 8181 you can also try netstat -n | findstr localhost. Both commands should provide a list with open ports on your machine. If the reply is empty, it might be best to contact tradingtechnologies and ask them for guidance.

More help can be found here -> https://library-staging.tradingtechnologies.com/trade/algo-trading/excel-integration-with-tt/reference/integration-with-a-web-proxy/

Nicogou2103

Xydocq

Hello,

Coming back to you with the latest. I’ve had a look at the link you provided; pls see the printscreen of the results.

Also, with regard to the add-in in Excel. The issue is that I can no longer open Excel.

Last year, you helped me resolve the issue of not seeing what I entered in the spreadsheet and it being reflected in the software. But now, every time I attempt to open the same spreadsheet, it comes up with the error message as to whether or not I want to open it in safe mode. And despite trying both options, the spreadsheet just closes down.

I can’t even go to the options of add-ins in Excel because I can’t reach that far.

So I don’t know where it comes from.

At one point, I was online with Microsoft support. At first, I thought it was coming from the Excel application. At the same time, I uninstalled the add-in application from the computer.
Microsoft Office 365 was reinstalled, and I could open Excel.

It’s only after I reinstall the add-in integration from the software that I get the same issue over and over again

Xydocq

Nicogou2103

greetings Nicola

Last time it was a DNS issue. The name localhost-tradingtechnologies.com didn’t get resolved to 127.0.0.1, the hosts-file can be used in such a case and solves the DNS issue. I had to do that in the past and am still doing it, to access certain resources on my network by FQDN or NetBIOS-name. You can try to flush the DNS cache on your computer. Open Command Prompt as Administrator. Run the command ipconfig /flushdns to clear the DNS cache. Restart your computer to apply the changes. It doesn’t break anything on your computer, so there’s no risk in trying.

There’s a new issue now. DNS is still working as it should. But your requests get dropped, when ever you try to access the resource. There are a few reasons, why it can get dropped. For one the certificate provided by tradingtechnologies is no longer valid or the port 8181 isn’t listening on your computer.

The netstat command is to check if the port is listening. The command you typed has a typo in it. You used ¦. The right caracter to use is |. You can simply use netstat -n. But be warned it will show any connection established or waiting on your computer. So the list might be quite long. Then you can scroll through the list and see if you can find Port 8181. It should show as 127.0.0.1:8181.

If you can find the port, I assume your problem might be related to a certificate. This problem can only be solved by tradingtechnologies.

Kind regards
Xydocq

Nicogou2103

Xydocq

Hello,

I don’t know what’s the problem now. I tried testing the 2 commands and I have this now

Xydocq

Nicogou2103

hello Nicola

I do not know why the ping is failing now. Could be the name didn’t get resolved correctly.

The failed netstat command means port 8181 isn’t listening on you computer.

Kind regards
Xydocq