Windows 10: Connect to Domain - Browser Security Issues

I gave up trying to fix a different issue with the Microsoft Store, and decided instead to do a full Windows 10 Pro reinstall. It was too many quirky problems one after the other.


Here is the dilemma I am having that is absolutely driving me APE.


Format - Install Windows 10 - use my personal (or local offline) account as the first login.


Use web, login to Gmail, Office 365, MS accounts NO problem.


Join domain (I am an admin user, and domain admin), go to Gmail/MS/Amazon can’t login anywhere. Amazon just shows links and text no pics. Plenty of HTTPS sites appear image blocked. I’ve verified IP address settings changed DNS servers. Nothing is working I can’t login into anything, anywhere.


Once I am on the AD it’s over via web browser access. Now I can login to gmail via Outlook (Office 365) I can login to Evernote using my gmail address through the Evernote app in the store. I CANNOT login to Evernote via a web browser and the gmail login does not go beyond the “Enter email address” screen hitting Next does nothing. Downloading Chrome same thing. Cannot even download vivaldi.


NO one else on the domain has this problem, and I didnt before either. I even deleted my domain user and created another with domain admin and admin access... added the computer to the domain as well — Same problem with the web browser. Its driving me nuts!

:)

 

Raising the windows domain and forest issues?


hi,

I run a domain that was all 2003 r2 servers. I recently upgraded all my domain controllers to windows 2012 r2.
That went off without any problems.. Our trust relationships had no issues also.

My first step was to raise the Domain and Forest levels past 2003 to 2008. This went off without a hitch.
These are the features for raising the levels to 2008:

• Features and benefits include all default Active Directory features, all features from the Windows Server 2003 domain functional level, plus:
• Read-Only Domain Controllers – Allows implementation of domain controllers that only host read-only copy of NTDS database.
• Advanced Encryption Services – (AES 128 and 256) support for the Kerberos protocol.
• Distributed File System Replication (DFSR) – Allows SYSVOL to replicate using DFSR instead of older File Replication Service (FRS). It provides more robust and detailed replication of SYSVOL contents.

Forest Level Windows Server 2008

• Features and benefits include all of the features that are available at the Windows Server 2003 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2008 domain functional level by default.

My next step is to raise the domain and forest to 2008 r2, then 2012, and finally 2012 r2. I have been trying to find out exactly what I could expect from raising the Domain and Forest for each step.

The step involving 2008 r2 seems relatively a non issue. But getting the couple of new features seem very nice

Domain Level Windows Server 2008 R2

• All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus 2 new features

Forest Level Windows Server 2008 R2

• All of the features that are available at the Windows Server 2003 forest functional level, plus the following features:

• Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. <== New Feature very cool
• All domains subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default.

Here is my big concerns for the next raising of domain and forest to 2012.

Forest Level Windows Server 2012:

• All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features.
• All domains subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.

Domain Level Windows Server 2012 R2: <=====Need to investigate more and why this post

• DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer:

• Authenticate with NTLM authentication <==============(what issues may arise)
• Use DES or RC4 cipher suites in Kerberos pre-authentication
• Be delegated with unconstrained or constrained delegation
• Renew user tickets (TGTs) beyond the initial 4-hour lifetime

Will this affect my exchange anywhere users with remote access authenticating either clear of NTLM???
and what would/may not to work properly day 1 when I raise the domain and forest to 2012. I cant really find anyone that can answer a straight question.

Has anyone gone through this? what problems did you have, if any , if a lot???

Any thoughts and suggestions will be much appreciated??

thanks


- - - Updated - - -

One more point... I am not sure if I posted this to the correct forum.. So if I was wrong and it should be in a different one..
PLEASE LET ME KNOW

 

EDGE Browser issue with secured login (HTTPS)

Hi Ram,

It is possible that the issue is due to compatibility or the browser components causing this matter to occur. We
suggest that you reset Internet Explorer 11 and Edge
and check if there are any changes. To reset these browsers, refer and follow these links and guide:

Edge:

Kindly refer to this
link from TechNet.

Internet Explorer 11:

To reset Internet
Explorer 11, follow these steps:

• 
  On the upper-right corner, click the
  Gear icon
  beside the
  Smiley icon.
  
• 
  Choose
  Internet Options.
  
• 
  Under
  Advanced
  tab, click on
  Reset.
  

Update us on how it goes.

Regards.

 

can't connect securely to this page

Hello Kelly,

To better assist you with your concern, I'd like to know the following:

• Confirm which build is currently installed on your device. To check, follow the steps below:

1. Press Windows key + R, then type in winver.
2. Click OK.

• What browser are you using? Does the issue also happen to other browsers?
• Were there any recent changes made prior to this issue?

Meanwhile, I'd recommend performing the steps in this article
to troubleshoot network connection issues in Windows 10.

Looking forward to your response.

Regards.