On Mon, 2008-04-14 at 17:43 -0400, Claude Jones wrote: > On Monday April 14 2008 4:43:29 pm Craig White wrote: > > There is no known issue with samba on Fedora for this to > > occur. > > > > I'm sure that's technically true. But we have two machines here, > side by side, one is running Fedora, the other PCLinuxOS off a > live CD; one is readily configured in a few minutes to browse my > network, the other, Fedora, has me jumping endless hoops...at my > age, that's not pretty to watch > > > I'm sure it's a configuration issue, whether it's 'hosts > > allow' setting in smb.conf or network misconfiguration or > > firewall setting or ??? > > > > Indeed, I'm sure you're right - but which configuration issue???? > > > try this... > > > > nmblookup -M WORKGROUP -d 10 > > > # nmblookup -M WORKGROUP -d 10 > INFO: Current debug levels: > all: True/10 > tdb: False/0 > printdrivers: False/0 > lanman: False/0 > smb: False/0 > rpc_parse: False/0 > rpc_srv: False/0 > rpc_cli: False/0 > passdb: False/0 > sam: False/0 > auth: False/0 > winbind: False/0 > vfs: False/0 > idmap: False/0 > quota: False/0 > acls: False/0 > locking: False/0 > msdfs: False/0 > dmapi: False/0 > lp_load: refreshing parameters > Initialising global parameters > params.c:pm_process() - Processing configuration > file "/etc/samba/smb.conf" > Processing section "[global]" > doing parameter log file = /var/log/samba/%m.log > doing parameter ldap ssl = No > doing parameter restrict anonymous = no > doing parameter domain master = no > doing parameter wins support = true > doing parameter dns proxy = no > doing parameter cups options = raw > doing parameter max protocol = NT > doing parameter default service = global > doing parameter acl compatibility = > doing parameter server signing = Auto > doing parameter security = share > doing parameter preferred master = no > doing parameter max log size = 50 > doing parameter workgroup = workgroup > pm_process() returned Yes > lp_servicenumber: couldn't find homes > set_server_role: role = ROLE_STANDALONE > Attempting to register new charset UCS-2LE > Registered charset UCS-2LE > Attempting to register new charset UTF-16LE > Registered charset UTF-16LE > Attempting to register new charset UCS-2BE > Registered charset UCS-2BE > Attempting to register new charset UTF-16BE > Registered charset UTF-16BE > Attempting to register new charset UTF8 > Registered charset UTF8 > Attempting to register new charset UTF-8 > Registered charset UTF-8 > Attempting to register new charset ASCII > Registered charset ASCII > Attempting to register new charset 646 > Registered charset 646 > Attempting to register new charset ISO-8859-1 > Registered charset ISO-8859-1 > Attempting to register new charset UCS2-HEX > Registered charset UCS2-HEX > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > Substituting charset 'UTF-8' for LOCALE > added interface ip=192.168.2.16 bcast=192.168.2.255 > nmask=255.255.255.0 > bind succeeded on port 0 > socket option SO_KEEPALIVE = 0 > socket option SO_REUSEADDR = 1 > socket option SO_BROADCAST = 1 > Could not test socket option TCP_NODELAY. > Could not test socket option TCP_KEEPCNT. > Could not test socket option TCP_KEEPIDLE. > Could not test socket option TCP_KEEPINTVL. > socket option IPTOS_LOWDELAY = 0 > socket option IPTOS_THROUGHPUT = 0 > socket option SO_SNDBUF = 110592 > socket option SO_RCVBUF = 110592 > socket option SO_SNDLOWAT = 1 > socket option SO_RCVLOWAT = 1 > socket option SO_SNDTIMEO = 0 > socket option SO_RCVTIMEO = 0 > Socket opened. > lang_tdb_init: /usr/lib/samba/en_US.UTF-8.msg: No such file or > directory > querying WORKGROUP on 192.168.2.255 > Sending a packet of len 50 to (192.168.2.255) on port 137 > read_udp_socket: lastip 192.168.2.101 lastport 137 read: 62 > parse_nmb: packet id = 12544 > Received a packet of len 62 from (192.168.2.101) port 137 > nmb packet from 192.168.2.101(137) header: id=12544 > opcode=Query(0) response=Yes > header: flags: bcast=No rec_avail=No rec_des=Yes trunc=No > auth=Yes > header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 > answers: nmb_name=WORKGROUP<1d> rr_type=32 rr_class=1 > ttl=300000 > answers 0 char `....e hex 6000C0A80265 > Got a positive name query response from 192.168.2.101 ( > 192.168.2.101 ) > 192.168.2.101 WORKGROUP<1d> > > ****************************** > it should be picking up four machines, not one ---- sounds like a networking issue...a bad hub/router/cable or something because if the PCLinux system picks up 4 systems and the Fedora machine only sees 1 and they're both polling the same broadcast address, then something is preventing it from working. You can ping each of these systems from the Fedora box? Take the cable connection from the PCLinux system and plug it into the Fedora system...that should tell you something. Craig
