I’ve successfully (I think) set up file sharing on the computer in the northwest corner. It uses Samba in the Windows ‘GROK’ domain. I noticed that Eric had previously set up a Samba account, but for the sake of starting new, I removed it and started a new account.
Samba is sharing /home/groksmb under the ‘groksmb’ user name. You shouldn’t need to authenticate from any of the computers, but in case you do, use that user and the password is written on the whiteboard upstairs. Each computer upstairs has been renamed according to cardinal directions (north, southwest, etc). I have set up a persistent share on each of the Windows computers so that /home/groksmb is mapped to S:. This is where we should save project files from now on. I’ve set up a directories in /home/groksmb for ProE and Eagle (as well as Eagle part library). Deepti/Geb/Gregg — I don’t know if you guys want to put all of your code there, but if you do, create a new directory. Should be full RW permissions. I talked to Gregg about setting up the backup — we should just be able to tell the software that he has been using to back up from /home/groksmb. Gregg — is there anything other than these types of files that will need to be backed up?
The Unix computers that use Ubuntu have a samba client and Nautilus samba extensions installed. To get to the network shares, you should just be able to go to Places > Network > Windows Network > GROK > GROK-SERVER….. Printers should work the same way, although I’m not sure Linux will play well with PNP driver propagation (probably will just print PostScript?).
Some notes on that Samba installation on grok-server:
-The Samba daemon binaries are located in /usr/sbin (smbd, nmbd)
-The configuration files are located in /etc/samba
-Not sure why, but there is an additional configuration file in /usr/share/samba — this is unused
-To have samba rehash its config files use SIGHUP (sudo killall -HUP smbd|nmbd)
-To restart the daemon (usually not necessary) manually kill all smbd,nmbd processes without SIGHUP
NOTE: I noticed that the southeast computer upstairs, all the computers downstairs, and the unused ethernet cable coming UP from behind the support column next to the treadmill are all connected to the downstairs router (which is in turned connected to the upstairs router) on 192.168.1.0/24 rather than 192.168.0.0/24 — this means that the upstairs SE computer will not ‘see’ the GROK workgroup and will not be able to fileshare. I’m not sure if there is some way to reconfigure the router downstairs (maybe if that router is on the same subnet and its DHCP assignments are also on the same subnet?) so that it’s computers can see that workgroup, or if a switch needs to be in place of that router, or what….