FYI, this bug's actually fixed as of the 1.2.0 "Better Together" update, see the Realms 155 bug for more info. So you're probably better off filing a new bug for your Xbox issue.
Yeah it's working great now. My biggest problem now is we couldn't agree on Survival or Creative and ended up with one on iPad and one on Windows.
Thanks!
--Manny
Hey! the big 1.2 update actually CONNECTED
OMG I'm so embarrassed about throwing a mini fit. Wow, though, it's been a year already.
Is Racknet configured to try successively lower MTU's? It does that by default. Seems like when I was poking around last year, it seemed to be a MTU issue with my ISP.
C'mon guys, you owe me like $12 or $16 by now, is there really no one at Mojang who knows how to connect two computers over the internet? Did you try asking Microsoft Research maybe?
I configured my router for ipv6 (newly supported in 1.1.7) using tunnelbroker.net, but still no go.
Still broken in 1.1.7. It would be nice if there were a way to test without burning money on a useless subscription. I had subscribed to test the free Proton VPN service (nope), so I was able to try 1.1.7. I did find a stupid expensive workaround, though. I have no less than 4 broken screen iPads, so I took the best of the bunch and just have it playing server for us. Can't really suggest that for everybody, lol.
I noticed recently I'm on a double-nat. The ISP's wireless modem is assigning a private ip to my router (192.168...).
0.16.1 doesn't connect
No 0.16.0 still can't connect. I read that MTU might be to blame. For some reason my isp MTU is 1480 instead of 1500. I tried the router at 1480, and also at 1000 and 576. None of those settings helped. I'll check out the other bug, thanks.
Following up on the Microcell experiment, I got a free trial of NordVPN. If I connect to NordVPN via TCP, I can connect to Realms. If I connect via UDP, I can't even load the NordVPN webpage. So definitely something weird with UDP. Apart from Minecraft and NordVPN, however, I haven't seen other problems with UDP. Everquest 2, for example, works fine. Again, more details about the failure would be helpful in contacting my ISP.
Well here's a goofy experiment. We have an AT&T Microcell. I disabled the WiFi so the phone uses the Microcell 4G internet, which goes over the same internet connection as the WiFi, and it does connect. Unfortunately, that's not a workable solution, but it is an interesting result. Earlier I tried the TunnelBear VPN, but it didn't work over that.
I would like to talk to my ISP about the issue, but without any ip addresses or other details about the failure, I just don't know what to tell them.
Realms has never connected from home on any of our iOS devices across several versions of MCPE. It does connect on the same device from my work. There's no feedback other than "Unable to connect to realm." I've tried everything I could think of on my end, including updating the router firmware and disabling the firewall. I'm finding it impossible to troubleshoot without any more specific information about where MCPE is trying to connect to and what the nature of the failure is. I've tried network monitoring tools to determine at least where it's trying to connect to, but so far have been unable to identify any specific traffic that starts as MCPE is trying to connect. This has been going on since I originally subscribed on June 13. I would very much like to have at least more details about connection errors to help investigate things on my end.
This is the last message I got from support:
"Sorry, but I'm not sure about what could cause it in that case. If it doesn't work, you could ask Apple for a new refund."
So it seems my only hope is fixing the bug.
I currently have two active subscriptions, and the game (or more likely the server the receipt is being forwarded to) is failing to find either of them in the receipt.
Having seen this from the the development side, I know Apple doesn't make it easy, but the fix really is to check every transaction in the receipt to see if any of them contains an unexpired subscription.
Thanks,
--Manny