Jump to content

Netduma Fraser

Administrators
  • Content Count

    25,408
  • Joined

  • Last visited

  • Days Won

    325

Everything posted by Netduma Fraser

  1. You're good to go. Please do not reboot before upgrading. You're good to go. Please do not reboot before upgrading.
  2. You're good to go. Please do not reboot before upgrading. We could not access your router. Please ensure the R1 WAN IP from device manager is in the DMZ of your ISP hub and that remote access is ticked in misc settings. You're good to go. Please do not reboot before upgrading. You're good to go. Please do not reboot before upgrading. You're good to go. Please do not reboot before upgrading. We could not access your router. Please ensure the R1 WAN IP from device manager is in the DMZ of your ISP hub and that remote access is ticked in misc settings. We could not access your router. Please ensure the R1 WAN IP from device manager is in the DMZ of your ISP hub and that remote access is ticked in misc settings. You're good to go. Please do not reboot before upgrading. You're good to go. Please do not reboot before upgrading. You're good to go. Please do not reboot before upgrading. You're good to go. Please do not reboot before upgrading. You're good to go. Please do not reboot before upgrading. You're good to go. Please do not reboot before upgrading. You're good to go. Please do not reboot before upgrading.
  3. They have definitely been added to the cloud so please try reapplying it to flush the cloud. That's fine, as long as auto&bleeding edge is ticked and applied it will work. Has the issue been resolved for you?
  4. Hey guys, really sorry for the delay. The team who does this is abroad for business currently. We will make it the top priority to get them done on Monday morning. Apologies for the inconvenience and thank you for your patience.
  5. Update, don't do that. Have updated auto&bleeding edge cloud to remove the error on PSN. Please allow up to 4 hours for it to propagate. If they're both ticked but the manual settings that are greyed out say a previous cloud don't worry about this. Auto/bleeding edge will overwrite this.
  6. Please go to auto&bleeding edge cloud and see how you get on. Someone else posted an ID for PS so will add that to the cloud as well. Are you also getting something blocked with strict on? Is both auto&bleeding edge ticked and applied? Otherwise just choose 25, 18, 25 Are you getting something blocked with strict on?
  7. Tick them both and apply yes. You don't need to wait for anything like that specifically, just that it can take up to 4 hours to work how it should
  8. We'll try and give you as much information as possible to diagnose your connection
  9. Instead of manually choosing now do auto&bleeding edge cloud and apply as you would do usually. Please allow up to 4 hours for the cloud to propagate.
  10. I believe I have completely fixed the issue now. So much so I had put it to the auto&bleeding edge cloud so please go back to that and let me know how you get on. Please allow up to 4 hours for the cloud to propagate.
  11. Please now try: 23 17 25 and 23 18 25 Please keep in mind it may take 4 hours to propagate. Going to work on another cloud tonight for release tomorrow. Thanks for your patience and feedback.
  12. Great suggestions guys, keep them coming. We'll see what we can do!
  13. Here are two further clouds to try, remember it may take 4 hours to propagate. 22 16 25 I believe this one is what works the best: 22 17 25 Give me your feedback and if like me you found the latter to work I shall move it over to bleeding edge.
  14. No conclusive information from anyone thus far so I took the console home this weekend and will test myself as it should be a lot quicker. Will let people know what I find/if I need to conduct 1 on 1's for further info.
  15. What cloud were you on? As this is in 21 already. So this appeared as a padlock? This is a bungie server so probably isn't related to NAT
  16. We could not access your router. Please put the R1 WAN IP from the device manager in the DMZ section of your ISP hub. You're good to go. Please do not reboot before upgrading. You're good to go. Please do not reboot before upgrading. We could not access your router. Please put the R1 WAN IP from the device manager in the DMZ section of your ISP hub.
  17. Thank you for the feedback! Okay interesting. When it's set to auto & bleeding edge the numbers you see won't change but it will be changed in the background. Okay let me know! Possibly, though if the issue persists it would be good to see what's happening for improving the cloud.
  18. Hey guys, so with recent updates people are seeing NAT issues and being unable to connect to games. I believe this is due to server changes on the game/online service i.e. adding new ones, repurposing them etc. We are aware of this and actively working to resolve the situation. Meanwhile as a workaround have your console off, disable the Geo-filter, boot up the console & game and then enable the Geo-filter once you're in the menu and able to search. You should be able to filter as normal. Keep auto&bleeding edge cloud enabled and applied whilst you do this. I will be putting out test clouds for people to try - keep in mind it may take up to 4 hours to propagate. Please let me know if the issue is resolved depending on the cloud you're on. If you have this issue and willing to help please let me know if you are available for a 1 on 1 and it will vastly speed up the process. For test clouds disable auto&bleeding edge and choose numbers for Whitelist, Game server & Map manually. Please only choose these if you are aware that they may not resolve the issue but you are willing to help. Otherwise please use the workaround until we can fix it. Thank you for your patience. UPDATE: Please go back to auto&bleeding edge cloud and apply. This should fix any of the issues you were seeing. Please allow up to 4 hours for the cloud to propagate. 1st: 20 14 25 2nd 20 15 25 3rd 21 14 25 4th 21 15 25 UPDATE Here are two further clouds to try, remember it may take 4 hours to propagate. 22 16 25 I believe this one is what works the best: 22 17 25 Give me your feedback and if like me you found the latter to work I shall move it over to bleeding edge.
  19. I believe you started your own thread with this question and I answered it there You can put it in the DMZ that is fine. Just ensure you connect ALL devices to the R1 to make the most of the features. Would recommend disabling the wifi on the Verizon to prevent devices automatically connecting to it.
  20. By that do you mean you've put the R1 in the DMZ? We still couldn't connect. If you have put it in the DMZ disable UPnP/any port forwarding on the hub. You're on the latest upgrade so you don't need to do anything. Can you post a new thread regarding your issue please, if its the one I'm thinking of change cloud to manually use 21, 15, 25 please.
  21. When we get to that we'll endeavour to get that implemented.
  22. We could not access your router. Please ensure the R1 is in the DMZ of your ISP hub and that remote access is ticked in miscellaneous settings. You're good to go. Please do not reboot before upgrading your router.
  23. You're good to go. Please do not reboot your router before upgrading. You're good to go. Please do not reboot your router before upgrading. Not good I'm afraid. Less. We couldn't access your router. You have...one chance to beat this thing. Put the R1 in the DMZ of your ISP hub and ensure remote support is ticked in miscellaneous settings.
×
×
  • Create New...