Windows 10 and Server 2003 R1

Question

Our office domain is run on Server 2003 R1. Most of the PCs have no problem logging in to the network and connecting the the file server.

We have two Windows 10 PCs that have trouble connecting to the server on first boot. On either computer, if the end user tries to access any of the shares, the computer freezes. One of the computers, while not able to access the server, is able to access the shares of other computers on the network.

The fix has been to automatically reboot the computer without even logging in. Although this is a workaround, it's a waste of time and effort.

Are there any tricks to get these PCs talking to the server correctly on 1st boot? I've already made sure that SMBv1 is enabled on both PCs.

I'd appreciate any tips you can give.

(P.S. I know it's an ancient server platform, but it's what I have to work with. The domain is not connected to the internet, so chances of intrusion are much less than the typical system.)

Answer 1

I got an error when trying to set the Workstation to Automatic (Delayed Start): Error 87 parameter incorrect.

So I went into the registry to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OneSyncSvc and changed the start value from 2 to 4, then restarted the machine. it didn't work. Went into the powershell and tried changing the start value there but also didn't work. What's the next step for that?

My next question is how do I implement the script in your last paragraph? Do I add this to the logon script on the server? If so, will it affect all of the accounts that use that script, or should I make a special script for just the users of the Windows 10 PCs?

Answer 2

Seems to me that this is compatibility issue between modern Windows 10 clients and the very old Server 2003 SMB stack. Even with SMBv1 enabled, the initial handshake often fails, which is why a reboot clears it. What usually helps is delaying the network redirector until the NIC is fully initialized. Let's try do this: disable “Fast Startup” in Windows 10, ensure the NIC driver is current, and set the service Workstation (LanmanWorkstation) to “Automatic (Delayed Start)” so it doesn’t try to connect before the stack is ready.

If the problem persists, the most reliable workaround is to script a net use \\server\share /persistent:no reconnect after logon, which forces a clean session without needing a reboot.

Answer 3

To address the connectivity issues between your Windows 10 PCs and the Server 2003 R1, consider the following troubleshooting steps:

1. Check TCP/IP NetBIOS Helper Service: Ensure that the TCP/IP NetBIOS Helper service is running as Local Service. If this service is stopped or misconfigured, it can lead to connectivity issues with SMB shares.
2. SMB Signing Policy: Since you mentioned that SMBv1 is enabled, ensure that the SMB signing policy is appropriately set. If you have clients that do not support SMB signing, avoid enabling the policy that requires it, as it can prevent those clients from connecting to the server.
3. Network Configuration: Verify the network configuration settings on the Windows 10 PCs. Make sure they are set to obtain an IP address automatically or, if manually configured, that they are using valid IP addresses within the network range.
4. Update Network Drivers: Ensure that the network drivers on the Windows 10 PCs are up to date. Outdated drivers can sometimes cause connectivity issues.
5. Check Event Viewer: Look at the Event Viewer logs on the Windows 10 PCs for any errors related to network connectivity or SMB. This can provide additional insights into what might be causing the freezes.
6. Disable Fast Startup: Sometimes, Windows 10's Fast Startup feature can cause issues with network connections on boot. Disabling this feature may help with the freezing issue.
7. Test with Local Account: Try logging in with a local account instead of a domain account to see if the issue persists. This can help determine if the problem is related to domain authentication.

If these steps do not resolve the issue, consider checking for any specific configurations or policies applied to the domain that might affect the Windows 10 PCs differently than the others.

---

References:

• Can't access shared folders from File Explorer in Windows 10
• You cannot open file shares or Group Policy snap-ins on a domain controller