@George_A 

Hi,

Is the service whose traffic goes through port 44158 using the TCP protocol or the UDP protocol?

I am asking because I haven't actually found a website that can correctly report whether UDP ports are open or closed on my home Internet connection.

Checking TCP ports works fine though.

  @woozle  TCP. I hope the instructions below will help you make more sense.  

Port Forwarding

Before launching the [Hellium] Miner, you will want to configure ports on your network to forward two ports:

• 44158/TCP: the Miner communicates to other Miners over this port. The networking logic knows how to get around a lack of forwarding here, but you will get better performance by forwarding the port
• 1680/UDP: the radio connects to the Miner over this port. You will not be able to forward packets or participate in Proof of Coverage without this

"Forwarding" on the second port is less relevant if you are running a radio packet forwarder on the same system at the miner (both on a Raspberry Pi, for example). But it is essential if you are running a Miner on the cloud for example.

  @Kevin_Z thanks for the quick reply. So I have got through steps 1 to 3, but port 44518 is still closed.

Step 1: Make sure the server is accessible from the internal network - indeed, the server is accessible in my local network and the IP is checked more than twice.

Step 2: Check the port forwarding settings in the router. - I am not sure what does that mean? I have checked the NAT forwarding rule - it is enabled and the correct IP/ protocols are used. UPnP is disabled as recommended in one of the posts I have seen in this forum. Are there other settings I am not aware of?

Step 3: Check the firewall setting. - Okay, I am not sure what I am supposed to check here. The tip recommends turning the firewall off? I have turned it off, but the 44158 port is still closed. Is there some rule that I am missing? 

My WAN IP is public (it starts with 91.XXX.YYY.ZZ), and I have reserved the IP adress of the virtual server (via DHCP rule).

I wanna add something, I am using the same internet service provider on another adress, with Archer C54 router and I have manage to open port 44158 with no problems whatsoever. I have even tried the same device and I had no problems opening the port for it. I hope this is helpful.    

Please advise,

Best,

George  

  @terziyski I have updated the FM and it is still not working. Suggestion 1 is basically step by step instructions how to set a virtual server rule for port 44158, something that I have done a dozen times already, and unless there is something I am missing, it is not going to solve the problem. I am sorry, I don't want to sound rude, but I had my hopes on the FM update and it is not working. Is there any chance support can check my router remotely, or something like this? I need to know if this problem is solvable or just ditch this router and try with different one.