Hello when i try to load up SS13 on the LLJK US 2 server i just get a message saying "connection closed but when i try other servers like Hippie station 13 i get a message saying something along the lines of banned guest accounts not allowed even though i am logged into my account.. take mine i have made 2 new accounts and still not fixed. Please help.
https://gyazo.com/29e3fd7753e2c38fedf824015a82577a
Link showing connection closed message.
ID:2245277
 May 9 2017, 2:20 pm (Edited on May 9 2017, 2:30 pm)
|
|
I tried loading up iconshare it loaded heres a ss.. i've never used byond so i'm pretty new.
https://gyazo.com/bce2b8046c3d53c8af8b45cc30492859 | |
As it logged me in as guest on the iconshare server does this mean its my firewall / security software that's causing the problems ? if so how do i fix this ?
| |
The first thing to check is the Windows firewall. Open that up and look at the inbound and outbound rules in your settings. If the firewall is working correctly, there should be an entry under inbound rules allowing byond.exe to use TCP. (There may also be one for UDP, but BYOND doesn't care about UDP.) Ideally you would also want dreamseeker.exe and dreamdaemon.exe there.
If you don't see an inbound rule, you may need to make one. 1) Select the inbound rules, and you should see an option to create a new rule. 2) The rule type is Program, and the program path would be (most likely) C:\Program Files (x86)\BYOND\bin\byond.exe. 3) The action for this rule is to allow the connection. 4) You can give this rule a name, like BYOND Pager, to make it easy to spot in your list. 5) Repeat the above steps for dreamseeker.exe and dreamdaemon.exe, in the same path, if necessary. Now generally these rules get created automatically when BYOND runs, when your system asks if you want to allow them to use the network. So if you said yes at the time, you should already have those rules. If the rule for byond.exe is present, the next thing I'd suggest is seeing if the pager has a port open. 1) Go to Documents\BYOND\cfg and find pager.txt. (Do this while the BYOND pager is running.) 2) Find a line called proxy. If it's not there, that's a problem; if it is there, copy down the port number. 3) Open a command prompt by typing "cmd" in the start menu. 4) Type "netstat -an | more" at the prompt. 5) Look for a line that says LISTENING and 0.0.0.0:[port] where [port] is the number you saw in the file. Whether the port is open or not, once we have that information I think we can take it further from there. | |
Also, another question I need to ask is if your user path (i.e., the full path to your documents folder) contains any Unicode characters that don't conform to a simple ASCII character set, like anything with an accent or in Cyrillic or whatnot. That's been known to cause some interference with files in the BYOND user data directory, although not this particular issue.
Another common cause of config problems is if for some reason the Documents\BYOND directory is on a network share. BYOND actually looks for this when it sets up its directory for the first time, but if it falsely believed the directory was local rather than on a network and put it on a network share anyway, that's another possibility. | |
Hello i tried all the things you said and i taken Screen shots of the information that showed up, please do take a look. My user path doesn't hold weird characters either.
I am certain that its not on a shared network aswel :/ https://gyazo.com/f1430424780a2d69f8758ffcb195df13 -- https://gyazo.com/c6073f0317067820997c8b240aacc7fa -- https://gyazo.com/6c442e20ae2686a87d2f593e4c3f862c -- https://gyazo.com/ccd27e0ff9b481a16b4bd088db94eb99 | |
I noticed the rule says Public; it should really also say Private. You might want to edit the rule so it applies on private networks as well. It's quite possible that the firewall is blocking the connection because it's on a loopback address (that is, Dream Seeker is connecting to the pager via the local 127.0.0.1 address).
| |
Thank you for all the help, it turns out i just needed to set it to private networks aswell as public, it's fixed now.. thank you again for your time and help :)
Take care | |
Thanks for following up with that info. A lot of people forget to do so once their problem is resolved, which of course doesn't help the next guy to have the same problem. I'll remember your solution for the next time this comes up.
| |
If you join another live game, even if not SS13, does it log you in as a guest or as your account? Because if it's still as guest, that fits the pattern of a communication problem.