Open Nat but still numerous issues

Im having a few different issues i think may all be related.

1 - Friends list can be seen some times and other times it says cannot access friends right now (more times not available)

2 - while trying to look at my settings i get errors saying cannot change till service is

3 - Having numerous issues connecting to friends on games. Had trouble on titanfall and now destiny.

4 - Error while playing destiny that kicks me off saying I do not have permission or my account is signed on somewhere else. My accounts only on my xbox and i never got a message saying my account was signed on on another counsel.

5 - Sometimes it takes 3-6 attempts to sign into my account.

6 - Various other issues saying Bungie servers are offline (i have friends playing and logging in and they are working just fine)

Couple notes.

I have forwarded ports to get my nat open but it is open.

I played for 3 hours earlier on wireless no issue then once the issues started the dont stop. I have tried plugging in wired and no help. ive went through all the router configuration helps on the support sites no help. tried contacting support but it wont
let he hit start chat saying my information is invalid.

Im at my wits end. any advice?

:)

 

Connection lost

I have a question for you, OP. Did your nat switching help with GTA? Mine is open and I still can't get in populated lobbies. And if I do, I get kicked within seconds.

 

Can't Receive Messages or Invites?

Also my nat is open & I have reset my router numerous times.

 

Have you restarted your router yet?

 

I just posted this same issue in another thread. I also have this issue. While playing destiny tonight it was craziness trying to chat with and view my friends. The only thing that works for me as a 24 hour fix is going into the alternate MAC settings and
clearing it. But, its only a 24 hour or less fix and it get annoying doing that all the time. Hopefully this does get fixed because this issue started in the last few months so one of the updates probably messed it up.

 

This very same thing has happened to me , terribly frustrating yet to find a solution