Connecting windows 7 pro to a 2016 windows domain server

_{Monday, February 26, 2018 3:16 PM}

I have a system which has a new windows 2016 server, a mix of windows 7 pro machines (that cannot be upgraded yet due to proprietry software running on them not being compatible with windows 10) and windows 10 PC's.

All machines have worked OK on a windows 2008 domain server without issue.  Now with the 2016 domain the GPO's have been copied exactly.  Now when connecting the windows 10 machines all works fine, client profiles, share logon's etc all OK.  

BUT I just cannot get windows 7 PC's to logon.  They join the new domain no problem and from there the windows 7 PC's after logging on just report a critical error (after about 30-40secs) and restart.  No successful log-on.  If I disconnect the LAN cable from the windows 7 PC's they start up OK but with of course no network connectivity.

I have followed many internet guides - adding permission here and there (on win 7 and domain controller) even resorting full read/write on all sysvol shares etc but no luck.  

So my question is windows 7 PC compatible with windows 2016 domains.  If so, does anyone have a draft GPO configuration that works with Windows 7 machines.

All windows 7 machines report domain not found in the error logs and no gp found.

DNS OK - System originally worked on DHCP but now have reverted to fixed IP to see if that had any effect, but none.

I am now after many changes and various config's at a complete and frustrated loss.

Need to get this up and working or is the simple answer dump new servers and go back to original server 2008 machines that work every time.

Simple cry for HELP!

_{Monday, February 26, 2018 3:20 PM}

Please post an unedited ipconfig /all of DC and problem client.

Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management

Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

_{Monday, February 26, 2018 4:45 PM}

Dear Dave here are the configs one sever side, one client windows 7

Hope this helps

_{Monday, February 26, 2018 4:48 PM}

What is 192.168.1.87 ? If it is not a domain controller in same domain then it should be removed.

Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management

Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

_{Monday, February 26, 2018 4:53 PM}

Dave

192.168.1.87 is another member server with secondary DNS on board, it is not a domain controller just a file store - is working fine and fully responsive

Problem only with windows 7 pc's.

Everything else, printers, scanners, win 10 pc's and file store ok including all shares

_{Monday, February 26, 2018 4:58 PM}

Ok, well if you think its group policy related you could try moving a test desktop to a container that doesn't get the gpo. Also gpresult /H c:\gpresults.html may turn up something.

Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management

Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

_{Wednesday, February 28, 2018 8:25 AM}

Hi,
Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

Best Regards,

Frank

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com