Windows Server 2016 Essentials - Unable to Install Client Software


i have been running windows 2012 essentials , windows 10 clients several years.  

i purchased windows 2016 essentials , running virtual machine on hyper-v server 2016.  (windows 2012 essentials running on hyper-v server 2012.)

wse 2016 seems install without problems, have not been able install windows connector software on windows 10 clients.  i have tried connector installation 3 different windows 10 workstations.  one of these 3 running vm on same hyper-v 2016 server (a brand new windows 10 installation).  (note - reset windows 10 workstations before trying install wse 2016 connector software, i.e., none of windows 10 workstations still connected older wse 2012 domain.  and wse 2012 server not running during time i've been trying install wse 2016.)

for wse 2016 point of entering userid / password, after long delay dialog box says -

cannot connect computer network

the server not available.  try connecting computer again.

i able ping server without problems , ping windows 10 workstation server.  if use incorrect userid or password error message.  so seem communicating server.

i have not found error messages in event log explain what's going wrong.

i tried capturing packet trace.  i see activity going on between windows 10 workstation , server, there new tcp connection gets reset server.

thanks can provide.


windofchange

mariëtte,

my wse 2016 server first ip address dns configuration, after comment recall seeing home office users didn't have complete dns configuration in network had problems.

i restructured dns setup in home office network , able wse 2016 connector software install.

the fact able ping wse 2016 server , when used incorrect userid or password got error message ... these 2 things led me believe dns configuration okay.

i went through lot of iterations trying find , fix problem, think issue 1 or both wse 2016 server and/or windows 10 not registered in dns?  with configurations found ping both wse 2016 , windows 10 workstation (from wse server , windows 10 workstation), nslookup wouldn't give me response.  at least didn't response when trying nslookup windows 10 workstation.

i'm not sure why ping working (although ping workstationname returned ipv6 address rather ipv4) , nslookup not working.  but whatever reason problem seems same thing preventing wse 2016 connector software installing?

thanks suggestion.  that put me on right track of taking closer @ how dns (forward , reverse lookup) functioning within home office network.

p.s.  i'll post more detailed notes in few days had in order working in case else runs similar problem.


windofchange



Windows Server  >  Windows Server 2016 Essentials



Comments

Popular posts from this blog

2008 Windows Deployment Server Properties Error

Can no longer user MS Update - Files required to use Microsoft Update are no longer registered

How do a find data in one file, search for it in another file and if not found, write a custom message to another file