Notifications
Clear all
2020-01-04 4:39 am
When I say server, think of it as a web server. It houses files to be provided to other computers
When I say client, think of it as a web broswer. It broswes files that live on other computers
2020-01-04 4:46 am
Right, I didn't think you meant on windows either, but just making sure.
So you are saying his Linux share is configured to only allow one of the windows machines to access it?
2020-01-04 4:51 am
Now for you
If your NAS is samba powered, you can browse it by logging into it in your linux file manager
Open file mangler
Click on "Go"
Select "SSH"
Type in the ip address or fully qualified network name (I use IP, it's easier and more likely to work)
Type in username and password for the samba server
Your NAS should be listed under the /mnt folder, and all your files and folders should be visible from there
2020-01-04 4:55 am
So you are saying his Linux share is configured to only allow one of the windows machines to access it?
I have no idea how his linux share is configured. This has nothing to do with his linux share. He's trying to access a windows drive from linux, not the other way around (at least, that's the way I read the problem)
Setting up a samba server is a completely different process
A samba server (linux share) lives on a linux box. It serves up files to other computers
2020-01-04 5:01 am
When I say server, think of it as a web server. It houses files to be provided to other computers
When I say client, think of it as a web broswer. It broswes files that live on other computers
Just so you know... I'm well aware of what a client and server is, and I have used samba server before many times without needing to install a separate client - I am aware of a command line tool for configuring clients.
Anyway, we're just speculating now... I suggest he goes back and performs a few basic troubleshooting steps as I outlined earlier... check workgroup is correct, check machines are also talking on the same class A, B or C network, check via UNC path, check firewall and public/private network stupidity in windows, protocol versions, etc...
It's the only way to narrow it down.
Topic starter
2020-01-04 5:04 am
I have installed Samba Client before.
In any case I just followed Dr. Spyder's instructions to a 'T' including installing Samba Client again.
Here's the results:
james@Jetson-Nano:/etc$ sudo mount -t cifs //192.168.1.4/Windows_Share /mnt/winshare
Password for root@//192.168.1.4/Windows_Share:
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
james@Jetson-Nano:/etc$
I know the host is not down. I just scanned it with Advanced IP Scanner to obtain its IP address. So I'm even certain the IP address is correct. And the folder Windows_Share is correctly spelled with the correct case. I also tried some other shared folders and got the same results. Also those folders don't require a Password but it asked for one anyway. I just pressed Enter. But it didn't say incorrect password, it just say the Host is Down.
DroneBot Workshop Robotics Engineer
James
2020-01-04 5:08 am
I suggest he goes back and performs a few basic troubleshooting steps as I outlined earlier
Nothing wrong with testing. I did all that stuff when setting up my own, and it never worked, so I ignored testing, and went straight for implementation
On my own network, which is working right now, my linux box still won't see my windows computers (even tho it's currently connected to the share), so I ignored the test results, and just connected the things
Same for my samba NAS. It doesn't see it on the network, so I just went ahead and connected to it anyway
"Sometimes you gotta run before you can walk"- Tony Stark
Topic starter
2020-01-04 5:10 am
I have no idea how his linux share is configured. This has nothing to do with his linux share. He's trying to access a windows drive from linux, not the other way around (at least, that's the way I read the problem)
That's correct. At least for one of my Windows machines. I still can't see the Linux shares on the second Windows machine and I can't figure out why that is.
In any case, the main problem is that I can't see Windows shares from Linux.
DroneBot Workshop Robotics Engineer
James
2020-01-04 5:15 am
Ok, no worries.
mount error(112): Host is down
I've seen this error before... it is usually to do with wrong SMB protocol version as mentioned earlier.
Topic starter
2020-01-04 5:18 am
Can the Windows machine that can't access the Linux machine actually successfully ping it?
I just had a Ping Party. Every computer successfully pings everybody else. So their all Ping Happy. ?
DroneBot Workshop Robotics Engineer
James
2020-01-04 5:19 am
If you've done the basic tests as I mentioned earlier, then try this:
check network group:
net config workstation
Topic starter
2020-01-04 5:20 am
Did you create the /mnt/winshare folder first ?
Yes Doctor. I followed your instructions to the 'T'. ?
I even copied and pasted from your post. The only thing I changed was the IP address and name of the shared file at the end.
DroneBot Workshop Robotics Engineer
James
2020-01-04 5:26 am
Topic starter
2020-01-04 5:33 am
Have you tried entering:
netstat -a
from the command line of either of the Linux boxes? That will show you everything that the box is aware of. See if the IP address of the windows box shows up instead of the host name.
Mike
That command gives me a very long list of items. Most begin with UNIX and I didn't see any recognizable IP addresses in the whole batch save for the IP address of the Jetson Nano itself.
DroneBot Workshop Robotics Engineer
James