You should check out these ideas for fixing when the windows Home server cannot be found on your PC due to a network error.
How to fix Windows crashes
Solutions to problems users may encounter with Windows Home Server and related software
When using network hardware or software, things don’t always go according to plan, and Windows Home Server (WHS) is also an exception. If you’re having trouble installing or using WHS with the Windows Home Server Connector console, be sure to read the advice (and read my review on WHS.Home).
Setting up the Windows Server connector and console
Why is it saying server not found?
No problems found at all” are most often caused by inconsistencies with your DNS. Several affected users have confirmed that they were able to resolve the issue after changing IP protocol version 4 for Google Consum’s DNS server addresses in the Open Connections and Network window.
If all goes well, installing the Windows Home Server installation connector (which is the console) will alsoIt’s not an easy task – find Follow, the command lines cd, and you’re done.
However, if something goes wrong, you may end up tearing your hair out trying to find a source pointing the problem at. It could be your computer, your version of Windows, your spatial network, your home server software, your main home router… When it comes to network troubleshooting, the possibilities are unfortunately endless. So if you’re trying to get a screen like the one below, you need help.
|If you receive this dreaded message suggesting that Windows try installing the Home Server Connector, the problem may be related to NetBIOS over TCP/IP. (Click to see larger image)|
Why can’t I see my server on my network?
In other cases, a Windows PC may not appear in Network Neighborhood due to incorrect workgroup settings. Try adding computers to our workgroup again. Go to System Control Panel -> Security and Systems -> -> Change Settings -> Identitynetwork fixer.
If you find that the Windows Home Server Connector is not installing, a related issue may Be simple: NetBIOS over TCP/IP does not grow in your network or PC. WHS uses over netbios TCP/IP to identify the devices on your new network, and the beasts to communicate with each other. If NetBIOS over TCP/IP isn’t working properly, you’re out of luck.
Here are three windows setting for NetBIOS over TCP/IP: enable it on an item, disable it, or get the settings from someone on your router. Traditional XP windows and Windows Vista are probably configured to use your home router’s NetBIOS settings.
If you are having trouble installing or running WHS, check your NetBIOS settings to allow tcp/ip-over, make sure certain settings are not disabled. This is slightly different from Windows on Vista and therefore Windows on XP.
How do I get a server to show up on my network?
Check if network discovery is enabled.Activate the FDResPub.You service,Make sure DNS client, SSDP discovery, and device host services are enabled in upnp.Enable SMB 1.0.Disable Windows Defender Firewall.Disable third party antivirus software.
In Windows Vista:
1. Select Control Panel –> and –> Internet Network and Network Sharing Center –> Manage Network Connections. A similar screen shows your network connection.
2. Right-click the computer network of your connection and select Properties. The LAN connection properties screen, similar to the one shown below, appears.Here.
3. Highlight Internet Protocol Version 4 (TCP/IP), select Properties, then click the Advanced button.
|Highlight Internet Protocol Version 4 (TCP/IP) on this screen so that it will dig deep enough to understand your NetBIOS TCP/IP settings via. (Click on image to enlarge)|