Evening all,
Slowly but surely my Linux knowledge is growing but I have always avoided the big "N" as the alien terminology tends to make my head spin after about 5 mins of reading! But I'm going to give it a go. A full tutorial through the LUG is not what I'm after, but a few pointers of where to start would be appreciated.
There's a desktop in the lounge (which will be the server) connected by cable to a Linksys wireless broadband router for ADSL internet access. My laptop connects to the internet wirelessly (ndiswrapper) through the router. Both machines connect to the router via DHCP and there are firewalls enabled on the desktop, the laptop and internally on the router. In the next couple of months I will be putting another desktop in my son's bedroom upstairs. All three machines will be running SUSE 10.0
All I really want is one shared folder on the server for moving files around all machines and for the laptop and upstairs desktop to be able to print to the printer connected to the desktop server.
I don't know what route to go. I've read a little about internet printing protocol and configuring cups but that only covers the printing. Samba seems to address both but my first initial attempts have failed. I set up the workgroup COLLINS-NET through the SAMBA SERVER module in YAST which also opens up a firewall port on the server. I then configure the SAMBA CLIENT through YAST on the laptop and after entering the username and password it seems to connect (this is only after I shut down the laptop firewall manually - God knows what port the SAMBA CLIENT needs open!). However when I try to browse the network through konqueror "smb://collins-net/" I get the error "could not connect to host for smb://collins-net/".
So I don't know - is SAMBA the way to go or is there a simpler solution? Your comments suggestions would be much appreciated. In the meantime I'm shutting down now and going for a sit down with a beer and a SuSE 9.2 Administration Guide!!!
Cheers,
Martin
On Sat, 2006-03-11 at 21:54 +0000, Martin John Collins wrote:
So I don't know - is SAMBA the way to go or is there a simpler solution? Your comments suggestions would be much appreciated. In the meantime I'm shutting down now and going for a sit down with a beer and a SuSE 9.2 Administration Guide!!!
Good you're doing the right thing..Samba is always easier to deal with after a beer :-)
Given that there are no Windows machines in the mix...you could achieve what you want with NFS and cups. Samba has it's uses but to be honest if you are only dealing with *nix to *nix then it's probably best to drop the mess that the SMB protocol can be.
YaST has a nice simple set up for NFS server and client...so I'll leave you to figure that out..Cups is best dealt with using the web interface
TO get admin access to the interface you may need to mess about with
lppasswd -g sys -a "existingusername"
Remote printing from another client is as simple as "lp inputfile -h hostname"...There should also be a facility in YaST to tell SuSE about remote lp queues so that they appear as printers in KDE but not having used it for a few years I couldn't tell you much about it.
Then assuming that you are using the SuSE Firewall, you need to open the correct ports. Looking at /etc/services will give you a good idea what needs to be done here.
Of course depending on how adverse you are to a terminal prompt you can do all this without YaST...However my experience with SuSE is to always let YaST configure what it can, as it gets a bit shirty if you start modifying configurations without it's help.
2006-03-11 at 21:54 +0000, Martin John Collins wrote:
Ahh I missed the bit about DHCP.
You have a few choices here....Let one of your computers issue DHCP and also run DNS populated from the DHCP leases granted (not always fun to get working)
or
Leave DHCP running on the router, but configure the router to have a gap in the address pool then you set a fixed address for the "server" machine (remembering to set up the default gateway and DNS addresses as your router)...Then go with the suggestions in my previous message (that's pretty much how I run at home)
or
Configure the server machine's Samba to be the wins server, look in the smb.conf file under [global] and the other machines to be wins clients (giving them the ip address of the wins server)
I don't know what route to go. I've read a little about internet printing protocol and configuring cups but that only covers the printing. Samba seems to address both but my first initial attempts have failed. I set up the workgroup COLLINS-NET through the SAMBA SERVER module in YAST which also opens up a firewall port on the server. I then configure the SAMBA CLIENT through YAST on the laptop and after entering the username and password it seems to connect (this is only after I shut down the laptop firewall manually
- God knows what port the SAMBA CLIENT needs open!). However when I try to
browse the network through konqueror "smb://collins-net/" I get the error "could not connect to host for smb://collins-net/".
collins-net is a workgroup...this only matters for browsing a whole network, if you are trying to connect to a specific machine your UNC path should be smb://hostname/(optional share name) not smb://workgroup/
Samba should take it's hostname from the system hostname.
Thanks very much indeed. I really didn't have a clue where to start. You've given me a lot to get on with and I'm looking forward to getting my hands dirty now I've got some pointers. Should keep me occupied for a least a week!!
Cheers, Martin
On Sunday 12 March 2006 00:54, Wayne Stallwood wrote:
through YAST on the laptop and after entering the username and password it seems to connect (this is only after I shut down the laptop firewall manually - God knows what port the SAMBA CLIENT needs open!). However when I try to browse the network through konqueror "smb://collins-net/" I get the error "could not connect to host for smb://collins-net/".
collins-net is a workgroup...this only matters for browsing a whole network, if you are trying to connect to a specific machine your UNC path should be smb://hostname/(optional share name) not smb://workgroup/
On Sat, 2006-03-11 at 21:54 +0000, Martin John Collins wrote:
Evening all,
Slowly but surely my Linux knowledge is growing but I have always avoided the big "N" as the alien terminology tends to make my head spin after about 5 mins of reading! But I'm going to give it a go. A full tutorial through the LUG is not what I'm after, but a few pointers of where to start would be appreciated.
When you feel confident and in need of some adventure... Have a look "avahi" http://avahi.org/wiki/WikiStart
I'm convinced that zeroconf networking "IS THE WAY TO GO" for home networking.....
Peter
On Saturday 11 March 2006 21:54, Martin John Collins wrote:
Evening all,
Slowly but surely my Linux knowledge is growing but I have always avoided the big "N" as the alien terminology tends to make my head spin after about 5 mins of reading! But I'm going to give it a go. A full tutorial through the LUG is not what I'm after, but a few pointers of where to start would be appreciated.
There's a desktop in the lounge (which will be the server) connected by cable to a Linksys wireless broadband router for ADSL internet access. My laptop connects to the internet wirelessly (ndiswrapper) through the router. Both machines connect to the router via DHCP and there are firewalls enabled on the desktop, the laptop and internally on the router. In the next couple of months I will be putting another desktop in my son's bedroom upstairs. All three machines will be running SUSE 10.0
I won't add too much to what's been said about printing, but as for file sharing - if they're all running suse 10, I'd stick with fish.
Ensuring your machines can access each other via ssh is the only prerequisite.
Deciding on one machine to host the files is nice for organisational reasons, and creating an extra user is too.
You then point konqueror to fish:/user@hostname:folder, and hey presto, instant file sharing via ssh. Quicker, less config if you're using yast, and more secure to boot.
If you like that sort of thing (I don't) you can even have konqy store your passwords in your encrypted wallet, plonk a link on your desktop and use it transparently as a "folder".
Fish really is the best thing since sliced bread for this kind of thing. :)
Of course, this assumes you have access to konqueror.
Ten.
-
Martin John Collins -
Peter Onion -
Ten -
Wayne Stallwood