Spaceboy 2573 Posted September 1, 2014 Posted September 1, 2014 (edited) Recently i have noticed that MBS is using the external IP rather than my dyndns address as what should be used for remote access. It used to work properly but something recently has broken it. my DYNDNS name is included in the right field in advanced settings but MBS seems to be ignoring it and using my non-static IP instead. latest dev build Edited September 1, 2014 by Spaceboy
psykix 97 Posted September 1, 2014 Posted September 1, 2014 Probably something to do with MB Connect which is being worked on at present.
DrWatson 62 Posted September 4, 2014 Posted September 4, 2014 Recently i have noticed that MBS is using the external IP rather than my dyndns address as what should be used for remote access. It used to work properly but something recently has broken it. my DYNDNS name is included in the right field in advanced settings but MBS seems to be ignoring it and using my non-static IP instead. latest dev build Yes I see this too it is most annoying when trying to demo mb3 to someone and the client (android) cant connect because it has a non static ip address as the external ip. 1
TolkienBard 58 Posted September 13, 2014 Posted September 13, 2014 Apparently I started having this problem last night and am still experiencing it at this very moment.
Happy2Play 9780 Posted September 13, 2014 Posted September 13, 2014 What version are you on? I saw this in the beta 3.0.5366 but was resolved when it became released/official.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now