Port cannot be reached, server is online

ID:1506107
 
Feb 26 2014, 1:36 am
Not a bug
BYOND Version:504
Operating System:Windows 7 Ultimate 64-bit
Web Browser:Firefox 27.0
Applies to:Dream Daemon
Status: Not a bug
This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
Descriptive Problem Summary:
The server tells me that the server cannot be reached, that my port is closed. Yet others are capable of connecting without issue.

Numbered Steps to Reproduce Problem:
I'm unsure, all I did was start the server.

Expected Results:
BYOND Hub reports server's port is open and accessible.

Actual Results:
BYOND states port is closed, will not allow me to try and clode>open the port.

Does the problem occur:
Every time? Or how often?
Happened every time I re-started the server.

Workarounds:
Just try to get someone to join, it may work, it may not.

Screenshot: http://puu.sh/7b52O/d5073fc3e3.png

Feb 26 2014, 12:29 pm
Can you ping

hub.byond.com

And paste the results please.

[EDIT]

I was getting some packet loss just now.

 root@byondpanel:~# ping hub.byond.com
PING tesla.byond.com (50.22.142.19) 56(84) bytes of data.
64 bytes from tesla.byond.com (50.22.142.19): icmp_req=1 ttl=51 time=26.7 ms
64 bytes from tesla.byond.com (50.22.142.19): icmp_req=2 ttl=51 time=27.2 ms
64 bytes from tesla.byond.com (50.22.142.19): icmp_req=3 ttl=51 time=35.1 ms
64 bytes from tesla.byond.com (50.22.142.19): icmp_req=4 ttl=51 time=26.6 ms
^C
--- tesla.byond.com ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4004ms
rtt min/avg/max/mdev = 26.656/28.943/35.172/3.605 ms
Feb 26 2014, 2:07 pm
You should probably do more than just 5 packets.
Feb 26 2014, 4:06 pm
In response to MisterPerson
True, it was something on my end anyway..
May 14 2014, 1:57 pm
Is this still an issue?
May 14 2014, 2:03 pm
No, it seems to be working again. The funny thing is that it is only BYOND that seems to work when it comes to portforwarding at the moment. But that's something my ISP will have to go and fix.
May 14 2014, 2:04 pm
Awesome, thanks for the feedback.
May 14 2014, 2:04 pm
Stephen001 resolved issue (Not a bug)