Yes, I have cleared all my cache files. Though I m starting to think its this router I am currently using. I let all 4 of my firewalls down and even tried to mirror the hub connection to see if something was interfering in between the connection signals sent from my computer to the site and vise verca. I am getting a new provider today to see if this solves the problem.
I appreciate everyone who gave advice (: Least now I know multiple things to check before coming back to the forum for future help on this topic heh.
I'm having the same problem too, my byond is not blocked or anything like that.
this is the ping, its dutch though Pingen naar tesla.byond.com [50.22.142.19] met 32bytes aan gegevens: time-out bij opdracht. time-out bij opdracht. time-out bij opdracht. time-out bij opdracht. Ping-statistieken voor 50.22.142.19: Pakketten: verzonden = 4, ontvangen = 0, verloren = 4 <100% verlies>. please help me D: | |
Oh and also this time-out and 100%lost(verlies) came after i did ipconfig, before i did iconfig there was no time-out and also the 100%lost was 50%.
| |
what does tracert hub.byond.com say?
| |
Traceren van de route naar tesla.byond.com [50.22.142.19]
via maximaal 30 hops: 1 * * * Time-out bij opdracht. 2 42 ms 21 ms 21 ms 82-168-37-254.ip.open.net [82.168.37.254] 3 22 ms 22 ms 29 ms 195.69.146.82 4 * * * Time-out bij opdracht. 5 * * * Time-out bij opdracht. 6 * * * Time-out bij opdracht. 7 * * * Time-out bij opdracht. 8 * * * Time-out bij opdracht. 9 * * * Time-out bij opdracht. 10 * * * Time-out bij opdracht. 11 * * * Time-out bij opdracht. 12 * * * Time-out bij opdracht. 13 * * * Time-out bij opdracht. 14 * * * Time-out bij opdracht. 15 * * * Time-out bij opdracht. 16 * * * Time-out bij opdracht. 17 * * * Time-out bij opdracht. 18 * * * Time-out bij opdracht. 19 * * * Time-out bij opdracht. 20 * * * Time-out bij opdracht. 21 * * * Time-out bij opdracht. 22 * * * Time-out bij opdracht. 23 * * * Time-out bij opdracht. 24 * * * Time-out bij opdracht. 25 * * * Time-out bij opdracht. 26 * * * Time-out bij opdracht. 27 * * * Time-out bij opdracht. 28 * * * Time-out bij opdracht. 29 * * * Time-out bij opdracht. 30 * * * Time-out bij opdracht. De trace is voltooid. | |
Seems like an error on your end. Although I don't know how you are able to reach our website. What does tracert byond.com look like?
| |
what you mean how does it look like? oh and at the end it says trace completed
| |
oh well nvm, it got fixed by itself right now.....finnaly
| |
uhm can someone help me i been having the same problem and have tried all the recommended stuff but i still cant connect to byond on my pager :(
| |
Where's the pager? I try to follow what Tom says but I have no idea what he means by pager
| |
The pager is the window that comes up when you run BYOND.exe, the program with the 'Blue atom' logo.
This is what the pager looks like. | |
Yeah I tried toms advice but nothing works.
I type in ping but nothing like what people say appears. I can't copy my cmd box. | |
Nevermind here's what it said when I typed in ping hub.byond.com
Pinging tesla.byond.com [50.22.142.19] with 32 bytes of data: Reply from 50.22.142.19: bytes=32 time=37ms TTL=52 Reply from 50.22.142.19: bytes=32 time=37ms TTL=52 Reply from 50.22.142.19: bytes=32 time=39ms TTL=52 Reply from 50.22.142.19: bytes=32 time=40ms TTL=52 Ping statistics for 50.22.142.19: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 37ms, Maximum = 40ms, Average = 38ms I can't open my pager since it goes BYOND Hub: connection failed | |
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved Pinging tesla.byond.com [50.22.142.19] with 32 bytes of data: Reply from 192.168.0.1: Destination host unreachable. Reply from 192.168.0.1: Destination host unreachable. Reply from 192.168.0.1: Destination host unreachable. Reply from 192.168.0.1: Destination host unreachable. Ping statistics for 50.22.142.19: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), error: byond hub connection failed | |
help plz'
| |
i having the same problem and i did everything you said and still dont work someone help me plz
| |
Idtaker wrote:
Microsoft Windows [Version 6.1.7601] You have a problem there it is supposed to being "Reply from 50.22.142.19" not your internal LAN IP address (192.168.0.1) Pinging byond.com [50.22.142.18] with 32 bytes of data: Reply from 50.22.142.18: bytes=32 time=204ms TTL=53 Reply from 50.22.142.18: bytes=32 time=204ms TTL=53 Reply from 50.22.142.18: bytes=32 time=206ms TTL=53 Reply from 50.22.142.18: bytes=32 time=207ms TTL=53 Ping statistics for 50.22.142.18: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 204ms, Maximum = 207ms, Average = 205ms This may be an ISP issue? do you have any firewalls running? are they blocking the IP? | |
To clear the cache, open the BYOND pager > File > Preferences > Games Tab > Click Clear Cache > OK > OK
You mentioned that your connected to the internet though your negibores wireless access, so this may be an issue with a setting that they have chosen.