Networking Complete

English Network/Internet
1

My whole network does not work on Fedora or openSUSE (both being .rpm kde systems) but it works on ubuntu

I have the following:

-A external with Fedora 12
-Desktop with openSUSE 11.2
-A laptop with no batteries and bad networking device with ubuntu 9.10*
-A iMac Leopard (no snow)*
-A Macbook pro w/ tiger*
-A windows built for vista, Dell with XP*
-Two broken windows computers…

I hope that will help you w/ thy problem in hand.

  • means successfully networked

The external runs on the openSUSE desktop computer…

-stephenmac7

PS nfs + samba don’t work

2

But really the windows and mac computers are not mine…
They are someone elses

3

I am sorry, but your post does not contain any usefull information for people who are supposed to help you.

How did you configure your NC? In YaST, Network manager?
Cabled, Wireless? When wireless, which hardware, no problems during configuration?
Output of

ifconfig -a

(as root).
…
…

4 
eth0      Link encap:Ethernet  HWaddr 00:11:11:B5:B5:36
          inet addr:192.168.2.6  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::211:11ff:feb5:b536/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:47937 errors:0 dropped:0 overruns:0 frame:0
          TX packets:35830 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:54429297 (51.9 Mb)  TX bytes:4129721 (3.9 Mb)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:62 errors:0 dropped:0 overruns:0 frame:0
          TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3700 (3.6 Kb)  TX bytes:3700 (3.6 Kb)
5

I used NetworkManager w/ yast2 + Dolphin for share managing

6

Your NIC at eth0 seems to have an ethernet address. Now you say you have no network. Did you try to ping one of the other systems? Or what did you try that you come to the conclusion your are not attached to the LAN?

7

I went to the network folder and it was completely empty… I am sorry I was unclear… I meant sharing doesn’t work on the non-stared devices…

8

So it is not at all about your network! You mean you can ping by IP addess (what means network connected) and ping by name (what means DNS functioning). And when you can then also reach the Internet e.g. by reading and posting the Forums, I would say you have network connectivity.

Also you probably can do all sorts of client server over the LAN. But what fails is using file systems on the other systems? When you mean that then please state if it is NFS what you are trying (between Unix/Linux systems) or Samba (where MS systems are involved)?

When it is about Samba try this: openSUSE SuSE Linux HOWTOs and Tutorials by Swerdna. It seems to help a lot of people.

9

If you type

smb://<computer's IP>

does anything come up?

I have had most of my systems not want to “see” the file server, but when I put in “smb://…” then it pulls it up fine.

Rarely, I’ve put in the ip address plus one known shared folder, but I usually don’t have to do that.

10

nothing only

Unable to find any workgroups in your network this may be caused because of a firewall

The workgroup name is WORKGROUP and sharing server does not work either even with NFS

11

Check your firewall settings? I remember having to do something to access my network with an older suse installation, but I don’t know if it is still true.

12

[QUOTE=stephenmac7;2142141
The workgroup name is WORKGROUP and sharing server does not work either even with NFS[/QUOTE]
What do you mean with this? Either you use Samba or you use NFS. When NFS there is no such thing as a workgroup.

13

nope the workgroup “WORKGROUP” won’t show

14

I tried samba, it did not work, then I tried NFS… very simple

15

Do you mean you in stalled an NFS server at one side and NFS client at the other side and it did not function? And that you did not post here saying: " Listen, this I have done on the server side, here is my exports, and this is my fstab on the client side and I went to YaST, etc, but it does not work, please help"?

And you did not answer the question how it comes you talk about a ‘workgroup’ in conjunction with NFS.

16

I was talking about samba only, and yes I did install nfs on the server and client and no, It did not work and yes I tried to fix it with yast2, all my network folders are completely empty.

17

Now please, can you decide on which you want to try to get running, Samba or NFS.

When you decide for Samba you should work with Swerdna’s Howto given above and ask when runing into problems. May be starting a new thread with something like “Problems with Samba” in the title, to get the Samaba gurus to the rescue (not me, forgot almot everything about the little Samba knowledge I had).

When you decide fort NFS I can try to help you, or when you want more NFS gurus looking into your problem, make a new thread with an appropriate title.

To help you in the decision, it is not simple NFS or Samba depending on the time of the day.
. NFS is for remote mounting of directories between Unix/Linux systems. It supports Unix/Linux features like user/group ownership and access bits.
. Samba is designed to let Unix/Linux sysems act as File/printer servers for Windows systems (and later vv). Specialy in the situation where Linux systems mount Windows file systems there are restrictions because the windows file systems do not support e.g. users/group ownership and access bits. These restrictions are made as tranparent as possible, but they are still there.

IMHO it is simple: when no MS OS is involved go for NFS, else for Samba.

18

then nfs not samba

19

Let us start with the server. You must have installed nfs-kernel-server and it is nice to have yast-nfs-server. You most probably have this allready.

You can then go to YaST > network services > NFS Server. Toggle to start, when you have the Firewall on check to open the ports, unless you think different you do not need NFSv4. Go to Next. Here you can add the directory/ies you want to export. For every exported directory you can, in the lower field, add if you want to limit the export to certain hosts and you can add options there. For options, rw,no_subtree_check is a nice default. You may want to consult

man exports

for more options.
Finish. Now the server must be runing. Before we carry on we check with the output of (please post):

cat /etc/exports

and:

netstat -at | grep LISTEN

Important to bear in mind:
As you know in Unix/Linux files (and thus also directories) are owned. This ownership is by userid and groupid which are numbers. The username is only a local alias for the userid. likewise the groupname.
When a directory is exported by system A and mounted by system B, system B will see the numeric userids/groupids which may not be the same users as on system A. The owners on system A may not even exist on system B. Thus it is very benificial when the same users on system A are defined on system B and with the same numbers. E.g. when you have the username stephenmac7 with userid 1001 on system A, which is the owner of exported data, on system B the user with userid 1001 will be the owner. Let us hope it has username stephenmac7 :wink: (or aleast represent the same physical person).
When this is not the case, options to increase security are available. But let us first see to get it functioning.

20

network services (xinetd)?

nothing there…

I user the kde program launcher “nfs” the only thing is ‘nfs client’ and this computer is supposed to be the server