Woolldoze Posted July 17, 2016 Share Posted July 17, 2016 I keep getting the "marionberry" error code. I'm on XB1, and I have the most recent firmware. I usually use a different router to play Overwatch, but I got this one for Destiny PvP because I'm tired of getting screwed by horrible hosts located somewhere near Timbuktu. The first time I plugged it in, I was able to log in, play games, and everything worked as expected, but today.. nothing. Here's my process: 1. Hard reset Xbox without turning it back on 2. Switch all ethernet connections to the Netduma router 3. Power cycle both router and modem 4. Wait until both are finished handling their business 5. Go to 192.168.88.1, and select the Destiny profile 5. Turn Xbox back on, boot up Destiny -> error "marionberry" I follow this same process with my normal router minus the 192.168... stuff obviously, and I'm able to log right in, no problem. What could I possibly be doing wrong? As it stands, this router is completely useless to me because it doesn't allow me to log into Overwatch, and now I can't even use it for Destiny. Thanks I tried factory resetting my Netduma. After factory resetting it, I added my xbox back to the list, and tried again. This time, it let me in, but when I tried to select my character, I got error code "vulture". Did it two more time, same thing happened. I hard-reset my Xbox, and now it's back to the marionberry errors. This is very frustrating as, like I said, this renders my Netduma completely useless. Just an FYI, after reading the terms of service, it looks like I have two weeks after receiving it to return it for a refund. If this isn't worked out by Sunday, July 24th, I'd like to go ahead and send it back for a refund. $200+ is a crazy amount just to kill lag, but it's an even crazier amount for a plastic brick. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted July 17, 2016 Administrators Share Posted July 17, 2016 Hey, welcome to the forum. You should be able to access online on both of those games with no issues at all. Are you seeing anything appear as blocked when booting up the game? Can you take a screenshot of the entire Host filtering page please. Link to comment Share on other sites More sharing options...
ColonicBoom Posted July 17, 2016 Share Posted July 17, 2016 'Vulture' means the game thinks you don't have an Xbox Live account. Has your Xbox Live run out? Are you trying to play over wifi? Link to comment Share on other sites More sharing options...
Woolldoze Posted July 17, 2016 Author Share Posted July 17, 2016 Hey, welcome to the forum. You should be able to access online on both of those games with no issues at all. Are you seeing anything appear as blocked when booting up the game? Can you take a screenshot of the entire Host filtering page please. Thanks for the reply. I booted it up today, and Destiny let me right in. I then tried Overwatch, and it gave me the BC-152 error at the log in screen with a host just north of me. I quit the game, and it let me right in with a host far to the west of me. I moved the geofiltering radius around, quit the game, and now no hosts are popping up to my screen. It's nothing but BC-152 error's again. Went back to try Destiny again, and no hosts are popping up, and I'm back to getting marionberry errors. A have a screenshot of when I was connected in Overwatch, but all other cases didn't have any hosts show up, so there's nothing to show: Do you think that there could be something wrong with the router? I'm using default settings, and it continues to fail. Settings: 'Vulture' means the game thinks you don't have an Xbox Live account. Has your Xbox Live run out? Are you trying to play over wifi? I played all day yesterday with my other router, and it's wired in in both cases. It has something to do with the Netduma router. Link to comment Share on other sites More sharing options...
Woolldoze Posted July 17, 2016 Author Share Posted July 17, 2016 Update: Went into my XB network settings, and I had my DNS set to my other router. Destiny and Overwatch both seem to be working fine. I'm thinking that may have been the issue. I'll let you know if anything changes. I feel like an idiot though. Thanks for your help. Link to comment Share on other sites More sharing options...
antithesis Posted July 17, 2016 Share Posted July 17, 2016 Update: Went into my XB network settings, and I had my DNS set to my other router. Destiny and Overwatch both seem to be working fine. I'm thinking that may have been the issue. I'll let you know if anything changes. I feel like an idiot though. Thanks for your help. That definitely sounds like the issue. We're all idiots at one time or another, don't sweat the small stuff. Link to comment Share on other sites More sharing options...
Netduma Staff Netduma Jack Posted July 18, 2016 Netduma Staff Share Posted July 18, 2016 Seems like the issue is resolved; issues like that are often simple to solve. Let us know if you have any more problems! Link to comment Share on other sites More sharing options...
ColonicBoom Posted July 18, 2016 Share Posted July 18, 2016 Update: Went into my XB network settings, and I had my DNS set to my other router. Destiny and Overwatch both seem to be working fine. I'm thinking that may have been the issue. I'll let you know if anything changes. I feel like an idiot though. Thanks for your help. Happens to the best of us sometimes - it's the best way to learn stuff. If you set the DNS / IP etc to 'Automatic' on the Xbox then it will just pull the settings from the Netduma. Glad you're sorted and thanks for the update. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.