BYOND Build Number:
Operating System:
Video/Graphics Card:
Game Hub/Link:
Internet Connection Type:
Firewalls/Routers:
Problem Description:
Steps to Reproduce Problem:
look I dont know any of this. Theres been a few topics that have this problem and this one user says the same thing about turning off md5 or whatever. I.DO.NOT know any of this. Im logged in and it signs me in as a guest, maybe we shouldnt be the ones to remove our firewall, maybe byond should get better software.
ID:294564
 Jun 20 2011, 8:03 pm
|
|
I have this same issue, however despite my firewall being configured to allow BYOND and dreamseeker both incoming and outgoing connections it still fails to log me in properly. Even when I turn off my firewall it doesn't work, and both my router and computer firewalls are configured properly and I guarantee I have no other firewall programs interfering.
| |
Argonus wrote:
I have this same issue, however despite my firewall being configured to allow BYOND and dreamseeker both incoming and outgoing connections it still fails to log me in properly. Even when I turn off my firewall it doesn't work, and both my router and computer firewalls are configured properly and I guarantee I have no other firewall programs interfering. This problem only happens when Dream Seeker can't talk to the pager but both programs can actually connect out to the Internet. The only way that situation is possible is if one or both programs have their Internet access partially restricted. Therefore, either another firewall is running or the firewall you have is malfunctioning or improperly configured. You may think you have ruled out all those possibilities but that can't be the case, or the problem would be resolved. (If you haven't already done so, you might need to start the pager fresh. If it was already open when you made the changes, it might have already failed to open a port.) Probably the easiest way to diagnose where things are going wrong would be to get some screenshots of your firewall settings for byond.exe and dreamseeker.exe (and dreamdaemon.exe as well, if you do any hosting), and a full list of the firewall's default rules. It's possible there's a setting you think is correct but isn't, or even that another rule in the same firewall could be interfering. If we can rule out all possibilities with that firewall, the only logical possibility left is another firewall you weren't aware of. [edit] One possibility I had forgotten about myself was that if you are using an nVidia video driver, it may have been installed with a network access manager that is basically a hidden firewall. Why a video card needs network control is a complete mystery to me, but it's entirely possible this is the problem. If it does turn out to be the case, what you need to do is disable it, which may involve uninstalling and reinstalling the driver. Google "nvidia firewall" for more information. | |
I don't seem to have any other firewall programs other than windows firewall, and I'm positive it is configured properly. I have even turned the firewall off completely to test it and it still has the same issues. Same thing happens even when I'm offline and trying to play locally hosted games on my own computer. Whatever is interfering with the connection between the pager and DS it's not my firewall, and I don't have a nVidia firewall installed on my computer or any others besides windows firewall. I've tried everything and I don't know what else to do.
| |
Argonus wrote:
I don't seem to have any other firewall programs other than windows firewall, and I'm positive it is configured properly. I have even turned the firewall off completely to test it and it still has the same issues. Same thing happens even when I'm offline and trying to play locally hosted games on my own computer. Whatever is interfering with the connection between the pager and DS it's not my firewall, and I don't have a nVidia firewall installed on my computer or any others besides windows firewall. I've tried everything and I don't know what else to do. As I said, you must have another firewall you are not aware of. nVidia was a possibility that I thought might pan out because many people who have nVidia cards don't realize that the manufacturer makes a firewall and that it is usually installed by default with the drivers. If you have an nVidia card at all, it's possible their firewall is in place and you just don't know it. Your antivirus software may also feature network protection services that function as a firewall. Bottom line: You absolutely, positively, most definitely have another firewall because that's the only thing that can cause the problem you're experiencing. So the solution now is to find it, so you can configure it, disable it, or uninstall it. If you get a list of tasks from your task manager I'll be happy to look that over to help you find the firewall. You can also go to a command prompt (find Run on your Start menu and type "cmd") and type "netstat -b" and that should give you a list of network connections and programs. If you're uncomfortable sharing those details over the forums, you can always email me at LummoxJR@aol.com. | |
I don't think I have an nVidia firewall since I use AMD, but I do use nVidia drivers but I think the firewall only comes with nVidia cards and not downloadable drivers.
Here are screenshots of all processes from all users on my machine (minus network and local services like svchost.exe): http://img40.imageshack.us/img40/7995/tasks1.png http://img69.imageshack.us/img69/6440/tasks2.png I should also mention I run windows 7. | |
Argonus wrote:
I don't think I have an nVidia firewall since I use AMD, but I do use nVidia drivers but I think the firewall only comes with nVidia cards and not downloadable drivers. My understanding is the firewall is part of the driver package. If you have an nVidia driver, don't assume you're not running the firewall. I'm not seeing anything indicative of that in your process list though. If you look at Add/Remove Programs (or whatever the Windows 7 equivalent is) it should usually show up there if it's installed. Here are screenshots of all processes from all users on my machine (minus network and local services like svchost.exe): I see a few references to Windows security center, so there could be something beyond the Windows firewall itself interfering. Other than that there aren't any smoking guns, but the app names are pretty vague. The SDHook service appears to be SpyBot, so I'd try also disabling that temporarily; if that fixes the issue then you should switch to some other equivalent software. I'm more curious now to see which services you're running, and also to see what netstat tells you as far as which applications are on the network. "netstat -b" is usually enough to show a lot of proxy connections if an antivirus program has a virtual firewall in it, for instance. | |
When I try to use "netstat -b" it says "The requested operation requires elevation". I'm rather stumped to what this means.
| |
i tried to email you but its not working is there anyway you can help me too?
| |
I'd be happy to help you, but you'll need to post a new topic so I can get your baseline information to work with. If this is the same issue where you keep joining games as a guest account, I can tell you for sure that you have a firewall interfering and that it needs to be configured to allow the BYOND apps to use the network.
| |
Let's just sort this out a bit.
Disregard what that other guy is saying, this is NOT a firewall issue. This has to be an issue with crappy BYOND coding. I'm getting this error, along with one that just hangs me at the 'launching byond world' blue screen. I've disabled every firewall, and allowed it through all my security problem. NVIDIA does not appear to even HAVE a software firewall. They have a hardware one built into certain graphics cards, but none recently. Simply put, wake the developers up and get them to fix this crippling bug. | |
Meronz wrote:
Let's just sort this out a bit. If you're going to resurrect a thread after three months, get your facts straight. I have explained in many posts why this is a firewall issue, and I will do so again below. I'm getting this error, along with one that just hangs me at the 'launching byond world' blue screen. The stuck splash screen is a separate issue. Whether the same cause is triggering it, I don't know. The splash does involve network traffic (because DS needs to talk to the pager, which owns the splash), so fixing your firewall could fix that too, but I've heard of stuck splash screens in other situations where this does not apply. I've disabled every firewall, and allowed it through all my security problem. As I've said to many others before and will say again to you now, you only think you've disabled every firewall. You have not. And you don't even need to disable them, except the nVidia one which has no right to exist; you just need to make sure they're all configured properly. (Disclaimer: The last time I ever used a firewall that allowed access on a per-program basis, I found out it was buggy and stopped using that one. So disabling is still something you can do as part of the process of working through the issue, since disabling a firewall outright at least takes it out of the equation.) A hardware firewall must be hooked up to the network directly to function; a GPU can't have a hardware firewall unless a network cable is plugged into it. NVidia does in fact have a software firewall, and this is well documented. I don't know if they've stopped this stupid practice or not, so perhaps their newer cards are firewall-free. If so, good for them, but all the information I've run across says they've had a firewall for years now. It's called several things, like "nVidia Network Access Manager" or "ActiveArmor". I frequently tell people to check for this though because on several occasions it has turned out to be responsible for this and a number of other issues. Here's an article on the subject that describes how the user discovered they had not properly found or disabled the nVidia firewall, and what they went through to fix it. It's an old article but many of its precepts would still apply with newer versions. http://groups.google.com/group/ microsoft.public.windowsxp.network_web/browse_thread/thread/ 47ccfdec52028db3 Simply put, wake the developers up and get them to fix this crippling bug. Well as one of the developers, let me explain the "login as guest" issue in detail. Dream Maker aside, BYOND consists of three programs: The pager, Dream Seeker, and Dream Daemon. All three of these need to use inbound and outbound network traffic, although DS doesn't really need to worry about inbound traffic unless it's hosting. To login on your account, the pager talks to the hub. So when you see "Logged in as Meronz [online]", you know the pager has successfully made an outbound connection. (This is not a persistent connection.) The pager opens a listening port we call a proxy port, so that Dream Seeker and Dream Daemon can talk to it so they can be told what account you're using. If your pager ever says "failed to open server port", that's one of several common firewall problems, and it means that a firewall has forbidden the pager to listen for inbound traffic. That message in fact is a dead giveaway of firewall problems, because nothing else (short of hardware problems or massive system instability) can cause that. Now assuming all goes well to this point and you have not seen any such message, let's say you join a game and it starts up in Dream Seeker. Now DS is telling you the pager is offline and it has to connect as a guest. In plain English, this is DS's way of telling you "I can't talk to the pager on its listening port, so I can't get your identity info and I have to tell the game this is a guest account." DS knows the port it needs to contact because it gets written to your config files by the pager; this message occurs because DS has tried to contact the pager, and failed. Only one thing (again, short of hardware failure or system instability) can cause two programs on the exact same system to fail to communicate: A firewall. The only possible conclusion is that one of the drivers hooking into the network stack--which is what a firewall is--has prevented that communication. Either it kept the pager from opening a port (the pager should tell you this), or it kept traffic from coming in once the port was open, or it kept DS from opening a port to the pager, or it kept DS's traffic from going out on that port. Four possibilities, basically pointing to one program or the other being denied access. When that happens, there are exactly two questions to ask: 1) Was the traffic blocked at the pager end, the DS end, or both? 2) Which firewall blocked the traffic? Just because you couldn't find your missing firewall doesn't mean you don't have one. Some firewall is still active and interfering with the DS-pager connection, because there is no other possible thing that can interfere with it. I realize it's easier to give up and blame everything on the software, but software doesn't fail to use the network except when a firewall makes it fail. I'm happy to help you through your issue, but you need to accept that there is in fact an issue with your firewall. I understand this situation very well, and I can tell you with absolute certainty that the only thing standing between you and a fix for this guest-account issue is a willingness to find the hidden firewall and deal with it. Post some screenshots of your firewall configuration screens, list what's running in the task manager, and a list of services in Windows would also be helpful; we can work through these one at a time to avoid you having to do all that at once. I'm also more than happy to investigate the separate bug with the stuck splash, for which I will need details and a reproducible test case--however I suspect that will resolve itself when the network functions properly. The only thing I'm not happy, or willing, to do is tolerate users giving other users bad advice. You're telling someone to give up rather than try to fix the problem. That won't help anyone, because there is no miracle software upgrade that will let us work around a firewall--that's kind of the point of firewalls. | |
You don't need to disable your firewall entirely. What you do need to do is make sure it is configured correctly. All of the programs in the BYOND suite need to be able to use outgoing and incoming TCP connections. If there is a version or hash check (like I said, it may say something like MD5 or SHA), you need to disable that.
If you are having trouble configuring your firewall, feel free to post a screenshot or describe the dialog and I'll try to help you through it.