<html><body><div dir="auto">As you say, Martin, the address that is published for the node does not respond, but this morning I located the IP address of the node and was able to connect without problems. </div><div dir="auto">It is clear that DNS does not resolve the real IP.<br></div><div dir="auto"><br></div><div dir="auto">Kin EA3CV</div><div dir="auto"><br></div><div id="ms-outlook-mobile-signature" dir="auto"><div><br></div>Enviado desde <a href="https://aka.ms/AAb9ysg">Outlook para Android</a></div><div id="mail-editor-reference-message-container" dir="auto"><br><hr style="display:inline-block;width:98%"><div id="divRplyFwdMsg" style="font-size: 11pt;"><strong>De:</strong> Dxspider-support <dxspider-support-bounces@tobit.co.uk> en nombre de Martin Davies G0HDB via Dxspider-support <dxspider-support@tobit.co.uk><br><strong>Enviado:</strong> jueves, julio 25, 2024 12:45:29 p. m.<br><strong>Para:</strong> The DXSpider Support list <dxspider-support@tobit.co.uk><br><strong>CC:</strong> Martin Davies G0HDB <marting0hdb@gmail.com><br><strong>Asunto:</strong> Re: [Dxspider-support] GB7VAX down again<br></div><br>On 24 Jul 2024 at 20:18, Brian Bowers via Dxspider-support wrote:<br><br>> Hi All,<br>> <br>> I am now at a loss.<br>> <br>> EE in their wisdom have done something, and now, I cannot for the life of<br>> me get the USER port of my cluster GB7VAX to allow connections from my<br>> users.<br>> <br>> The cluster is connected to the network, as I can verify that by going into<br>> the console, but when going through the logging PC, its a no go.<br>> <br>> Can anyone shed any light on the issue?<br><br>Brian:<br><br>I have no knowledge or experience of EE as an ISP but is it possible that they might have <br>made some changes either in their systems or to your router that have closed off the port <br>through which your external users have to telnet into GB7VAX?<br><br>I see that the address of GB7VAX seems to be gb7vax.serveftp.com:7300; is this <br>correct? Assuming it is, I've just tried to telnet into it and the connection has failed to get <br>through as you and your users have experienced. I've also just tried to telnet to port 7300 at <br>what appears to be the IPv4 address of gb7vax.serveftp.com, ie. 86.152.75.236, and that has <br>also failed. Trying to ping that IP address also fails, but your router might be configured to <br>not respond to pings so that's not too much of a surprise.<br><br>Have you checked that the port forwarding on your router is correctly set, so that an incoming <br>telnet connection on port 7300 is forwarded to the correct port at the IP address of your <br>GB7VAX machine on your LAN? If your router is managed by EE then it's certainly possible <br>that their recent changes might have screwed up the port forwarding.<br><br>Have the changes that EE have recently made resulted in a change to your IP address on the <br>Internet? If it's no longer 86.152.75.236 then you might need to update the entry for GB7VAX <br>at serveftp.com.<br><br>Does EE provide you with a static IP address on the Internet, or a dynamic address that can <br>change? I've always believed that having a static WAN address can make things a bit <br>simpler to control...!<br><br>--<br>73, Martin G0HDB<br><br><br>-- <br>This email has been checked for viruses by Avast antivirus software.<br>www.avast.com<br><br>_______________________________________________<br>Dxspider-support mailing list<br>Dxspider-support@tobit.co.uk<br>https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br><br></div></body></html>