I don't know if I can open this topic. I updated my dev with the last xdk (7776 from 6995.1) with the recovery disc and now occurs a strange thing. All the connection test to partner.net (via launcher) or XBL (via dashboard) are satisfactory but when I'm in the dashboard and try to sign in xbl, it appears that you sign in but inmediatly you sign out, then you can't access for example to the bazar. But if you for example play a game you can sign in without problems, only when you are in the dashboard you are unable to sign in. Anyone has this problem or known why can occur this? thank in advance boys
I recommend waiting it out, Thats what happened with xbox live when the servers got full. If its still like that in a week I suppose then it might be a problem. Downgrade your version to see if partnernet marketplace works then, if it does. Then use that for all marketplace downloads untill the marketplace expires. I don't know, best advice I can give. - lsl
The servers should be fine if thats what your implying. I know quite alot of people so have recovered to this kernel and dont have this problem. Seems strange. Try recovering once more incase. Also for troubleshooting reasons and a hunch I have, try creating. New profile with this kernel and see if the problem still occurs on that. And you didnt change any settings lately have you? Well should I say, since the recovery, that coulve potentially caused this?
Well I will try again. I back to 6995.1 and no problems. Xenon, when I see this (when I have 7776) I tryed with a new profile and occurs the same. I forgot to say that the same occurs to a friend.
That's strange... never occured to me (don't have debug xbox 360, anyway) is there an "auto disconnect" option somewhere? i know it may look stupid, but it looks coherent.
No. If the servers were full that would happen to more people than just you, and wouldn't just happen on one specific kernal, as almost all of them use the same network. The two you stated do aswell.. Anyways I just ran by here because my friend went to the washroom and she'll be back in a bit so I'm going to end this post here. Anyways congrats.
So? Had it been a network overload, everyone in and out of that version would have experienced the same problem as you which they had not. I hope you see what I'm trying to say, a network overload doesn't just kill one specific kernel version's networking capabilities in the dash, for some people.
Sure that's strange allright... Just one "stupid" question. Does your friend have a XDK or a retail Xbox? never occured to me on retail... Maybe a ping problem? Devs usualy have "powerfull" Web connection, so maybe your ping isn't high enough. (the timeout may be different for a debug xbox 360) (I know this may look stupid, but if he changed nothing and that it isn't a server overload... what can it be, really?)
Now both devs (are devs) run fine without performing anything. We can's say what's wrong the first time.
Like I said its a matter of waiting. I never directly implied the servers were overloaded but it is clear that it was a server based situation as logic implies that when downgrading the individual was able to access partnernet and when upgrading the individual wasn't able to until time took its course. Microsoft has already begun to put in security to keep the service from overloading to prevent several of their last mistakes. If it was overloaded I wouldn't be surprised if the servers cap themselves to prevent public inconvenience. It only makes since. Thus if the servers were at its limit its plausible for it not to effect everyone. And even if the number of connections didn't meet its limit, its certainly server based. That much is certain.
You made all of that up with no proof however... You're just assuming... Yet others connected fine? Why would the server reject some... And only on a specific kernal...? ... So you're saying because the service is overloading, it decides to only kick two heard of people off of a service ONLY on that kernal, ONLY when their at dash? The servers aren't public. Also it would be a bigger inconvenience if the server capped itself. Sense*. And no it doesn't. So you're saying the servers with millions of people on Live won't crash, but the ones that stem off of the live server would die because it only has so many people... And yet again if it met its max bandwidth/connections, it wouldn't just reject two people in one specific kernel version only when they are at the Launcher. Yet again, how is it server biased if the server is still up and running and is still allowing more connections from other kernal versions, or the same in a different game.. It sends the same data signing in, so why would it fail only at the dash... That sounds more like a CLIENT problem... =| Common sense really.. =|
PN can act weird sometimes,yes it can has server problems from time to time but I wouldn't put to much thought into it.
I think you are way over analyzing the situation, and its not that big of a deal. I have had problems similar to this before. Its pointless just to make a public spectical of something like this just to prove your right, its really very pointless. I was just attempting to help off my own experience with the XDK. - outdated kernels cannot access the partnernet marketplace from my experience, I'm sure newer kernels may go hand and hand with that. - People have had trouble similar to this with xbox live, after dash updates not being able to sign in when others in different locations could. - I much rather believe someone then to doubt them, He clearly stated his friend wasn't able to either and switching kernels did allow him back on partnernet. I prefer to take the benefit of the doubt with people, this guy doesn't sound like a moron. All I said is this much is certain, as he stated one other person, other then himself had problems accessing PN with the new kernel, Obviously it wasn't the kernel as that remained the same and then suddenly partnernet was accessible thus I rest my theory that its server based. I'm not going to pretend to know how or why it happened that way, but neither should you, nor should you assume its the fault of the end user just because it works for you. Really there's no point in any of that other then just to say "hey, I"m right". I believe the original intent was to help the person asking the question not who is right. Clearly the situation was resolved. No need to pursue the situation further. - lsl
