How-to
Networking a DOS CNC control to Windows 10 safely
Short answer
Connect the DOS control to a dedicated Windows 10 Ethernet adapter, leave that adapter on its public (unidentified) profile, serve one shared folder over SMB1 on a static 192.168.10.0/24 link with no gateway, and allow inbound SMB only from that subnet. The shop side keeps its private profile and firewall, the control maps the share as F:, and the whole link stays off the internet.
On this page
Network a DOS-era CNC control to Windows 10 by giving it its own Ethernet adapter on the host, leaving that adapter on the public profile Windows gives an unidentified network, and serving one shared folder over SMB1 on a static /24 with no gateway. The shop side stays on the private profile with its firewall on, and the CNC adapter accepts inbound SMB only from the CNC subnet. The result is a two-device segment the internet cannot reach and the shop network cannot route into, with the control mapping the shared folder as F: exactly as it did from the old intermediate PC. Everything here was verified on Windows 10 version 1803 with Microsoft Network Client v3.0 for MS-DOS 6.22; retest after Windows feature updates, because SMB1 handling changes between releases.
What keeps a DOS link on Windows 10 safe #
The constraint is the protocol. The DOS client negotiates only SMB1 dialects — SMB2 arrived with Windows Vista, and no older client speaks it — so the Windows host must have the optional SMBv1 feature installed to serve the share. SMB1 also carries wormable exploits, so one safety rule governs the whole build: the CNC segment stays two devices on a point-to-point cable with no gateway, no bridge and no internet connection sharing, and the SMBv1 feature comes off the day the machine is retired.
Isolation on the Windows side comes free. Windows labels the CNC link an unidentified network and, on version 1803, offers no way to reclassify it, so it sits on the public profile, where inbound file sharing is blocked by default. The shop connection stays private with its firewall on. Two independent networks meeting in one host is the layered control pattern described in why layered OT security controls protect a network path: the host is the only path between them, and its only crossing is the shared folder.
Addressing plan for the isolated segment #
Worked example: 192.168.10.0/24. The mask 255.255.255.0 leaves 8 host bits, so the segment spans 192.168.10.0 through 192.168.10.255; subtract the network address (.0) and the broadcast address (.255) and 254 usable host addresses remain — far more than the two this segment will ever carry. Assign 192.168.10.1 to the Windows adapter and 192.168.10.2 to the control, both static. Static is not optional: a two-device crossover link has no DHCP server, and an adapter left on DHCP falls back to an unpredictable 169.254.x.x address the DOS client cannot find. Leave gateway and DNS empty on both ends — an empty gateway is what keeps the segment unrouted.
Check the plan against the shop network. If the shop runs 192.168.1.0/24, the differing third octet (1 versus 10) shows the subnets do not overlap. If the shop already uses 192.168.10.x, pick another unused /24 such as 192.168.77.0/24 and shift both addresses into it.
Keep the crossover cable for a 10/100-only control NIC. If both ends are gigabit, they cross over automatically and a straight patch cable works.
Configure the Windows 10 host #
- Install the optional SMBv1 feature on the host and restart. Windows 10 ships with it disabled; Microsoft's guide to detecting, enabling and disabling SMBv1 documents the steps for each Windows release.
- Create C:\share on the host and share it. Create a dedicated local user for the control and give that user read and write on the share. The reported setup granted Everybody read and write; fall back to that only if the DOS client will not authenticate to a named account, and accept it only because the segment carries exactly two devices.
- On the adapter cabled to the control, set 192.168.10.1 with mask 255.255.255.0, no gateway, no DNS. The reported setup ran first on a USB-to-Ethernet adapter and later on the built-in port, unchanged.
- Connect the shop side on the host's second interface and confirm Windows classifies it private with the firewall on.
- Confirm the CNC adapter's network shows as an unidentified network on the public profile, and leave it there.
- Add one inbound firewall rule on the CNC adapter: allow SMB over TCP port 445, applied to the public profile, scoped to source addresses 192.168.10.0/24. The firewall stays on for both profiles.
- Reported fallback on 1803: if the scoped rule and the DOS client will not complete negotiation, disable the firewall for the public profile only, then verify the private profile still shows its firewall on before running parts.
- Confirm no route exists: open the CNC adapter's properties and check that bridging and internet connection sharing are not enabled on it.
Configure the DOS network client #
- In the Microsoft Network Client setup on the control, replace the old NetBEUI arrangement with TCP/IP.
- Set the control's address to 192.168.10.2 with mask 255.255.255.0, no gateway, no DNS, matching the host's plan.
- Map the share to F: with the client's net command, by host name or by IP address. If name lookup fails, add the host's name to the client's LMHOSTS and HOSTS files and map again.
- Keep the control's login password to 14 characters or fewer: LAN Manager-era authentication reads only the first 14.
- At startup, answer the reconnect prompt only after waiting at least 5 seconds; answering immediately was associated with failed connects. If F: is not mapped, reboot and answer again with the same delay — the reported link often connects on the second start.
- Verify from the control: open Menu > Drive > F: and confirm the contents of C:\share list.
Verify the link and live with the timeout #
Post a test NC file from the CAM station to the share over the shop side, confirm it lands in C:\share on the host, then open the drive listing at the control and run it with the Run command, which loads the whole program into control RAM. The DOS session idles out after inactivity; re-selecting the drive at the control wakes it immediately. Execution is immune because the program sits in RAM, but DNC streaming through a timeout was never tested in the reported setup.
After every Windows update or adapter change, recheck three things: the CNC adapter is still the unidentified public profile, the scoped rule (or the profile-disable fallback) is still the only firewall exception, and F: lists a freshly posted test file. The verified baseline is Windows 10 version 1803 — SMB1 presence and firewall defaults move between feature updates, so retest rather than assume.
Host hardware and retirement options #
This build exists to retire an aging intermediate PC — the old Windows box that used to sit between CAM and the control. If the machine behind your rebuild is an aging Windows controller you would rather not keep at all, the P2V migration plan for an aging Windows machine controller covers that decision. A second reported path skips Windows entirely: the same DOS client read a Linux Samba share from an Ubuntu server and from a Raspberry Pi, with Samba serving the old dialects. And if the host should live at the machine instead of on a shop bench, the same two-NIC configuration runs on a fanless industrial mini PC in the cabinet.
Questions asked
Why does the DOS startup report a failed connection when F: works?
The DOS startup on the reported control can print a reconnect failure even when the mapping actually completed. Open the drive menu, select F:, and check that the folder contents list. If the listing appears, the link is up and the startup message is noise. If it does not, reboot the control, answer the reconnect prompt only after waiting five seconds, and try again; the second start frequently connects.
How do I clear stale credentials on the DOS client?
After a host name or password change on the Windows side, the DOS client can keep authenticating with saved credentials and fail with a network error (error 86 in one report, on a Windows 7 host). Delete the saved password files (.pwl) in the client's NET directory, recreate the login on the control, and map the share again. Adding the host to the client's LMHOSTS and HOSTS files clears name-resolution failures.
Can I stream a program through this link while cutting?
DNC streaming through the DOS link was never tested in the reported setup, and the idle timeout was never measured. The Run command loads the whole program into control RAM before cutting starts, so a timeout cannot interrupt a running part. Treat continuous streaming as unproven: time the actual timeout on your machine and stream only if a trial part cuts clean through it.
What can replace the Windows laptop as the transfer host?
Two reported alternatives exist. A small Linux host running Samba, configured to serve the old SMB dialects, has been used with this DOS client from an Ubuntu server and a Raspberry Pi. Otherwise, the same Windows configuration runs unchanged on any small always-on PC with two network interfaces, as long as its Windows release still offers the optional SMBv1 feature.