from Pi: access files located on PCs in Windows workgroup

[tito-t]

hello,
I integrated my Pi into my windows workgroup acc. to http://raspberrywebserver.com/serveradm ... twork.html

Now I can access /home/pi from my Windows PCs and browse through all directories on my Pi and copy and open files there and back.
I also can access from either Windows PC all HDs on other Windows PCs (Windows drives have been "published", "drive sharing")

But how can I browse through PC directories from my Pi and access all HDs and all files located on the PCs?
(PCs in the homenet are sometimes changing, but not always all are turned on, IP addresses are assigned dynamically by my internet router, just the general mask is
192.168.2.x)

[tito-t]

nothing available? e.g., like the file manager which also scans for network PCs?
(Perhaps like the Windows explorer which is able to scan both for local and network computers and ressources, even if not connected or logged in to?)

[broe23]

Windows uses SMB/CIFS. Linux uses Samba. If using Windows 10, there is a known issue that Microsoft has created to keep guest users from connecting and Netbios is messed up from an update that was pushed out in October. The default smb.conf does not need to be changed. Windows has to have no firewall running, same as Linux. Also you have the make sure that the username to connect to on Raspbian is also converted to a Samba user. Archwiki and the Samba website has everything you need to know, along with the various Ubuntu forums.

[tito-t]

I have mostly Windows 7 pro clients, no firewall active for my home net (trusted network).
I am using Jessie (Noobs) on my Pi, and I am quite new to the Pi and Linux.
So how exactly can I browse with my Pi through my home network (PCs, drives, directories, files)?
I didn't find a solution so far by Google or forum search.

So a tangible link to a detailed guide would be very much appreciated.

[broe23]

I have mostly Windows 7 pro clients, no firewall active for my home net (trusted network).
I am using Jessie (Noobs) on my Pi, and I am quite new to the Pi and Linux.
So how exactly can I browse with my Pi through my home network (PCs, drives, directories, files)?
I didn't find a solution so far by Google or forum search.

So a tangible link to a detailed guide would be very much appreciated.

See my reply that I stated. Everything is available through those resources I pointed out. The solution out on Google is going to hit Arch Wiki if search by the key word "Samba". You just have to make sure that all samba files are installed so that it works properly. Out of the box, Raspbian and all Linux distros only come with a very minimal install of Samba so that the OS can find the Printer.

[tito-t]

See my reply that I stated. Everything is available through those resources I pointed out.. You just have to make sure that all samba files are installed so that it works properly..

I have samba installed, acc to this guide; I already mentioned that: http://raspberrywebserver.com/serveradm ... twork.html

Code: Select all

sudo apt-get install samba samba-common-bin
# /etc/samba/smb.conf:
#workgroup and wins support, and set them up as follows:
workgroup = your_workgroup_name
wins support = yes 

the part "from PC to PI" after that works like a charm , now I need it also "other way round".

But your hints are just vague and uncertain indications or assertions:
I don't see a reasonable tutorial or guide how to provide this functionality, to browse with the Pi through the homenet, find online PCs, log in eventually, and then browse through remote drives, directories, and files, just as it's possible by using the Windows explorer.

[broe23]

Did not ask you to post that code. Everything you need to know is in the post that I mentioned in my last one.

[JimmyN]

I don't see a reasonable tutorial or guide how to provide this functionality, to browse with the Pi through the homenet, find online PCs, log in eventually, and then browse through remote drives, directories, and files, just as it's possible by using the Windows explorer.

You will only be able to access what is shared on the PC. When you create a share on Windows you can mount that share on the RPi, either manually using the mount command or using fstab to mount it at boot. Once the Windows share is mounted on the RPi you can browse, edit, or change files/directories, as if the share were a local directory on the RPi.

To use the RPi's File Manager to access the Windows shares (sort of like using Windows Explorer) start up File Manager and in the top Menu bar click on "Go", then "Network". The first time through it will take a bit and the icon will keep churning, as it has to "discover" what is on the network.

You should see the Windows Network icon show up, click on that. You'll see the Windows Workgroup icon appear, click on that. Now you should see all the PC's in the Workgroup. Click on any PC and you'll see the shares available on that PC and be able to browse them and change things. You will need to enter your Windows username/password when asked in order to access the shares. When you have arrived at a Windows share that you'll want to return to you can save that location in File Manager's Bookmarks, then next time you can use File Manager to jump right to the share with a single click rather than doing all the navigation again.

[tito-t]

