Simple networking blues - what did I break?
I installed SuSE 10.0 on two PCs at my house. Initially, both could browse the web; both used DHCP from my LinkSys router. For now, the network is: - two PCs (SuSE 10) on the LAN side of - LinkSysWRT54G domestic broadband router - an ADSL modem, on the WAN side of the router, connected to my ISP I used YaST on both machines to give them static addresses. One machine (this one I'm typing from) connects successfully to internet. The other machine does _not_. They can each ping the other. They can each reach the config page of the LinkSys router. I have tried leaving the DHCP server on, and also tried switching it off at the LinkSys. No change. From YaST, the following are the particulars of the two machines, first the non-connecting PC: YaST > Network Services > DNS & Hostname Hostname Domain Name thatbox ourhouse Name Servers & Domain Search List Name Server1 Domain Search1 206.191.0.140 magma.ca <--- (also tried "ourhouse") Name Server2 206-191.0.210 YaST > Hostnames Current Hosts IP Address Hostname Host aliases 127.0.0.1 localhost 192.168.1.80 thatbox.ourhouse thatbox ::1 localhost ipv6-localhost ipv6-loopback etc...... YaST > Network Devices > Network Card Name IP Address IBM EtherExpress PRO/100 VE 192.168.1.80 Subnet mask 255.255.255.0 And now, for the machine that _does_ connect successfully: YaST > Network Services > DNS & Hostname Hostname Domain Name thisbox ourhouse Name Servers & Domain Search List Name Server1 Domain Search1 206.191.0.140 ourhouse Name Server2 206-191.0.210 YaST > Hostnames Current Hosts IP Address Hostname Host aliases 127.0.0.1 localhost 192.168.1.90 thisbox.ourhouse thisbox ::1 localhost ipv6-localhost ipv6-loopback etc...... YaST > Network Devices > Network Card Name IP Address AOPEN RTL-8139/8139C/8139C+ 192.168.1.90 Subnet mask 255.255.255.0 The only difference that I see between the two is "Domain Search1" is set to "ourhouse" in one and to my ISP "magma.ca" in the other... but I've tried both settings and it makes no difference. Currently, firewall is disabled on both machines -- I feel so naked. At this minute, while I'm sending this, the LinkSys' DHCP server is disabled. What am I overlooking? Where is the setting? YaST > Network Services > Network Services (xinetd) is currently not enabled (and never was) on both machines. I just pinged each machine from the other, seconds ago. What's wrong on "thatbox" that it can't see my ISP or beyond? Yes, I know the answer is right in front of my face, but I'm not seeing it. Be as sarcastic as you wish, but please point me at what I'm not allowing myself to see. Kevin (two steps forward, three steps back...)
On Sat, 2005-10-15 at 13:35 -0400, elefino wrote:
I installed SuSE 10.0 on two PCs at my house. Initially, both could browse the web; both used DHCP from my LinkSys router. For now, the network is: - two PCs (SuSE 10) on the LAN side of - LinkSysWRT54G domestic broadband router - an ADSL modem, on the WAN side of the router, connected to my ISP
I used YaST on both machines to give them static addresses. One machine (this one I'm typing from) connects successfully to internet. The other machine does _not_. They can each ping the other. They can each reach the config page of the LinkSys router.
I have tried leaving the DHCP server on, and also tried switching it off at the LinkSys. No change.
From YaST, the following are the particulars of the two machines, first the non-connecting PC:
YaST > Network Services > DNS & Hostname Hostname Domain Name thatbox ourhouse
Name Servers & Domain Search List Name Server1 Domain Search1 206.191.0.140 magma.ca <--- (also tried "ourhouse") Name Server2 206-191.0.210
YaST > Hostnames Current Hosts IP Address Hostname Host aliases 127.0.0.1 localhost 192.168.1.80 thatbox.ourhouse thatbox ::1 localhost ipv6-localhost ipv6-loopback etc......
YaST > Network Devices > Network Card Name IP Address IBM EtherExpress PRO/100 VE 192.168.1.80 Subnet mask 255.255.255.0
And now, for the machine that _does_ connect successfully:
YaST > Network Services > DNS & Hostname Hostname Domain Name thisbox ourhouse
Name Servers & Domain Search List Name Server1 Domain Search1 206.191.0.140 ourhouse Name Server2 206-191.0.210
YaST > Hostnames Current Hosts IP Address Hostname Host aliases 127.0.0.1 localhost 192.168.1.90 thisbox.ourhouse thisbox ::1 localhost ipv6-localhost ipv6-loopback etc......
YaST > Network Devices > Network Card Name IP Address AOPEN RTL-8139/8139C/8139C+ 192.168.1.90 Subnet mask 255.255.255.0
The only difference that I see between the two is "Domain Search1" is set to "ourhouse" in one and to my ISP "magma.ca" in the other... but I've tried both settings and it makes no difference. Currently, firewall is disabled on both machines -- I feel so naked.
At this minute, while I'm sending this, the LinkSys' DHCP server is disabled.
What am I overlooking? Where is the setting?
YaST > Network Services > Network Services (xinetd) is currently not enabled (and never was) on both machines. I just pinged each machine from the other, seconds ago. What's wrong on "thatbox" that it can't see my ISP or beyond?
Yes, I know the answer is right in front of my face, but I'm not seeing it. Be as sarcastic as you wish, but please point me at what I'm not allowing myself to see.
What is the output of route -nr of both. It sounds like thathouse does not have a default route set. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On 10/15/05, elefino
I installed SuSE 10.0 on two PCs at my house. Initially, both could browse the web; both used DHCP from my LinkSys router.
[snipped lots of useful info] elefino, Did you specify a default gateway for 'thatbox'? Just asking because it's missing in the initial post (YaST > Network Devices > Network Card > Network address setup > Routing). \Steve
On Saturday 15 October 2005 14:01, Steve Graegert wrote:
Did you specify a default gateway for 'thatbox'? Just asking because it's missing in the initial post (YaST > Network Devices > Network Card > Network address setup > Routing).
Duh! (applying another bruise to forehead..... whap!) Works. Thanks. Now for the next step. The purpose of setting static IP, rather than using DHCP was to set up Samba Servers and Clients on each box, to allow them to share some of each others' files. (I'm not entirely clear on why, but it was somebody's suggestion, and they probably know more than I, so I went for it...) I have (what I believe to be) Samba server configured on thisbox.ourhouse. For a workgroup, I gave it OURHOUSE, as well. Other than that, I just mostly accepted defaults as I went through the YaST Samba Server config module. Went to other machine (thatbox.ourhouse) and started the YaST Samba Client module. An early step is to browse to existing workgroups and accept one. I get nothing in the Existing Neighbors pop-up dialog. Is there something that I need to switch on, in order for the Samba server on "thisbox.ourhouse" to become visible to the Samba Client setup dialog on "thatbox.ourhouse"? I'm pretty sure that the server on "thisbox.ourhouse" is running, because: thisbox:~ # rcnmb start && rcsmb start Starting Samba NMB daemon - Warning: daemon already running. done Starting Samba SMB daemon - Warning: daemon already running. done thisbox:~ # Again, I'm missing something, and it'll be really blatant and foolish, but... my eyes keep sliding past whatever it is. Ideas? Both systems now have: - static IP - sufficient network config to ping each other, and to browse the web. Is there another prerequisite before Samba can be working on this two-PC network? Are there any Samba server settings that I should forward that would tell anybody anything useful? Kevin
'm just adding one comment to my previous-post question: The SuSE firewalls are still OFF for both machines, if anybody was going to ask me that. (Save another e-mail turnaround...) Summary of question: Two-PC network with LinkSys router. IP is configured sufficient that both PCs can browse the web and can ping each other. Samba server configured on thisbox.ourhouse, keeping most defaults and naming the Workgroup "OURHOUSE". Server started. On the second PC, thatbox.ourhouse, Samba Client config dialog cannot see ANY neighbors. I thought it should be able to see OURHOUSE workgroup, so that I could select that and continue with client setup. Wondering why it doesn't, and what additional configuration I need to do first. Kevin
On 10/15/05, elefino
'm just adding one comment to my previous-post question:
The SuSE firewalls are still OFF for both machines, if anybody was going to ask me that. (Save another e-mail turnaround...)
Summary of question:
Two-PC network with LinkSys router. IP is configured sufficient that both PCs can browse the web and can ping each other.
Samba server configured on thisbox.ourhouse, keeping most defaults and naming the Workgroup "OURHOUSE". Server started.
On the second PC, thatbox.ourhouse, Samba Client config dialog cannot see ANY neighbors. I thought it should be able to see OURHOUSE workgroup, so that I could select that and continue with client setup. Wondering why it doesn't, and what additional configuration I need to do first.
How is your samba server configured? You may want to post your /etc/samba/smb.conf (please only active options, not the commented ones). Without knowing the configuration help is very limited. \Steve PS: Why are you using samba in a Linux to Linux environment? (Got to admit, I never tried that) NFS is more suitable in this situation.
On Saturday 15 October 2005 16:15, Steve Graegert wrote: [...]
How is your samba server configured? You may want to post your /etc/samba/smb.conf (please only active options, not the commented ones). Without knowing the configuration help is very limited.
This is going to hurt, but here goes... [global] workgroup = OURHOUSE printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = Yes domain master = Yes local master = Yes netbios name = thisbox os level = 65 passdb backend = smbpasswd:smbpasswd preferred master = Yes security = user [homes] comment = Home Directories valid users = %S browseable = No read only = No inherit acls = Yes [profiles] comment = Network Profiles Service path = %H read only = No store dos attributes = Yes create mask = 0600 directory mask = 0700 [users] comment = All users path = /home read only = No inherit acls = Yes veto files = /aquota.user/groups/shares/ [groups] comment = All groups path = /home/groups read only = No inherit acls = Yes [printers] comment = All Printers path = /var/tmp printable = Yes create mask = 0600 browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775 [netlogon] comment = Network Logon Service path = /var/lib/samba/netlogon write list = root That's all of it except for a couple of comment lines that were at the top. By the way, in /etc/samba, my smbusers and smbpasswd files have never been touched (they have dates from July). I don't know if that's significant.
PS: Why are you using samba in a Linux to Linux environment? (Got to admit, I never tried that) NFS is more suitable in this situation.
Because: - I once had it accidentally working (SuSE 9.1, I think) for several months (my wife was happily sharing files on my PC, and I could send files to hers for printing, faxing, etc.) - Several people have recommended Samba as being faster than nfs, as well as easier to configure (I never did get nfs to work) - the second computer "thatbox.ourhouse" is dual-boot with Win98, and I might like to get Windows to see network shares, someday. Kevin
On 10/15/05, elefino
On Saturday 15 October 2005 16:15, Steve Graegert wrote: [...]
How is your samba server configured? You may want to post your /etc/samba/smb.conf (please only active options, not the commented ones). Without knowing the configuration help is very limited.
This is going to hurt, but here goes...
[global] workgroup = OURHOUSE printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = Yes domain master = Yes local master = Yes netbios name = thisbox os level = 65 passdb backend = smbpasswd:smbpasswd preferred master = Yes security = user [homes] comment = Home Directories valid users = %S browseable = No read only = No inherit acls = Yes [profiles] comment = Network Profiles Service path = %H read only = No store dos attributes = Yes create mask = 0600 directory mask = 0700 [users] comment = All users path = /home read only = No inherit acls = Yes veto files = /aquota.user/groups/shares/ [groups] comment = All groups path = /home/groups read only = No inherit acls = Yes [printers] comment = All Printers path = /var/tmp printable = Yes create mask = 0600 browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775
[netlogon] comment = Network Logon Service path = /var/lib/samba/netlogon write list = root
OK, looks good. Now, when the samba server is running you should be able to mount one of the home directories: john@smbclient % su Enter password for root: # mount -t smbfs -o rw,username=john //server/home/john /mnt/john This requires that user 'john' is added to the smbpasswd database: john@smbserver % su Enter password for root: # smbpasswd -a john <provide password> Now, john can be authenticated at the server.
By the way, in /etc/samba, my smbusers and smbpasswd files have never been touched (they have dates from July). I don't know if that's significant.
Yes, it is. See above.
PS: Why are you using samba in a Linux to Linux environment? (Got to admit, I never tried that) NFS is more suitable in this situation.
Because: - I once had it accidentally working (SuSE 9.1, I think) for several months (my wife was happily sharing files on my PC, and I could send files to hers for printing, faxing, etc.)
Aha.
- Several people have recommended Samba as being faster than nfs, as well as easier to configure (I never did get nfs to work)
Hmm, every UNIX system provides for NFS clients and servers, configured in less than a minute. Unless you're using Windows and Linux only Samba is fine, but other clients (e.g. BSDs) will have to use the ugly smbclient interface due to the lack of smbfs support. Would be no option for me, but that's not important here. When it comes to speed, both are highly tunable, so it's possible to achieve impressive results with NFS and Samba.
- the second computer "thatbox.ourhouse" is dual-boot with Win98, and I might like to get Windows to see network shares, someday.
Indeed, a pressing argument. \Steve
On Sat, 2005-10-15 at 22:15 +0200, Steve Graegert wrote:
On 10/15/05, elefino
wrote: 'm just adding one comment to my previous-post question:
The SuSE firewalls are still OFF for both machines, if anybody was going to ask me that. (Save another e-mail turnaround...)
Summary of question:
Two-PC network with LinkSys router. IP is configured sufficient that both PCs can browse the web and can ping each other.
Samba server configured on thisbox.ourhouse, keeping most defaults and naming the Workgroup "OURHOUSE". Server started.
On the second PC, thatbox.ourhouse, Samba Client config dialog cannot see ANY neighbors. I thought it should be able to see OURHOUSE workgroup, so that I could select that and continue with client setup. Wondering why it doesn't, and what additional configuration I need to do first.
How is your samba server configured? You may want to post your /etc/samba/smb.conf (please only active options, not the commented ones). Without knowing the configuration help is very limited.
\Steve
PS: Why are you using samba in a Linux to Linux environment? (Got to admit, I never tried that) NFS is more suitable in this situation.
Consider this idea, you could have guest win-systems, so having one export (smb ) and not two (smb and nfs) is easier, or so it would seem, to support. I've hit this wall on my systems as well. Right now my file server exports the same directory 192.168.2.101/data1 as both smb and nfs. If I could figure out how to get the linux clients to read/write, and even find the smb export, I wouldn't bother with nfs. Mike
On 10/16/05, Mike McMullin
On Sat, 2005-10-15 at 22:15 +0200, Steve Graegert wrote:
On 10/15/05, elefino
wrote: 'm just adding one comment to my previous-post question:
The SuSE firewalls are still OFF for both machines, if anybody was going to ask me that. (Save another e-mail turnaround...)
Summary of question:
Two-PC network with LinkSys router. IP is configured sufficient that both PCs can browse the web and can ping each other.
Samba server configured on thisbox.ourhouse, keeping most defaults and naming the Workgroup "OURHOUSE". Server started.
On the second PC, thatbox.ourhouse, Samba Client config dialog cannot see ANY neighbors. I thought it should be able to see OURHOUSE workgroup, so that I could select that and continue with client setup. Wondering why it doesn't, and what additional configuration I need to do first.
How is your samba server configured? You may want to post your /etc/samba/smb.conf (please only active options, not the commented ones). Without knowing the configuration help is very limited.
\Steve
PS: Why are you using samba in a Linux to Linux environment? (Got to admit, I never tried that) NFS is more suitable in this situation.
Consider this idea, you could have guest win-systems, so having one export (smb ) and not two (smb and nfs) is easier, or so it would seem, to support. I've hit this wall on my systems as well. Right now my file server exports the same directory 192.168.2.101/data1 as both smb and nfs. If I could figure out how to get the linux clients to read/write, and even find the smb export, I wouldn't bother with nfs.
In a mixed environment Samba is the best choice. I thought its pure Linux/UNIX. To your Samba problem: 1. Is Samba running? (/etc/init.d/smb start) 2. Did you add the desired directory to the list of shares and disabled read-only ? 3. Did you add all hosts or networks to the list of allowed machines? \Steve
participants (4)
-
elefino
-
Ken Schneider
-
Mike McMullin
-
Steve Graegert