Need Linux Help - Can't see Windows Workgroup.

Posted by: @spyder

@robo-pi

Ok, wait. What linux computer are we talking about here ?

Is this your pi or the jetson ?

I tried this on the Jetson Nano.  I can give it a shot on the Pi too.  Because I seem to be having the same problems with both.

Let me try your recipe on the Pi.

Ok, when you saw this line...

Posted by: @robo-pi

Password for root@//192.168.1.4/Windows_Share:

Just hit enter. Don't type a password

I just tried it on my jetson, and it works just like I posted

Posted by: @spyder

Ok, when you saw this line...

Posted by: @robo-pi

Password for root@//192.168.1.4/Windows_Share:

Just hit enter. Don't type a password

I just tried it on my jetson, and it works just like I posted

I did that, but it didn't complain about the missing password.  It just said "Host is Down".   Which I know is baloney.

I'm trying to do this on the Raspberry Pi now, but this could take all night.  I think I'm going to go to bed instead and  try this tomorrow.   The Pi is only an early model B+ so it takes a while to do anything. 

@robo-pi

It only took a minute or 2 for me to do on my jetson, and the original post was done on my pi4 running Buster, which also only took a few minutes.

I didn't have a 3b immediately handy to test (meaning, already plugged in and running raspbian)

Posted by: @spyder

I didn't have a 3b immediately handy to test (meaning, already plugged in and running raspbian)

Mine isn't a 3B.  It's just a plain old B+.   I think it's version  1.2. ? 

It doesn't even come remotely close to comparing with something like the Jetson Nano.

I think it only runs at 700 Mhz and is a single-core processor.   It's not quite an original model B as it is a B+.   But it's not a 2B or a 3B.   It's just a plain old B+.    It's an antique Pi ?

Posted by: @robo-pi

It's just a plain old B+.    It's an antique Pi

Oh

Do you have any stone knives or bear skins handy ?

@robo-pi

I should have warned you about the length.  See if you can ping the IP addresses of the Windows boxes.  

Posted by: @spyder

@dronebot-workshop

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

@spyder

I think you may have me confused with someone else on this thread Spyder, I don't have a Raspi NAS. I think it was @codecage who had one.

I do have a NAS, but it's a Hewlett Packard MediaVault and I have no problems accessing it!

?

Bill

@dronebot-workshop

Posted by: @dronebot-workshop

I think you may have me confused with someone else

Oops. Sorry

Sorry I did not follow this whole thread, but just in case :

Micro$oft disabled older versions of the SMB (a.k.a. Server Message Blocks, a.k.a. CIFS, a.k.a.Windows Networking, a.k.a. etc....) on recent versions of Windows, so many older implementations of SMBs (including some NAS with older versions of SAMBA) can't get access to-/be accessed from- recent Windows

I think I remember SMB v3+ is required now for W10 compatibility if W10 registry is not tweaked.

Apparently this is a problem that I can relieve myself of having and shame of ignorance. ? 

From what I've read on the Internet, and see in this thread, I'm not the only one experiencing these difficulties. 

I've read a ton of posts from Google searches where people were voicing similar problems.  They typically took the following format:

Lost Soul: HELP!  I can't access my Windows folders from Linux

Linux Gurus:  No problem.  Try this, that, and the other thing, and also follow the tutorials at this link:...

Lost Soul:  I tried everything you've suggested and nothing worked.

Forum Page: There are no more replies to this thread.  ? 

Just replace "Lost Soul" with "Robo Pi" and you get the idea. ? 

I've been at this for quite some time and I haven't been able to solve it yet.

@robo-pi did you get any numeric error code ?

An error code 5 (sometimes comes out as -5) is "access denied" and relates to access authorizatons on the "server" machine, while a 53 is the usual code for "shared folder or server not found".

If you know the name or the IP of a server+shared folder you can access it as :

\\<<server name or IP>>\<<shared folder name>>

like : \\MYWINSRV\MYFILES or \\192.168.1.123\MYFILES for example

@robo-pi

I haven't given up yet and I'm still with you on this.  Do not give up!

I did a rather lengthy reply to this thread after Eric's reply above about the SMB 3+ issue, but it seems to have gotten way laid somewhere.

I was actually on my Jetson Nano doing the reply as I was trying to get it to connect to my NAS server, but when I clicked on the "ADD REPLY" button everything seemed to lock up!

