SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have two machines connected via a router, address 10.0.0.2. I can not yet get them to talk to each other, they both happily share the router to connect to the internet.
I have read the Admin guide, the user guide, and am still at a loss.
When I search network places I am told no work groups exist?
I have gone into user set up groups but am still lost.
Could some kind person please direct me to a simple howto, or explain the route to take.
The router is acting as a DNS server (I think) and automatically assigns addresses in the range 10.0.0.1 to 10.0.018.
Any help will be gratefully accepted.
I usually run NFS server/client so the computers in my network can talk to each other. It's pretty simple to do, but it's better for you to read about NFS:
Is one of your boxes a Window's box? In order to do a "Windows Share" you will need to run Samba client/server. I've used ftp effectively on the lan. I haven't tried nfs yet, but it is supposed to be a good protocol for two communicating Unix/Linux boxes.
The first and obvious step would be to see if the machines can "ping" each other. Let's say you have 10.0.0.2, 10.0.0.5, and 10.0.0.6 . From both machines try:
ping 10.0.0.2
ping 10.0.0.5
ping 10.0.0.6
This will tell you if the machines are capable of talking to one another.
Starting Samba should be easy, and can be done from YaST.
Hi
I can ping each machine, I multi-boot and wish to get rid of windowsXP from my machines.
I might be making life more difficult than it needs to be, but the machines will not talk to each other apart from pinging when both are running SUSE 9.1 pro.
I might have overdone it with the server software having loaded Samba,NFS et al..
The router assigns IP addresses, but the workgroups error is bugging me.
I have configured both machines the same, same users,same root, etc. but no go, apart from pinging.
I realise I am close which makes it doubly frustrating.
I have read several books but still have hit a stumbling block, the answer I know will be blindingly obvious but I can't see it.
Please help?
Try to disabling firewall on both machines (you have already a firewall builtin in the router, don't you?)
then start samba servers on both machines and setup one machine as Primary Domain Controller (in yast on the 1st page of samba configuration)
*edit*
I discovered today that if you don't enable Primary Domain Controller on one machine, you won't be able to browse samba network, you'll be only able to access the samba shares when you connect to the machine directly, e.g. by typing smb://Machine/ in Konqueror.
To temporarily disable the firewall (and see if that is your problem) you can (as root user) type "SuSEfirewall2 stop". I think samba shares are blocked at the firewall (IP tables) level by default. If stopping the firewall fixes it, then you will either need to permanently disable the firewall, or you will need to open several ports (137-139 I believe).
Seeing if you can smb:// in is also a good idea. You may need to use both. You should be able to smb using either the computer name, or IP address. You might need to try using IP addresses.
I built my firewall according to nfs howto, and then got my little lan going no trouble. The important files are hosts.allow and hosts.deny, at least when you are using nfs. Don't know about Samba. But then I don't have router either.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.