edit, Pi config error, fixed (the Pi and 1 Windows PC were unreasonably connected to a windows domain.
Now all are in the Workgroup, and now just static IPs like 192.168.2.x for either one (also for my Pi ).

@broe23 : sorry, I don't understand a word what you mean or what you are talking about.

@jimmyN: thank you, that "Go to ... network ... Windows network ... workgroup ... " worked so far, I can see the workgroup.
(tbh, I had no idea about that go to thing... :-/ )

From either Windows PC I can see all computers (PC28, PC30, PC55, myPi).
(all PCxx are Windows PCs, PC28+30: Windows7, PC55: WinXP; myPi (you might guess it:) is my Pi )
All Firewalls down (checked it!)


On the Pi I can see in the Workgroup NO PC at all , just myPi

good news: I can ping all PCs .
But I can't access either one.

but all volumes on eitherPCs are completely released (?) decontrolled (?) (correct idiom? German: für andere Benutzer freigegeben) , no firewall active.

so something is totally messed up.

[broe23]

edit, Pi config error, fixed (the Pi and 1 Windows PC were unreasonably connected to a windows domain.
Now all are in the Workgroup, and now just static IPs like 192.168.2.x for either one (also for my Pi ).

@broe23 : sorry, I don't understand a word what you mean or what you are talking about.

I cannot state it any simpler. All of the information that you need to know about SAMBA is the Man pages on Raspbian, Arch Wiki has info on Samba, Ubuntu Wiki has info on Samba, the list goes on. If you are using an instal with Pixel, install Synaptic package manager and then open it and do a search for "Samba". We are talking about something that you are going to have to learn and a lot of it is doing on your own. If you get stuck, then hit up a forum that deals with Samba or ask here. Your smb.conf does not need to be changed when you get everything installed for Samba. It is because when you install any Linux Distro, it is a minimum install of Samba to allow the OS to find network printers.

[tito-t]

sorry, broe23, your post makes no sense at all, I need a reasonable solution to my problem.
I don't use Pixel, I have the GUI from 1 edition before that.
I also already explained how I installed Samba files additionally, I can access the Pi from either and all Windows PCs, but not other way round.

Thankfully to JimmyN's post I meanwhile I can identify the network ("WORKGROUP") by the Pi, but I still can't see any joined PCs yet in there .

So what is missing, and what is the solution?

[tito-t]

navigating to windows Network -> Workgroup
it shows the file path
smb://WORKGROUP/

strangely, after 30 minutes since all computers have been started, I eventually got a list in there (previously before that the list was completely empty):
PC55, PC28, myPi
but when I try to open one of the PCs then I get the error msg window:

Empfangen der Freigabenliste vom Server ist gescheitert: Das Argument ist ungültig
(Google translate: receiving the release list (checkout list?) from the server failed: The argument is invalid)

But what "Server" ? what a release list? what an argument? And there is no dedicated Server!

and after that a 2nd error msg window:

Der angegebene Ort ist nicht eingehängt
(Google translate: The specified location is not attached (hooked in? do they mean perhaps: mounted? ))

what has to be attached or hooked or perhaps: mounted?

[hortimech]

OK, you are trying to access files on windows machines from your rpi (and vica-verca). You could setup windows to allow guest logon, but that isn't really recommended, especially if the windows machine is joined to a domain.

What you are trying to do is run a standalone server on your rpi, so I suggest you read this:

https://wiki.samba.org/index.php/Settin ... one_Server

The main thing to understand is, in a workgroup,, you have to create the username everywhere with the same password.

[tito-t]

well, again, to the 4th time:
Of course I have user rights and they are working fine in my homenet.
I can access any PC from either PC, and I also can access my Pi from either PC.

When trying to access a remote PC I am asked for a user name and a password, that's normal for a windows workgroup.
When I log in to the Pi from either PC I am also asked for a user name and a password, that's also supposed to be normal (according to the turorial I linked to above it's :
user pi, pwd pi )

everything's working like a charm from This side

Just from my Pi I can not acess a PC, I am not even asked to enter a user name and a password, nothing works, just error messages.

I actually don't want to set up a "server", neither a Windows domain server nor a samba network server, a Pi is just a client among all others (and perhaps additionally for another 2 Pis).
It's a peer-to-peer-network, that is the way it should remain,
with clients joining it randomly (or not), both Windows PCs and Pis,
and finally it always works fine for Windows PCs, so why not for the Pi?

So what's wrong,
what is missing,
how to fix it?

[mattmiller]

I'm able to browse my Win10 machine from my Pi but I can't remember what I did to my win10 machine to allow this (must have done something if its not working for you)v:(

So I can go int File Manager - Go - network and I can select my Win10 computer - I'm asked for a user name (I did create a pi user on my Win10 to make life easy) and then I can see all my shares

So it is perfectly possible and since I've not done anything clever on the Pi side - it must be a Windows thing - something in the back of head says to turn off encryption but I can't remember the details (and that might be wrong)

I've had this setup for so long i just can't remember what I must have done

[tito-t]

hmmm... that makes me really curious what's messed up here.
But you must have installed samba probably, additionally, on your Pi (like I did), didn't you?
perhaps packages I don't know?
I'm also curious about your encryption thing (if this actually is that what you assumed it was... ) I have no idea where Win7 PCs preferences are switched acc. to such a setting...

[mattmiller]

This is my conf - its just installed from http://simplesi.net/auto-install-a-simple-samba-setup/

#======================= Global Settings =======================
[global]
workgroup = WORKGROUP
wide links = yes
unix extensions = no
dns proxy = no
#### Debugging/Accounting ####
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
security = user
map to guest = Bad User
guest account = pi
#======================= Share Definitions =======================
[root]
comment = Admin Config Share
path = /
browseable = yes
force user = root
force group = root
admin users = pi
writeable = yes
read only = no
guest ok = yes
create mask = 0777
directory mask = 0777
#-------------------------------------------------------------------
[pi]
comment = pi user /homepi folder
path = /home/pi
browseable = yes
force user = pi
force group = pi
admin users = pi
writeable = yes
read only = no
guest ok = yes
create mask = 0777
directory mask = 0777

I had a look at my network settings and I don't think its anything to do with encryption - like I say -I've had this machine a few years so I can't remember if/what I had to do to get it to be visible

I do nothing on the Pi end except install samba as above - pretty certain its something at windows end needed for Linux clients to browse shares - I'd google that sort of thing and see if it gets you anywhere

[tito-t]

thank you, I executed that script, now my smb.conf looks like yours.

from my Windows PCs I again can access my Pi like a charm.

but on my Pi,
opening -> WORKGROUP
shown path:
smb://WORKGROUP/
I again see 3 computers (PC28, PC30, myPi)

trying to open PC28, it says sth like access denied, no release list, argument invalid, whatever...
opening PC30, I see surpisingly 2 of the Pi (!!!) folders, ie. /pi and /root
(hell, how I hate that s**t ! )

[hortimech]

@mattmiller, you do realise the smb.conf you are using is like hanging a big sign 'Come on in, everything is open, you can access ALL areas' on your computer. Anybody can connect to your computer and read anything!

@tito-t, have you read the Samba wiki page I pointed you at, please don't read any other pages you might find on the internet, most are just wrong, mainly because they use old ways of doing things. Samba is a fast moving project and things change in smb.conf, what might have worked with 3.6.x, may not work with 4.3.x (Note: you shouldn't be using any version before 4.3.0, they are all EOL)

[tito-t]

I don't understand the wiki page, it's english, too many words, nothing specific what I have to do, and additionally I don't want to install a Samba Standalone Server, my Pis are just clients,
so in 1 word, short version:
useless

strangely enough that
clicking on PC28, it says sth like access denied, no release list,
and opening PC30, I see surpisingly 2 of the Pi (!!!) folders, ie. /pi and /root

as I already said:
I need a short and reasonable step-by-step guide, or even better: a install program or script which does everything automatically what's needed.

[hortimech]

You i***t, if you want to do what you say you want to do, then yes, you do want to set up a standalone server. What do you think a windows machine that is not a member of a domain is ???

Rowland
rpenny at samba.org

[mattmiller]

you do realise the smb.conf you are using is like hanging a big sign 'Come on in, everything is open, you can access ALL areas' on your computer.

Yep
None of my Pi are exposed to T'internet just LAN

I do all my stuff using VNC and SMB - I edit files using Windows tools and just run them on my Pi

[tito-t]

the same for me, it's just for my personal purposes, and I have nothing to hide from myself on my Pi or on my PCs.
But how networking works - no idea, neither in Windows workgroups nor in domains nor with or without Pis. It simply just should work.

[hortimech]

@tito-t, Please don't threaten to sue me for insult, you won't get very far because, in my opinion you are acting idiotic.

You can describe a normal windows machine that is not part of of a domain as a 'standalone server', so if you want your Unix machine to act just like a windows machine does (when it isn't a member of a domain), it needs to be set up as a 'standalone server'.

People, including myself, have given you advice, which you have dismissed out of hand, probably because it sounds like you want somebody to come to your house and set it up for you.

Can I suggest you research a bit more on the internet and learn how to do what you want to do.

[mattmiller]

Well I seem to have upset the gremlins - I can longer browse the network from any of my Pi and my Win10 machine is not showing any other machines on the network either