Cannot Connect Computer Windows Essentials 2012

Hello Experts,

I am not able to connect a client to Windows Server Essentials 2012.  While I am able to browse to http://mydomain/connect with the client when I run the join app it fails with, "The server is unavailable. Try to connect....etc".

I have two nics on the server, one for the internet (WAN) and the other for the LAN.  The WAN nic is just fine and I have access to the internet from the server; however, the LAN nic can't seem to hold the the server's own ip address though it is able to hold the server's ip address as the DNS since that's running.  When I run ipconfig/all I do see that the LAN nic is referencing the server's ip address correctly; though when I look at this nic directly the ip address for the server is missing.

I've run BPA I get the "DNS client not configured" and I've tried various suggestions to fix this but none seem to work.  I've also changed the nic for the LAN to ensure it's not a hardware issue.

Finally both the server and the client display limited connection on the LAN nic.  I don't know what it is I am doing wrong but at this point I've exhausted what I could come up with, any assistance would be greatly appreciated.
configall.txt
ShadowITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Neil RussellTechnical Development LeadCommented:
IN th e ipconfig /all you have attached the LAN has an automatically assigned microsoft IP address and NOT a statically assigned IP. The two nics need an IP address on DIFFERENT subnets, your WAN is on 192.168.111.10 via DHCP so I sugguest you use 192.168.1.x for your LAN.
Fix that  and try again.
0
ShadowITAuthor Commented:
Thank you for your suggestion; unfortunately it didn't solve the issue.  I also tried one with different subnets...neither worked.
newipcofigall.txt
again-ipconfigall.txt
0
Neil RussellTechnical Development LeadCommented:
your WAN still shows a DNS on a 169 address, it should not be.
When on a client now what happens if you ping mydomain
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Cliff GaliherCommented:
What you described is known as "multi-homed" due to multiple NICs being haned to multiple networks. Essentials (as a SKU and as a role) do not work with multi-homed severs, or multi -NIC servers in general actually. You can't do what you want with your current topology.
0
ShadowITAuthor Commented:
Neilsr: Good catch, I fixed the DNS on the WAN side (see attached).  Unfortunately it is still not working properly.  Thank you

Cliff Galiher: This is new information to me; I suppose that since SBS supported this, as it's replacement, I assumed Essentials did as well.  OK, if this topology isn't supported what is?  Do I just have a single nic on the server, which I assume I would configure to connect to the internet, I then also configure the client this same way and just join it this way?  So what are the implication of this, Windows Essentials is basically just a file server?
ipconfigallfixed.txt
0
ShadowITAuthor Commented:
Cliff Galiher:  You mean like this, correct?
WindowsEssentialsTypicalTopology.png
0
Cliff GaliherCommented:
SBS hasn't supported multiple NICs in a long time either. Then last version that did was 2003, and even them, it was only supposed to be done with the premium edition that shipped with ISA as a routing and firewall platform. Since 2008, SBS and essentials were designed to be deployed with a single NIC and a private IP address. Any internet access for the server and clients is provided by a separate NAT capable router. Configuring SBS or Essentials with a public address or multiple NICs is not supported.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ShadowITAuthor Commented:
Yes, I was referring to SBS 2003....so you didn't say specifically if I had this right now, I'm guessing yes?
0
Neil RussellTechnical Development LeadCommented:
OK what exactly do you have? 2012 essentials or SBS 2003?  You question was for 2012 but now you say 2003SBS
0
ShadowITAuthor Commented:
I had SBS 2003 but now I am moving to Windows Essential 2012.  As I explained, because I had SBS I have this expectation, what I guess is now incorrect for  Windows Essential 2012 which explains why it is not working.
0
Cliff GaliherCommented:
A few clip-art images with no labels or IP spaces declared is not much to go on. You may have it right. Or you may have it very very wrong. I can't answer that with the limited information provided.
0
ShadowITAuthor Commented:
I've always pondered the peculiar personality that professes aid but can't but deliver it with that light sprinkle of snarkiness.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.