Laptop won't connect to either Liahona or LDS Access

[heatherawood]

My Dell laptop won't connect to either Liahona or LDS Access, which is weird because I have another laptop just like it that will. I'm trying to connect at a seminary building. It will sometimes connect for a few minutes right when I get to the building, but then it disconnects and won't reconnect. The splash page has never popped up, so I've tried going straight to https://guestwirelesstermsofuse.churchofjesuschrist.org on both internet explorer and chrome right when it connects for those few minutes, but the page doesn't load fully like it does on my phone or other laptop. Anyone have any guesses what I need to look for on the laptop?

[jdlessley]

My Dell laptop won't connect to either Liahona or LDS Access...

LDS Access should not be available because it was transitioned to Liahona in April and should no longer even be on the list of available networks. I would concentrate on connecting to Liahona only.

It will sometimes connect for a few minutes right when I get to the building, but then it disconnects and won't reconnect.

The brief connection and disconnecting is sometimes normal. The disconnect is because the policy acceptance page has not been displayed and acknowledged. It is possible the acceptance page is not displayed because popups are disabled on your browsers. Try turning them on, at least for the churchofjesuschrist.org website.

If turning on popups for churchofjesuschrist.org does not work for the next attempt then try disconnecting from the network by clicking Forget and then reconnecting by selecting the Liahona network again and entering the password. This should restart the network connection and enable the acceptance page/popup.

[winjesluck]

Are you able to check your laptop's is getting it's DNS server address from DHCP and is not set manually.
That's one of the reasons I've had issues connecting to the Liahona network and not getting the splash page before.

[tylergraf]

I had my DNS set to 8.8.8.8. Removing that to use the network's default DNS fixed it for me.

[Roontek]

Confirming that having my DNS set to CloudFlare caused the issue. Had to remove the rule in MacOS and allow it to run off of the standard DNS.

[warddb]

Can you explain how to do what you did on a pc and mac for a non-techy person?