Hi!
Trying to access this publicly accessible web page: https://securelogin.bmw.com works fine to load when connected to the Internet via my mobile phone, but when connected to our Meraki network it won't load. Just getting a time out. I'm wondering where to start troubleshooting this?
If I do an nslookup I get the same result from both networks (resolves to the same IP number), so don't really know what the problem is. 🤔
Solved! Go to solution.
The reason for my trouble in this thread was that we had ”Statics routes” setup in:
Security & SD-WAN -> Addressing & VLANs
And the IP address for https://securelogin.bmw.com/ was covered within that range and therefore the the traffic was being routed internally instead of externally.
Sorry for the confusion and thanks all for trying to help! 🙂
Hello @Tintin
First thing to try is to see if a reload of the site has the same outcome.
Next step would be to clear the browser cache.
If both tries didn't work, you could try to power off the Meraki network and turn it back on.
Another step would be to change DNS-server on your settings. Googles DNS is 8.8.8.8 as example for IPv4.
Cheers
Thanks so much for your reply! 🙂
All of this has been tried except the Meraki network power off. What is the recommended way to do that by the way? 🤔
If that also don't work, what is the next step?
no idea what the recommended way is.
I usualy just pull the plug since there is no power-button on my device.
The reboot-option can be tried, even it didn't help solve connection problems I have had in the past.
When I shut down/restart my Network, I usualy turn off all devices and then start up the devices one by one with some waiting time in between. (Modem -> Router -> Switches -> Access-Points -> NAS -> Printer -> PC)
@Tintin
What happens when you try to open https://160.46.231.113/login out of your Meraki network?
If you can open the page it is clearly a DNS issue.
The reason for my trouble in this thread was that we had ”Statics routes” setup in:
Security & SD-WAN -> Addressing & VLANs
And the IP address for https://securelogin.bmw.com/ was covered within that range and therefore the the traffic was being routed internally instead of externally.
Sorry for the confusion and thanks all for trying to help! 🙂