Hi,
I'm trying to setup a Linux box with Samba (1.9.18p10) and it isn't
having any luck making a home for itself on the network.
If I go to a Windows95 machine, I see all (well most) machines on the
net there, but not the Linux box. I can also not see any other machines
from the Linux box.
Here is log.nmbd output that repeats every 5 seconds or so:
find_workgroup_on_subnet: workgroup search for DYNDOMCTL001 on subnet
207.164.206.91: found
dump_workgroups: dump workgroup on subnet 207.164.206.91: netmask=
255.255.255.0:
DYNDOMCTL001(1) current master browser = UNKNOWN
OMEGA91 40009a03 (Newlix Corporation's Newlix Omega
v1.0.0-m)
and smb.conf [global] section:
[global]
server string = Newlix Corporation's Newlix Omega v1.0.0-m
security = server
password server = APASSSERVER
netbios name = OMEGA91
bind interfaces only = yes
interfaces = 192.168.2.91/255.255.255.0
name resolve order = lmhosts wins bcast host
guest account = netbios
printing = bsd
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=8192
SO_RCVBUF=8192
encrypt passwords = yes
unix password sync = yes
passwd program = /usr/bin/passwd %u
passwd chat = *new*pass* %n\n *new*pass* %n\n *change*
wins support = no
wins server = 192.168.2.66
wins proxy = yes
os level = 0
domain master = no
local master = no
preferred master = no
workgroup = DYNDOMCTL001
remote announce = 192.168.2.255
If I do 'smbclient -L omega91' I get:
Added interface ip=192.168.2.91 bcast=192.168.2.255 nmask=255.255.255.0
error connecting to 0.0.0.0:139 (Connection refused)
But if I do 'smbclient -L omega91 -R bcast' I get:
Added interface ip=192.168.2.91 bcast=192.168.2.255 nmask=255.255.255.0
Got a positive name query response from 192.168.2.91 ( 192.168.2.91 )
Server time is Mon May 18 23:14:00 1998
Timezone is UTC-4.0
Password:
Domain=[ADOMAIN] OS=[Unix] Server=[Samba 1.9.18p10]
connected as guest security=user
Server=[OMEGA91] User=[netbios] Workgroup=[ADOMAIN] Domain=[ADOMAIN]
Sharename Type Comment
--------- ---- -------
attached Printer Locally attached printer
cdrom Disk Newlix Omega 1.00m
(1999/05/12@23:03EST)
fax Disk FAX outgoing spool area
ftphome Disk FTP base directory
IPC$ IPC IPC Service (Newlix Corporation's
Newlix Omega v1.0.0-m)
shared Disk Shared file space for all users
webhome Disk Web base directory
This machine has a browse list:
Server Comment
--------- -------
OMEGA91 Newlix Corporation's Newlix Omega v1.0.0-m
This machine has a workgroup list:
Workgroup Master
--------- -------
ADOMAIN
'ifconfig eth0' reports:
eth0 Link encap:Ethernet HWaddr 00:80:C8:E1:E6:B1
inet addr:192.168.2.91 Bcast:192.168.2.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22815 errors:0 dropped:0 overruns:0 frame:1
TX packets:16404 errors:0 dropped:0 overruns:0 carrier:0
coll:2154
Interrupt:12 Base address:0x6c00
Please help!
--
// Jean-Serge Gagnon jsg@newlix.com
// Newlix Corporation http://www.newlix.com
An update on this: the 'smbclient -L omega91' was giving the error because the lmhosts file contained the IP 0.0.0.0 in it. Removing the IP in the lmhosts file fixed that error, but the Linxu server still can't see the other network systems and the Win95 system can't see OR connect to the Linxu server; i.e. you can't even type '\\OMEGA91' in the Location or Explorer4... Jean-Serge Gagnon wrote:> > Hi, > I'm trying to setup a Linux box with Samba (1.9.18p10) and it isn't > having any luck making a home for itself on the network. > > If I go to a Windows95 machine, I see all (well most) machines on the > net there, but not the Linux box. I can also not see any other machines > from the Linux box. > > Here is log.nmbd output that repeats every 5 seconds or so: > > find_workgroup_on_subnet: workgroup search for DYNDOMCTL001 on subnet > 207.164.206.91: found > dump_workgroups: dump workgroup on subnet 207.164.206.91: netmask> 255.255.255.0: > DYNDOMCTL001(1) current master browser = UNKNOWN > OMEGA91 40009a03 (Newlix Corporation's Newlix Omega > v1.0.0-m) > > and smb.conf [global] section: > > [global] > server string = Newlix Corporation's Newlix Omega v1.0.0-m > security = server > password server = APASSSERVER > netbios name = OMEGA91 > bind interfaces only = yes > interfaces = 192.168.2.91/255.255.255.0 > name resolve order = lmhosts wins bcast host > guest account = netbios > printing = bsd > socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=8192 > SO_RCVBUF=8192 > encrypt passwords = yes > unix password sync = yes > passwd program = /usr/bin/passwd %u > passwd chat = *new*pass* %n\n *new*pass* %n\n *change* > wins support = no > wins server = 192.168.2.66 > wins proxy = yes > os level = 0 > domain master = no > local master = no > preferred master = no > workgroup = DYNDOMCTL001 > remote announce = 192.168.2.255 > > If I do 'smbclient -L omega91' I get: > > Added interface ip=192.168.2.91 bcast=192.168.2.255 nmask=255.255.255.0 > error connecting to 0.0.0.0:139 (Connection refused) > > But if I do 'smbclient -L omega91 -R bcast' I get: > > Added interface ip=192.168.2.91 bcast=192.168.2.255 nmask=255.255.255.0 > Got a positive name query response from 192.168.2.91 ( 192.168.2.91 ) > Server time is Mon May 18 23:14:00 1998 > Timezone is UTC-4.0 > Password: > Domain=[ADOMAIN] OS=[Unix] Server=[Samba 1.9.18p10] > connected as guest security=user > > Server=[OMEGA91] User=[netbios] Workgroup=[ADOMAIN] Domain=[ADOMAIN] > > Sharename Type Comment > --------- ---- ------- > attached Printer Locally attached printer > cdrom Disk Newlix Omega 1.00m > (1999/05/12@23:03EST) > fax Disk FAX outgoing spool area > ftphome Disk FTP base directory > IPC$ IPC IPC Service (Newlix Corporation's > Newlix Omega v1.0.0-m) > shared Disk Shared file space for all users > webhome Disk Web base directory > > This machine has a browse list: > > Server Comment > --------- ------- > OMEGA91 Newlix Corporation's Newlix Omega v1.0.0-m > > This machine has a workgroup list: > > Workgroup Master > --------- ------- > ADOMAIN > > 'ifconfig eth0' reports: > > eth0 Link encap:Ethernet HWaddr 00:80:C8:E1:E6:B1 > inet addr:192.168.2.91 Bcast:192.168.2.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:22815 errors:0 dropped:0 overruns:0 frame:1 > TX packets:16404 errors:0 dropped:0 overruns:0 carrier:0 > coll:2154 > Interrupt:12 Base address:0x6c00 > > Please help! > > -- > // Jean-Serge Gagnon jsg@newlix.com > // Newlix Corporation http://www.newlix.com-- // Jean-Serge Gagnon jsg@newlix.com // Newlix Corporation http://www.newlix.com
Nothinman wrote:> > One of your problems I believe is that if you have "bind interfaces only > true" you must list lo(127.0.0.1) in the list so that smbd can connect to > it's self. > > Also you might want to upgrade to the 2.0.x series, it is much improved and > the swat configuration util that comes with it is great to start a smb.conf > with.I would like to go to 2.x, but there are reasons why I can't at this time. Are you sure about the 127.0.0.1 interface? Broadcast for browse list will not come from there as is with requests for connections from Windows clients. Has ANYBODY seen this problem before? Windows clients on the NetHood can NOT see the Linux box or connect to it (by using something like \\OMEGA9\CDROM). AND the Linux box can not connect to other machines (with smbclient -L WINNAME) or ever get a list of machines on the net even though they are ALL on the same subnet and are all configured to use the same WINS server! Thanks again. My original post was:> I'm trying to setup a Linux box with Samba (1.9.18p10) and it isn't > having any luck making a home for itself on the network. > > If I go to a Windows95 machine, I see all (well most) machines on the > net there, but not the Linux box. I can also not see any other machines > from the Linux box. > > Here is log.nmbd output that repeats every 5 seconds or so: > > find_workgroup_on_subnet: workgroup search for ADOMAIN on subnet > 192.168.2.91: found > dump_workgroups: dump workgroup on subnet 192.168.2.91: netmask> 255.255.255.0: > ADOMAIN(1) current master browser = UNKNOWN > OMEGA91 40009a03 (Newlix Corporation's Newlix Omega > v1.0.0-m) > > and smb.conf [global] section: > > [global] > server string = Newlix Corporation's Newlix Omega v1.0.0-m > security = server > password server = APASSSERVER > netbios name = OMEGA91 > bind interfaces only = yes > interfaces = 192.168.2.91/255.255.255.0 > name resolve order = lmhosts wins bcast host > guest account = netbios > printing = bsd > socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=8192 SO_RCVBUF=8192 > encrypt passwords = yes > unix password sync = yes > passwd program = /usr/bin/passwd %u > passwd chat = *new*pass* %n\n *new*pass* %n\n *change* > wins support = no > wins server = 192.168.2.66 > wins proxy = yes > os level = 0 > domain master = no > local master = no > preferred master = no > workgroup = ADOMAIN > remote announce = 192.168.2.255// Jean-Serge Gagnon jsg@newlix.com // Newlix Corporation http://www.newlix.com
Thanks, yes I can ping, telnet everything! It was the 'Scope ID' in the Windows machines. If I use the '-i scopeID' with nmbd, smbd, nmblookup and smbclient everything works... what a pain!!! So does anybody know why the Windows machines receive their scope ID from the WINS server, but the Linux box didn't? I mean if I look at all the environment variables when the dhclient-script (ISC DHCP) gets the bind request for an IP, there are no 'new-netbios-scope'... There are 'new_ip_address', 'new_netbios_name_server', etc... I will also ask in the dhclient list, but I was wondering if anyone else had this problem... (P.S. I am not the one that decided to use a ScopeID, that is my customer's decision) Thanks again. christian wrote:> On Thu, 20 May 1999, Jean-Serge Gagnon wrote: > > > Has ANYBODY seen this problem before? Windows clients on the NetHood can > > NOT > > see the Linux box or connect to it (by using something like > > \\OMEGA9\CDROM). > > AND the Linux box can not connect to other machines (with smbclient -L > > WINNAME) > > or ever get a list of machines on the net even though they are ALL on > > the same > > subnet and are all configured to use the same WINS server! > > Can the linux box ping the windows boxes? Can the windows boxes ping the > linux box? Can you at least nmblookup the windows boxes names?Gerald Carter wrote:> > Jean-Serge Gagnon wrote: > > > remote announce = 192.168.2.255 > ^^^^^^^^^^^^^^^ > You don't need this if all the machines are on the > same subnet. Not sure if removing it will fix all > your problems, but I would start there.-- // Jean-Serge Gagnon jsg@newlix.com // Newlix Corporation http://www.newlix.com