Windows Home Server network share incompatability

Question

Windows Home Server network share incompatability

Eli Calkins 40

On an HP Compaq 6530b, I have an install of Windows Home Server, the original release from 2007. On an HP Compaq 6735s, with Windows XP SP3 installed, I can access the home server and the network share. Back to my main PC, on Windows 11, I can access the home server, but trying to access the network share brings up this error:
[Window Title]

Network Error

[Main Instruction]

Windows cannot access \WinHomeServ

[Content]

Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.

[V] See details [Diagnose] [Cancel]

[Expanded Information]

Error code: 0x80004005

Unspecified error

Why does this happen?

(Yes, I named the home server WinHomeServ)

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Carl-L 21,485 Microsoft External Staff Moderator

Hello Eli Calkins,

Welcome to Microsoft Q&A forum.

May I know if the AI assistant suggestion works for you? I'm quite interested in what it says when you try to connect directly using IP rather than the name.

Since your server is quite old, and Windows 11 might have stricter SMB security than older server can support itself, this could also cause the issue. Additionally, I see that the server using SMB 1.0, which is disabled by default on Windows 11, so please follow the AI instruction to enable it and let me know.

Please let me know the results and whether they help.

I'm waiting for your reply.

Carl-L 21,485 Reputation points Microsoft External Staff Moderator

2026-08-21T10:20:44.95+00:00

Hello Eli Calkins,

Just checking in to make sure that you have received my reply. Please let me know if you have any updates.
Eli Calkins 40 Reputation points

2026-08-21T13:10:44.4666667+00:00

The AI answer worked and I am able to access a network share from a client os nearly 15 years newer than the server.
Carl-L 21,485 Reputation points Microsoft External Staff Moderator

2026-08-22T12:25:30.01+00:00

Hello Eli Calkins,

Thanks for letting me know.

If you have any other questions, feel free to ask.

Answer 2

This usually happens because the Windows 11 PC can reach the server itself, but cannot complete access to the shared folder using the older file-sharing protocol that the 2007 Windows Home Server likely expects.

The strongest match here is legacy SMB compatibility. A similar case after a Windows upgrade showed access failures to an older NAS because the newer Windows system no longer had the SMB 1.0/CIFS client enabled, while the older device still negotiated only SMB1. Windows XP SP3 being able to access the share also fits that pattern, because XP commonly works with older SMB implementations.

Other supported checks from the available guidance are:

Confirm basic network reachability.
- In File Explorer, try accessing the server directly.
- If the machine is reachable but the share is not, the issue is likely share protocol, sharing, credentials, or firewall rather than simple discovery.
Test by name and by IP.
- If access by IP works but access by name does not, that points to name resolution rather than SMB itself.
- Similar guidance for network-access issues notes that if it works via IP but not name, DNS or NetBIOS is the likely problem.
Verify the Windows 11 network is set to Private and sharing is enabled.
- Check Settings > Network & internet > Properties and ensure the network profile is Private.
- Check Settings > Network & internet > Advanced sharing settings and turn on Network discovery and File and printer sharing.
- In Windows Security > Firewall & network protection > Allow an app through firewall, ensure File and Printer Sharing is allowed for Private networks.
If the server is very old, test SMB 1.0/CIFS Client on Windows 11.
- Open Turn Windows features on or off.
- Expand SMB 1.0/CIFS File Sharing Support.
- Enable SMB 1.0/CIFS Client.
- Restart Windows and test the UNC path again.

This is a security-sensitive change because SMB1 is obsolete. Use it only to confirm compatibility with the old Home Server, and disable it again if the server can be updated or replaced.

Why this happens in this case:

The server is visible and reachable, so basic connectivity likely exists.
Windows XP can still open the share, which is consistent with an older SMB stack.
Windows 11 is stricter with legacy file-sharing compatibility, so it may connect to the host but fail when opening the share.

If enabling the SMB 1.0/CIFS Client makes the share open, that confirms the root cause is legacy SMB incompatibility.