Port help for a novice

[#1]

No, I am very sorry I gave you the wrong information. The correct address is http://newsurroundsound.ddns.net:30125/

[#2]

Moving on...

nslookup newsurroundsound.ddns.net
Server:  UnKnown
Address:  192.168.10.1

Non-authoritative answer:
Name:    newsurroundsound.ddns.net
Address:  90.251.39.97

I have checked if newsurroundsound.ddns.net port 30125 is open using https://www.yougetsignal.com/tools/open-ports/ 

this is the result Port 30125 is open on newsurroundsound.ddns.net

I used the telnet command telnet newsurroundsound.ddns.net 30125 and the host allowed the connection, so for me it would probably work using the intended application. I can not connect using a web browser

To confirm I am using a Hub Two, the broadband firewall for my plusnet account is set to Low.

Have you enabled 'Plusnet Safeguard' or any other form of online protection?

It would be interesting if you can try  telnet newsurroundsound.ddns.net 30125 to see if you get a connection

[#3]

Ah, thank you again for all this info. I will pass your findings on to the webmaster.
- I will try and work out how to tenet. It's not that straightforward on a Mac, it seems.

- I don't have any online protection switched on

Thanks,

Ben

[#4]

I have been asked to check all my EiskaltDC settings again. Which sort of brings me back to my original question; about how to open a TCP port (part of the setting up process). Hunting around in my Hub 2 settings, I can across the attached, which mentions ports. Does this help to shed any light?

[#5]

You do not need to open any outgoing ports to the internet, they are already open by default.

Did you add those port forward rules titled EiskaltDC? those rules forward any external traffic on port 3000 TCP/UDP and port 3001 TCP to the PC name Bs-iMAC

[#6]

I found this in my research

How have you configured it?

Firewall with port forwarding, what have you made the External/WAN IP or a different option? 

I can not log in as I have do not have an account.

Edit: with UPnP enabled these rules are added

[#7]

No, I have never changed any settings in Hub 2, I am not sure how they got there BUT I have had this software (EiskaltDC) working fine in the past, maybe that's a clue. That was years before I changed to Hub 2. Thank you for your continuing help with all this. 

[#8]

> Edit: with UPnP enabled these rules are added

I don't understand; do you mean that it was automatically configured?

[#9]

UPnP this stands for Universal Plug and Play.

So with that option enabled the Firewall rules would have been added by the application in this case EiskaltDC++, so the port forward shouldn't really need adding as they are already there.

So which connection option are you using?

Looking at the EiskaltDC app preferences there is an option for 'Logs' maybe try enabling 'System messages' to see if that provides any help information when you try connecting.

[#10]

Been checking some more, can you delete the current three port forward rules for the name EiskaltDC++

Then make sure the EiskaltDC++ connection setting is set for "Firewall with port forwarding"

Then on the Hub Two create the three rules manually and try again

Edit: using https://www.ipfingerprints.com/portscan.php you should be able to confirm the ports are open

PORT     STATE         SERVICE

3000/tcp open          ppp
3001/tcp open          nessus
3000/udp open|filtered hbci

[#11]

Many thanks. I have done half of this, deleting the 3 EiskaltDC rules and saving. I am not sure how to create rules as I have never done it before, but am looking into it. I have also enabled EiskaltDC  logs, but it is not immediately clear how they get generated (although something has already appeared in my saves folder, so perhaps its auto-generated. I'll keep an eye on it/them.)

[#12]

This should help with the Hub Two

https://www.plus.net/help/broadband/router-user-guides/hub-two/ 

[#13]

I have run into 2 small problems recreating those port assignments. I can create the first rule (called EiskaltDC++ Transfer Port) no problem, but when I try to create the next one, when I save it, it's not listed. The name is I believe EiskaltDC++ Encrypted Transfer Port. 

Advance Settings>Firewall>Port Forwarding wouldn't let me replicate what I originally had as rules; there were two rules which used ports with the same number (screenshot above), but I couldn't save the second rule I tried to (re)create. I was told that the port was already in use.

How important are rule names? The page you sent earlier is not especially helpful for that. It seems there is limited space to put in a long name, although I am flying blind to a degree, as I didn't save a record of my original rules. My screenshot above just says " EiskaltDC++ Transfer Port ( " and " EiskaltDC++ Encrypted Tra " and one other.

[#14]

The name has to be unique, but the name of it is not important, just a name which makes sense to you
Maybe something like EiskaltDC-1, EiskaltDC-2 EiskaltDC-3
Make sure you do not create two rules for the same protocol
Hope that makes sense

[#15]

Great, thanks. I have now deleted and created my rules again and saved them to my Hub 2 account. I think that I had one of them as a TCP when I should have had it as UDP, now corrected.

So it's now (see attachment)

I see that the top ones (which work fine) have a grey background, whereas the ones I created don't.

I am getting the dialogue "Do you want the application "EiskaltDC++.app" to accept incoming network connections?", which is an improvement over previously, although the network service still isn't showing me a file listing of any kind, viz:

"[14:31:12] * Fail: Connection timeout...

[14:31:13] * Connecting to dchubhost.no-ip.info:30123" 

The EiskaltDC log is giving me the following: 

[2024-05-29 14:25:31] File list refresh initiated
[2024-05-29 14:25:31] File list refresh finished
[2024-05-29 14:25:33] Connectivity: Determining the best connectivity settings...
[2024-05-29 14:25:33] Connectivity: Local network with possible NAT detected, trying to map the ports using UPnP...
[2024-05-29 14:25:53] Connectivity: UPnP: Failed to initialize the MiniUPnP interface
[2024-05-29 14:25:53] Connectivity: UPnP: Failed to create port mappings
[2024-05-29 14:25:53] Connectivity: Automatic setup of active mode has failed. You may want to set up your connection manually for better connectivity