MS DOS Based CNC machines cannot see WinXP shares
Posted: 5. Sep 2018, 19:49
I have configured two windows 10 Host machines with Virtualbox and installed Windows XP Pro running some Cad software used by CNC miling machines. Two of these CNC machines are windows 7 based but two are MS-Dos and can only communicate with the network using NetBui (Hence Windows XP). I know this setup works because I previously configured another Windows 10 PC and this is working with all 4 CNC machines. The latest host machines are the the April update 1803 build and I am sure this has something to do with the problem. Initially I couldnt browse the workgroup and see anything other than the host machine which seemed really strange. I checked all the normal things such as:-
1) Making sure all host and guest machines on the same workgroup
2) Enabled file and print sharing in Windows 10
3) Disabled Password sharing on local machines.
I finally made some progress after lots of internet searches by re-installing SMBv1 on the Windows 10 Host which is automatically disabled in the Creators update, and enabling the Function Discovery Resource Publication and Function Discovery Provider Host services in Windows 10. As a result both Windows 7 based CNC machines can now see the Windows XP host shares and access the contents, however neither of the MS-DOS based machines can see the shares. I just get Error 53: The computer name specified in the network path could not be located" when trying to map a network drive to the shares.
As I said this works perfectly in an earlier build of Windows 10 so must be something that's been blocked/broken by a Windows 10 Update.
For background I have tried
1) Checking the relevant ports are open on Windows 10 Firewall for Netbios (same as file and print sharing I am informed???)
2) Disabling Windows 10 Firewall altogether
3) There is only Avast Free antivirus on the host machine so no third party firewall
4) There is no AV at all on Win XP Host machines.
5) I have set Full Control to Everyone in the permissions on the XP Guest shares just in case it was a permissions issue.
I am totally stumped with this one so any advice would be very much appreciated
Fozzie
1) Making sure all host and guest machines on the same workgroup
2) Enabled file and print sharing in Windows 10
3) Disabled Password sharing on local machines.
I finally made some progress after lots of internet searches by re-installing SMBv1 on the Windows 10 Host which is automatically disabled in the Creators update, and enabling the Function Discovery Resource Publication and Function Discovery Provider Host services in Windows 10. As a result both Windows 7 based CNC machines can now see the Windows XP host shares and access the contents, however neither of the MS-DOS based machines can see the shares. I just get Error 53: The computer name specified in the network path could not be located" when trying to map a network drive to the shares.
As I said this works perfectly in an earlier build of Windows 10 so must be something that's been blocked/broken by a Windows 10 Update.
For background I have tried
1) Checking the relevant ports are open on Windows 10 Firewall for Netbios (same as file and print sharing I am informed???)
2) Disabling Windows 10 Firewall altogether
3) There is only Avast Free antivirus on the host machine so no third party firewall
4) There is no AV at all on Win XP Host machines.
5) I have set Full Control to Everyone in the permissions on the XP Guest shares just in case it was a permissions issue.
I am totally stumped with this one so any advice would be very much appreciated
Fozzie
. Certainly the info that Windows 10 as a host is breaking things may be of interest to those using the OS with Virtualbox.