Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

Page 1 of 2 12 LastLast
Results 1 to 12 of 19

Thread: Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

  1. #1
    Registered single phase's Avatar
    Join Date
    Feb 2006
    Location
    Pennsylvania
    Posts
    359
    Downloads
    0
    Uploads
    0

    Lightbulb Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

    You can securely network DOS and Windows 10 together if you do it this way . . . for now.

    The idea is to bring two networks together in a windows 10 PC (I will refer to this PC as the laptop), one network goes to the mill (public, no firewall) and the other goes to the CAD/CAM computer (private, with firewall). Both networks see the “C:\share” directory that has permissions for everybody to read and write. My CAD/CAM windows 10 computer is networked with the laptop. So with this setup, when I post g-code, it is instantly available on the mill.

    The single board computer upgrade from Milltronics (SBC) with networking, runs Microsoft Network Client v3.0 for MS-DOS 6.22. In the past we used the simple DOS NetBIOS NetBEUI protocol with the old windows like Windows 2000. However, modern computers running Windows 10 use the TCP/IP protocol. They can still use NetBEUI but only over TCP/IP.

    Before the changes brought about by windows 10, my configuration was an Ethernet crossover cable connecting my circa 1998 MV-15 Centurion 6 loaded with a network card to an old Pentium PC running Windows 2000. This Windows 2000 computer has been connected to my mill for years, both before and after I got my SBC in 2015. The windows 2000 computer had two NICs. I have always run my CAD CAM in the most modern Windows possible and output g-code files directly to the Windows 2000’s shared HDD over my Ethernet network. Then I would then go to the mill and run the g-code file directly off that same drive as it was the mapped as F: drive on the mill. It had been working great but connecting Windows 2000 to Windows 10 is getting as difficult as just connecting DOS to windows 10. Microsoft has had to make Windows 10 a fortress against the nasty stuff out there on the net. The last straw for me was when Windows 10 could no longer login directly to my Windows 2000. So I needed to have this same functionality but to do away with the windows 2000 computer.

    I have talked to SportyBob, Moldcore and several others many times over the years in posts here on the zone. They have helped in getting me to this solution. If you ask them or Milltronics for help on this subject you tend to get the answer “it can be done but it is fiddley, unsecure and unstable (given Microsoft’s propensity to change things)”. They are right but it is working and it is secure. I do want to say that I am not a networking expert or pro.

    SportyBob had been experimenting with a NAS solution with some success but he has told me that the latest NAS he tried did not connect to DOS. I hear that he has a USB solution now that is quite nice so some of you may want to look into that.

    I have an old laptop that is running Windows 10. I decided to see if I could get it to connect directly to DOS. At first it was looking hopeless because the error codes do not tell you much. I just kept changing settings and eventually it connected. It tells me it did not connect, but it actually did.

    The laptop configuration is a j7 create USB to Ethernet adapter plugged into the windows 10 laptop. Then a crossover Ethernet cable connects it directly to my NIC on my MILL’s SBC. That is it, no switch and no router, though they probably would work in place of the crossover cable. I realize that the USB NIC is not probably needed as the laptop has a built in NIC. I wanted this configuration to stay with the USB adapter.

    This configuration is two completely independent networks that both come together in this windows 10 laptop where both networks can access the same shared folder on the C: drive. The Wi-Fi on the laptop is connecting to the shop network of the Windows 10 machines and it is set as a private network!!! This makes it usable and still secure. The USB NIC connects to the mill as an unidentified network, and so automatically defines it as a public network, you can’t even change it to private. But that is kind of the magic. Windows will let you turn off the firewall on the public network and leave the firewall enabled on the private Wi-Fi network. Amazing, that it works out that way because you need the firewall to the internet but you can’t have it going to the mill.

    When networking windows 10 to DOS you have to drop the firewall. But it is not a security threat when things are connected this way. I am surprised that this actually works because there is so little information out there on what Windows 10 is going to do with two separate networks connected to it at the same time. If any of you find more detailed information on this aspect of Windows please share it here.

    If anybody wants the rest of the network configuration settings I will post them here. All of this is based on windows 10 version 1803 which is after the removal of homegroups.

    Cheers
    SF

    Similar Threads:
    Last edited by single phase; 07-23-2018 at 09:15 PM.


  2. #2
    Registered single phase's Avatar
    Join Date
    Feb 2006
    Location
    Pennsylvania
    Posts
    359
    Downloads
    0
    Uploads
    0

    Default Re: Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

    Screen captures of the status dialog boxes

    Attached Thumbnails Attached Thumbnails Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC-network-sharing-center-jpg   Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC-network-interenet-status-jpg  


  3. #3
    Registered single phase's Avatar
    Join Date
    Feb 2006
    Location
    Pennsylvania
    Posts
    359
    Downloads
    0
    Uploads
    0

    Default Re: Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

    Share a folder with permissions to everyone. My folder is on the root and it is named share.


    Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC-share-folder-jpg



  4. #4
    Registered single phase's Avatar
    Join Date
    Feb 2006
    Location
    Pennsylvania
    Posts
    359
    Downloads
    0
    Uploads
    0

    Default Re: Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

    set the options for the adapter that is connecting to DOS


    Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC-change-adapter-options4-jpg


    Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC-change-adapter-options5-jpg


    Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC-change-adapter-options6-jpg



    on the mill DOS networking use IP address 192.168.10.2



  5. #5
    Registered single phase's Avatar
    Join Date
    Feb 2006
    Location
    Pennsylvania
    Posts
    359
    Downloads
    0
    Uploads
    0

    Default Re: Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

    set the sharing options for both the public and private networks


    Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC-sharing-options1-jpg


    Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC-sharing-options2-jpg


    Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC-sharing-options3-jpg



  6. #6
    Registered single phase's Avatar
    Join Date
    Feb 2006
    Location
    Pennsylvania
    Posts
    359
    Downloads
    0
    Uploads
    0

    Default Re: Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

    firewall settings for public and private networks

    Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC-windows-firewall-jpg



  7. #7
    Registered single phase's Avatar
    Join Date
    Feb 2006
    Location
    Pennsylvania
    Posts
    359
    Downloads
    0
    Uploads
    0

    Default Re: Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

    conclusions and lingering issues

    I would say this is stable enough for a home shop. The network does eventually timeout at the mill but you only have to select the menu/drive again and it wakes just fine. I only use the run command that loads the entire program instantly into the controls RAM so the timeout has no effect on execution of the g-code. I do not know if it will timeout in DNC. Maybe somebody will have a fix for this timeout. The other problem is the error in running the autoexec bat file where you have to answer yes to two questions. See attachment.

    Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC-screenshot_20180723-181202_video-player-jpg





    I suspect that it just needs more time and if I were to put in a couple wait commands in the autoexec file it would get through it. I do not remember the wait command for DOS. I think I answered the two yes questions too quickly a few times and it never did connect to the laptop drive. I just reboot the mill and it almost always works the second time.

    The laptop complains about the firewall being off once after you boot into windows.

    If somebody else tries this, please post your results here too.

    Last edited by single phase; 07-23-2018 at 09:59 PM.


  8. #8
    Registered single phase's Avatar
    Join Date
    Feb 2006
    Location
    Pennsylvania
    Posts
    359
    Downloads
    0
    Uploads
    0

    Default Re: Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

    someone needs to post all the DOS network setup wizard screens to add to his thread

    but I remember that you have to take out the netbeui and put in the tcpip protocol and call out the name of the shared directory and give it a drive letter like F:



  9. #9
    Registered
    Join Date
    Dec 2017
    Location
    United States
    Posts
    54
    Downloads
    0
    Uploads
    0

    Default Re: Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

    as a nerd with a bunch of machines running many different operating systems, I will add that my sbc cent 5 can see and access without issue a Linux samba share hosted on an Ubuntu server, and on a raspberry pi. I didnt bother trying to get any of the modern windows machines to communicate with it, I just use the Raspberry Pi that controls my 3d printer as a NAS device. This works easily with my setup because I dont store anything on my workstations, it is all saved on one server that then distributes copies to a few others onsite and off so Im already accustomed to saving things to a network location (Read that as ridiculously paranoid of loosing data)



  10. #10
    Registered
    Join Date
    Jul 2006
    Location
    USA
    Posts
    118
    Downloads
    0
    Uploads
    0

    Default

    Quote Originally Posted by ImTippmann View Post
    as a nerd with a bunch of machines running many different operating systems, I will add that my sbc cent 5 can see and access without issue a Linux samba share hosted on an Ubuntu server
    I had a similar thing about using a Pi. Hardwire Ethernet to the milltronics and use wifi to talk to the Windows machine.

    Small script monitors a directory for changes and pushes updates to the control.



  11. #11
    Registered
    Join Date
    Jan 2014
    Posts
    16
    Downloads
    0
    Uploads
    0

    Default Re: Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

    Quote Originally Posted by single phase View Post
    someone needs to post all the DOS network setup wizard screens to add to his thread

    but I remember that you have to take out the netbeui and put in the tcpip protocol and call out the name of the shared directory and give it a drive letter like F:
    That would be: NET USE <DRIVE LETTER> <NETWORK SHARE> /user <LOGIN NAME ON SHARE COMPUTER>



  12. #12
    Registered
    Join Date
    Jan 2014
    Posts
    16
    Downloads
    0
    Uploads
    0

    Default Re: Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

    I am setting this up right now. It worked for 12 years on Netbeui and another 3 or so years with TCP/IP connected to a win 10 system, then one day in April it quit.



Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


About CNCzone.com

    We are the largest and most active discussion forum for manufacturing industry. The site is 100% free to join and use, so join today!

Follow us on


Our Brands

Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC

Networking Windows 10 to DOS 6.22 on the Milltronics Centurion 6 SBC