New
#11
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 tofor example without the www most people go to google and google redirects to https which may be causing an issue....Code:http://msn.com
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
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.