Page 2 of 2

Re: File uploads/downloads via Ethernet cable

Posted: Sun Mar 19, 2023 4:38 pm
by tblough
You are not going to be able to connect the two computers with either a crossover cable or a switch unless both are on the same network. It looks like your file computer is on 192.168.1.xxx and your CNC10 computer is on 169.254.122.xxx.

You need to set your file computers IPv4 address to something like 169.254.122.10. See the section in TB168 on Setting up a Static IP Address Network under Windows and Linux. Notice the note after step 8 on page 6.

Re: File uploads/downloads via Ethernet cable

Posted: Sun Mar 19, 2023 6:05 pm
by cncsnw
As Tom pointed out, you need to set up the CNC10 computer to use DHCP, so that it gets its IP address from the router, and consequently is on the same network (i.e. it gets automatically assigned an address that begins with 192.168.1).

Also, you do not want to specify "c" as the network drive letter in your cnc10.net file. That letter is not supposed to be the drive letter that the remote computer happens to know its hard drive as. That letter is the one you want the remote computer's shared folder to appear as. Since your control computer already has a "c:" drive (or rather, a /cncroot/c directory) that contains all your local working files, you need to map the shared network folder to some other drive letter. Common choices are "e" and "n".

Also, you do not specify Windows subdirectories as part of the share name in the cnc10.net file. You specify only the computer name (host name) and the "share name". The share name is a single word (not containing any backlashes). In your example, it might be "USERS" or it might be "DOCUMENTS" or it might be something different. When you set up file sharing in Windows, you specify a share name for the folder that you want to share. That name may or may not be the same as the folder's name on the Windows computer. For example, you could share the folder "C:\USERS\ME\DOCUMENTS" as "MYSHAREDFOLDER". Then a remote computer (e.g. the CNC10 system) could map that share, "//DESKTOP-LO9U0GN/MYSHAREDFOLDER", as some network drive (e.g. "n"). Then, when that remote computer looked on its "n:" drive, it would see the files and subdirectories that were in C:\USERS\ME\DOCUMENTS.