b00stg0d Posted October 29, 2016 Share Posted October 29, 2016 I had this issue a few months ago and now it's back. I will set my geo-filter over a desired location with an area of 700-1000 miles and it will still connect me to dallas or chicago based on what IP(routing) I am using at the time. What is the dealio? Starting to lose faith. The only reason I have the two netdumas is for the geo filter and it seems to be getting to be the norm that it's either not working. I've rebooted, let it sit, reset, hard reset.... I'm at a loss. Link to comment Share on other sites More sharing options...
iAmMoDBoX Posted October 30, 2016 Share Posted October 30, 2016 I had this issue a few months ago and now it's back. I will set my geo-filter over a desired location with an area of 700-1000 miles and it will still connect me to dallas or chicago based on what IP(routing) I am using at the time. What is the dealio? Starting to lose faith. The only reason I have the two netdumas is for the geo filter and it seems to be getting to be the norm that it's either not working. I've rebooted, let it sit, reset, hard reset.... I'm at a loss. I've had this happen before and a reboot fixed it... Try this: Reboot, delete the device, add it again on the geofilter in a different "slot" at the top. Link to comment Share on other sites More sharing options...
b00stg0d Posted October 30, 2016 Author Share Posted October 30, 2016 I've had this happen before and a reboot fixed it... Try this: Reboot, delete the device, add it again on the geofilter in a different "slot" at the top. I will try this now, thanks. I am worried there may be another cloud issue as before when this occurred to me a few days later Fraser had to do some cloud testing and it also involved not getting OPEN NAT with filter enabled. I am also having that issue again. Link to comment Share on other sites More sharing options...
b00stg0d Posted October 30, 2016 Author Share Posted October 30, 2016 I've had this happen before and a reboot fixed it... Try this: Reboot, delete the device, add it again on the geofilter in a different "slot" at the top. NO such luck.... This got even more strange. I selected the filter waited a few minutes just in case, it took me right into a game but instead of going to the usual Dallas server it went to East Coast yet I have a 17ms ping??? That's incorrectly marked for sure cause my base ping to East coast is 50ms, Anyway check the screenshot, someone in Antartica is connected.... WTF?!?! Something is surely EF'd up FO SHO! Even shows a lock symbol on the server I am on so I guess it locked some but not this mis-marked one? Link to comment Share on other sites More sharing options...
b00stg0d Posted October 30, 2016 Author Share Posted October 30, 2016 Backed out of lobby, next match, same crap.... Link to comment Share on other sites More sharing options...
b00stg0d Posted October 30, 2016 Author Share Posted October 30, 2016 very next lobby Link to comment Share on other sites More sharing options...
Zennon Posted October 30, 2016 Share Posted October 30, 2016 Try. Turn off your console, turn on the geo, refresh the host filtering page, turn on your console. Link to comment Share on other sites More sharing options...
b00stg0d Posted October 30, 2016 Author Share Posted October 30, 2016 tried that Zennon. no luck. results in NAT Failed w/ geo filter on before going into game or testing network. Similar to last issue with cloud update and testing. Link to comment Share on other sites More sharing options...
b00stg0d Posted October 30, 2016 Author Share Posted October 30, 2016 OK, I unchecked the cloud and applied rechecked and applied and it seems to be doing it's jobby job now. SHEESH! Thanks for the help guys! Link to comment Share on other sites More sharing options...
Zennon Posted October 30, 2016 Share Posted October 30, 2016 Great, I will close the thread Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.