ping - but no connection possible
Posted: Tue Dec 13, 2022 5:16 pm
Hi
I have a softether server behind a standard 1Gbe Internet router. Port-forwarding to 443. That all works perfectly fine and is (as far as I can tell) box standard.
Now I am having this very strange effect: Trying to connect to one specific remote site
- sometimes (mostly) works as expected - but sometime it doesn't.
- It seems to depend on the type of internet connection. E.g., using my laptop, if I use my
- home WLAN (so my home Internet connection) it works fine
- phone as a hotspot it doesn't.
- When it doesn't work, it gets stuck at "contacting [server.name]" - so one could think it is a DNS issue
- but it isn't - as I can still NSLOOKUP and also PING the [server.name] when over such a connection (I appreciate that I rather ping the remote router than the server - but it shows that the DNS resolution work as always).
I am wondering if some kind of proxy or NAT translation down the network path could create that problem - but what could I do against it.
It is also mysterious that this issue appears only in relation to that one remote site. To other remote servers - with as far as I can tell are near identical in terms of internet connection, hardware and software configuration - I can always connect.
Any hints would be appreciated.
I have a softether server behind a standard 1Gbe Internet router. Port-forwarding to 443. That all works perfectly fine and is (as far as I can tell) box standard.
Now I am having this very strange effect: Trying to connect to one specific remote site
- sometimes (mostly) works as expected - but sometime it doesn't.
- It seems to depend on the type of internet connection. E.g., using my laptop, if I use my
- home WLAN (so my home Internet connection) it works fine
- phone as a hotspot it doesn't.
- When it doesn't work, it gets stuck at "contacting [server.name]" - so one could think it is a DNS issue
- but it isn't - as I can still NSLOOKUP and also PING the [server.name] when over such a connection (I appreciate that I rather ping the remote router than the server - but it shows that the DNS resolution work as always).
I am wondering if some kind of proxy or NAT translation down the network path could create that problem - but what could I do against it.
It is also mysterious that this issue appears only in relation to that one remote site. To other remote servers - with as far as I can tell are near identical in terms of internet connection, hardware and software configuration - I can always connect.
Any hints would be appreciated.