This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 76%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
I have a windows 10 client that has been connected to windows server essential 2016 for a few weeks. Recently the client stopped seeing the server. I can not ping, remote desktop ao anything. I have another windows 10 machine and it is working fine. I have tried turning off firewall without benefit. I have the dns of the client pointed to the ip address of the server. I had to enter an alternate ip address in the adapter settings to get internet because the dns is not working for this client.
When I look at the network status it says I am on private network not domain.
I also made sure the Dns client, functional discovery provider host, ssdp discovery and upnp device host are all running.
Any suggestions?
Have you tried to reset TCP / IP Stack?
Run Command Prompt as administrator.
Type the following command:
netsh int ip reset
Unfortunately that did not work. I still can not see the server but I can see the other windows 10 client. The other client can see the server by the way.
I also tried to do a system restore on the client to a moment when the connection was working. It did not help.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Might try reinstalling the connector.
https://learn.microsoft.com/en-us/windows-server-essentials/use/get-connected-in-windows-server-essentials
I ended up fixing it by unplugging it from the netgear orbi satellite and connecting it directly to the switch. Everything worked fine. Now I just have to figure out why orbi is not letting the connection through.
Make sure the domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS
ipconfig /all
(check router DHCP settings)
--please don't forget to Accept as answer if the reply is helpful--
HI
1.can you enter on your issue win10, other win10 client and server essentials ?
ipconfig /all
2.are issue win10 client and other win10 client all connect to the same netgear orbi satellite ,meanwhile netgear orbi satellite and wse2016 connect on the same switch ?
It's good,if you can give a network topology .
3.did you set orbi satellite as router or as Repeater ?
4.if you try to connect your netgear orbi satellite to another switch port,will the same issue persist ?
if the problem persist,we can run tracert the FQDN of wse2016,I suspect it will fail at netgear orbi satellite.if it fail at netgear orbi satellite,did you try to reset netgear orbi satellite and reconfig it.
for example wse2016 FQDN is wse2016.mydc.com
tracert wse2016.mydc.com