I walked away from the Nano and when I returned my Nano was just showing the desktop without any apps that had been previously showing (huh?).

Most of my lost comments were about some of the "try this/try that" suggestions above and that we seem to have lost the forest somewhere in the trees on this thread.

I'm going to try to get us back on track and when this get resolved we can hopefully let the forum know what the issue was.

Posted by: @codecage

I'm going to try to get us back on track and when this get resolved we can hopefully let the forum know what the issue was.

Thanks, Steve, I hope you solve it. ?   If you do we'll have to start calling you Sherlock Codecage. ? 

Posted by: @codecage

I walked away from the Nano and when I returned my Nano was just showing the desktop without any apps that had been previously showing (huh?).

That's what the Linux on the Nano does.  If a program freezes up just go do something else for while.  Eventually you'll come back to a nice clean desktop with the frozen program shut down. ? 

It's kind of a nice feature actually.

Since I can access the Linux shares from one of my Windows computers I could put the external hard drive on the Linux  machine  and share it from there.   At least that way all my computers could access the homemade "Cloud Drive".

 I could also share files that way too since all the computer could access the "Cloud Drive".

But now I'm still faced with my SECONDARY problem of why my second  Windows 10 machine can't see the Linux shares.        One can see them, the other one can't.   And I can't figure out what's different between them.

So that's a  SECONDARY problem I'm trying to figure out as well.    Why does one Windows see the Linux shares, and not the other?   I have no clue.   But that's most likely on the Windows side of things.

Looking into the Windows Mystery

As a secondary problem I've noticed that my two Windows machines are behaving differently on my private network.  One machine is able to see, read, and write, files to shares on Linux machines.  The other Windows machine cannot see the Linux shares. 

This is something that has been true for a very long time, and I suspect that it was something I actually did at some point.  But I can't recall how I did it.

I've been looking the two machines over in detail and the only significat difference I can find between them is the name they give to their private networks.

When I go to the Windows"Settings" and choose "Network & Internet" and then finally chose "View your network properties" I get the following different results for the two Windows computers.

Computer One

Name: Wi-Fi
Description: Realtek RTL8188EE 802.11 bgn Wi-Fi
Status: Operational
Maximum transmission unit: 1500
Link speed (Receive/Transmit): 54/72 (Mbps)
DHCP enabled: Yes
DHCP servers: 192.168.1.1
IPv4 address: 192.168.1.4/24
DNS domain name: home
DNS connection suffix: home
DNS search suffix list:
Network name: Robo_SID 2
Network category: PrivateConnectivity (IPv4/IPv6): Connected to Internet / Connected to unknown network

Computer Two

Name: Wi-Fi
Description: Intel(R) Centrino(R) Advanced-N 6205
Status: Operational
Maximum transmission unit: 1500
Link speed (Receive/Transmit): 144/144 (Mbps)
DHCP enabled: Yes
DHCP servers: 192.168.1.1
IPv4 address: 192.168.1.13/24
DNS domain name: home
DNS connection suffix: home
DNS search suffix list:
Network name: Robo_SID
Network category: Private
Connectivity (IPv4/IPv6): Connected to Internet / Connected to unknown network

Other than having a few unimportant details different the major difference appears to be in the Network Name:

One says it is Robo_SID while the other one says it is Robo_SID 2

I'm sure that I had done this a long time ago, but I can't remember how I did it.   Robo_SID 2 is the private network that can see the Linux machines, while Robo_SID cannot.   Robo_SID  is also the name of my Wi-Fi router, but I think that is different from these Private Network names.

In any case, how do I go about finding information on these named private networks?   Where are they defined?  Apparently I created Robo_SID 2 but I can't remember how I did it or where that information exists.

I looked on my router which has an SSID of Robo_SID.         I didn't see anything on the router named Robo_SID 2.     I think I just used the same name when setting up my private networks.

In any case, where do I find the details of a  Private Network?  Surely there must be a way to view their parameters and edit them?  I must  have created Robo_SID 2 at some point, but I can't remember  how I did it.

Apparently Robo_SID 2 has properties that allows that Windows machine to see the Linux shares.   So if I could find where it is defined,  I could see how it is different from Robo_SID.

Sorry if this is all confusing, but this is driving me bananas.

Where are these Private networks defined?