{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/3/2025 10:18:49 PM
1
Hello there,
Thank you very much for reaching out to us. I'm sorry to hear that you are receiving this error code. While the issue may very well be coming from the use of Remote Play and any limitations that may come fro the device you are using to Remote Play with, we recommend following our [url=https://help.bungie.net/hc/en-us/articles/360049496531-Network-Troubleshooting-Guide]Network Troubleshooting Guide[/url] and our [url=https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types]UPnP and Port Forwarding Guide[/url], in the event the issue may stem from a NAT-related issue. When handling the UPnP and Port Forwarding, please use each method separately. These two methods should not be used at the same time.
English
-
I have looked at the network. And it is when I enabled remote play on my Xbox that the Xbox started to have this issue. I don't have this issue when I do not have this issue on remote play it is only on the Xbox that is physically plugged in to the router. I would like to know if Remote Play is the issue why on Destiny's end is it an issue just because I want to use Remote Play?
