LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 09-19-2012, 10:11 AM   #1
Brandon9000
Member
 
Registered: Apr 2012
Location: Florida
Distribution: Many
Posts: 111

Rep: Reputation: Disabled
Samba problem: findsmb and nmblookup fail


I wrote a program which uses findsmb to get a list of Samba aware resources. It worked fine. It was able to see both my own cluster of virtuals and other company computers too. My company moved to a different location. The network was flakey for awhile, but has seemed okay for months now. I am not sure that moving is the cause of the problem I am about to describe, but it is the only obvious change. Now findsmb only discovers the machine I am running in. I am doing this in a number of VMWare virtuals, and have tried this in several. In every case, findsmb only finds localhost. I should repeat that this was working fine in the past. I did enough research to discover that findsmb relies on nmblookup. So I tried "nmblookup -A <ip address>" for several of the IPs around and it always comes back with "no reply." I have no idea what's wrong. Does anyone have any ideas?

Last edited by Brandon9000; 09-19-2012 at 11:47 AM.
 
Old 09-19-2012, 12:53 PM   #2
Brandon9000
Member
 
Registered: Apr 2012
Location: Florida
Distribution: Many
Posts: 111

Original Poster
Rep: Reputation: Disabled
I got a little more information. The log /var/log/messages contains:

Sep 19 13:49:58 linux nmbd[4891]: [2012/09/19 13:49:58, 0] nmbd/nmbd_packets.c:1072(process_browse_packet)
Sep 19 13:49:58 linux nmbd[4891]: process_browse_packet: Discarding datagram from IP xxx.xxx.xxx.xxx. Source name LINUX<00> is one of our names !

where I have used x for the IP. Does anyone know what this means or how to fix it?
 
Old 09-19-2012, 01:38 PM   #3
Brandon9000
Member
 
Registered: Apr 2012
Location: Florida
Distribution: Many
Posts: 111

Original Poster
Rep: Reputation: Disabled
No, that wasn't it. I defined different NetBIOS names for the computers in smb.conf and it made that error message go away, but I still get "no reply." Nmblookup can only see the local machine. Any ideas?
 
Old 09-19-2012, 02:55 PM   #4
Brandon9000
Member
 
Registered: Apr 2012
Location: Florida
Distribution: Many
Posts: 111

Original Poster
Rep: Reputation: Disabled
Okay, I think I have an answer more or less. One of the virtuals I had up to be "seen" from my dev virtual was on a different subnet. The other, just has some problem with Samba. I brought up two additional virtuals and findsmb run from my dev virtual can see both of them. There was no global problem, just problems with the two virtuals I had up to be detected. It is interesting that I can no longer see the few Samba aware resources of other people in my company, but I'll just chalk that up to increased security at our new location.
 
Old 01-17-2013, 10:19 PM   #5
apjjr
LQ Newbie
 
Registered: Jan 2013
Posts: 1

Rep: Reputation: Disabled
I have also been having problems with findsmb seeing only the local machine, so I started looking for a work-around.
Try the following:
Quote:
echo -e "smblist.sh $(date)\n"; smbtree -SN|grep '\\'|cut -f2|cut -c 3-|sort|while read svr; do echo -ne "$svr\t"; ipname=$(nmblookup $svr|grep '<00>'); cmnt=$(smbclient -NL $svr 2>&1|grep -m 1 'IPC'|cut -c 40-); echo -e "$ipname\t$cmnt"; smbclient -NL $svr 2>&1|grep Disk; done; exit 0
I'm still trying to find out why findsmb fails. I seem to remember it working in years past.
Alex

Last edited by apjjr; 01-18-2013 at 09:56 PM. Reason: Improved code
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Fedora 4: Samba running but nmblookup doesn't work and can't see in windows lsgko Linux - Networking 3 09-14-2005 11:10 PM
nmblookup problem. bruse Linux - Networking 1 09-07-2005 02:07 PM
Samba - nmblookup will_k Linux - Networking 3 08-25-2003 01:48 AM
Samba problem, nmblookup not finding W2K box dwynter Linux - Networking 5 06-24-2003 02:44 PM
Samba Prob: nmblookup failure paulmann Linux - Networking 2 06-09-2003 07:17 PM


All times are GMT -5. The time now is 07:01 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration