Problem with logging onto Corporate WiFi Networks (the rest is fine)

LMiller7 said:

Have you contacted the company IT staff about this?

Yes, that is their Help/Dervice Desks. They were quick to assess that the problem was mine as it was my laptop (and no one else was having this problem).

Kari said:

[/LIST]

This might be too obvious but have you tried to enter the URL for the sign-in page (highlighted in above quote) manually in a browser after you have connected WiFi? Your IT support should be able to give you the URL.

Yes, I did. What happened was after providing the UID-PWD combination, I was told "Login Successful" but I still did not have an actual connection (e.g. able to surf to a URL). When I looked at the WiFi point's status, I read that it was not connected. I'll go through that sequence again today to make sure the above is correct.

The only things I can think of that you can try is:

1) Open IE, not Edge, and go to internet options -> connections -> LAN settings and make sure its not using a proxy
2) When you connect, run ipconfig in a command prompt and take note of the default gateway...try accessing that IP through your browser (ie. http://192.168.1.1)
3) I've heard of firefox having issues so try edge or IE or even chrome, and go to

Code:

http://msn.com

for example without the www most people go to google and google redirects to https which may be causing an issue....

Other than that, I'm out of ideas :)

With the help of one of the corporate ICT guys, the problem was identified and resolved.
The problem was that I had a specified a DNS server address to be used in the IPv6 properties which was not recognized in the corporate network.
The solution was to change the setting such as to obtain a DNS server address automatically.

Thanks for the help

Quarantain said:

No, my default browser is Mozilla FireFox.

reset the network device settings to default.

I assume you are logging into an Active Directory domain.
When logging into a domain the client must first find a domain controller. With Active Directory a client will always do that by using DNS, even when the domain controller is on the local network. If there is a problem with DNS, and using the wrong DNS server is certainly that, then the client may be unable to find a domain controller and the login will fail.

I suspect that is what was happening.