New Server 2012 R2 Essentials. In connecting computers, I have to use <servername>.<domainname>.local or else the IP address of the server to get the connector started, instead of just <servername>.
Then everything works correctly for connecting Pro versions (to domain). For Home versions the connecting goes fine, but then after reboot the computer looses connection (Connector icon in tray greyed out instead of green, and says "Cannot connect to <servername>." as if the server were powered off. But am able to see the server's shares (and Internet access good, DNS is set static as IP of server).
Both symptoms may have same cause.
Presently testing using a off-the-shelf router that is DHCP server.
Since our customer's network I will be setting up this server to is mixed Win 7/8 Pro/Home, I need the Home systems to keep their connection after reboot! (I think I also should connect the Pro client computers in the Non-domain manner, for consistency).
Thank you
NEW INFORMATION: After seeing the delay in switching DNS server to IP of the Server, I looked at the "hosts" file. Apparently, during originally running the /connect, it adds the line:
192.168.11.9 SVR #Windows Server Added Entry#
And then, 3 or 4 minutes later during the connect install (depending on the computer), it takes that line back out! (Note: that is the IP address and name of the Server)
So I put it back in to the 7 Home Premium PC hosts file, and it connects to the server no problem on boot.
It still has the problem that svr/connect will not resolve on systems without the hosts file addition. Also, even for connected computers, the Server does not show up in "Network."