How to troubleshoot these Samba Errors?

DanRaposo
DanRaposo used Ask the Experts™
on
I am having some difficulty brwsing my Samba domain.  I seem to all of a sudden be getting frequent authentication issues when attempting to browse the DOMAIN from a windows workstation.  It smells like a DNS problem, but I am not sure how to go about troubleshooting this.


When I Browse I get a warning that says "Domain is not accessible. You might not have permission to use this network resource."

NetBIOS is enabled over TCP/IP and the problem seems to come and go.     Here is a snippet from the nmbd.log file.


[2009/07/21 15:10:37, 3] nmbd/nmbd_winsserver.c:wins_process_name_query_request(1892)
  wins_process_name_query: name query for name UNKNOWN-HOST<00> from IP 192.168.0.113
[2009/07/21 15:10:37, 3] nmbd/nmbd_winsserver.c:wins_process_name_query_request(1927)
  wins_process_name_query: name query for name UNKNOWN-HOST<00> returning DNS fail.
[2009/07/21 15:10:37, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(454)
  process_name_query_request: Name query from 192.168.0.113 on subnet 192.168.0.7 for name UNKNOWN-HOST<00>
[2009/07/21 15:10:38, 3] nmbd/nmbd_winsserver.c:wins_process_name_query_request(1892)
  wins_process_name_query: name query for name WWW-3.IBM.COM<00> from IP 192.168.10.170
[2009/07/21 15:10:38, 3] nmbd/nmbd_winsserver.c:wins_process_name_query_request(1927)
  wins_process_name_query: name query for name WWW-3.IBM.COM<00> returning DNS fail.
[2009/07/21 15:10:38, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(454)
  process_name_query_request: Name query from 192.168.0.113 on subnet 192.168.0.7 for name UNKNOWN-HOST<00>
[2009/07/21 15:10:38, 3] nmbd/nmbd_winsserver.c:wins_process_name_query_request(1892)
  wins_process_name_query: name query for name MCA-055FDC<00> from IP 192.168.10.156
[2009/07/21 15:10:38, 3] nmbd/nmbd_winsserver.c:wins_process_name_query_request(1927)
  wins_process_name_query: name query for name MCA-055FDC<00> returning DNS fail.
[2009/07/21 15:10:38, 3] nmbd/nmbd_winsserver.c:wins_process_name_query_request(1892)
  wins_process_name_query: name query for name MCA-055FDC<20> from IP 192.168.10.156
[2009/07/21 15:10:38, 3] nmbd/nmbd_winsserver.c:wins_process_name_query_request(1927)




Any thoughts on how to tackle this one?  Running

Redhat 5.1 with Samba version
Version 3.0.25b-1.el5_1.4


 
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
It looks like you are having a problem with Internet Explorer Enhanced Security:

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23351830.html

This may sound odd, but try adding the UNC path to trusted sites in Internet explorer.

Author

Commented:
Sorry if I was not clear.  When I said browsing I did not mean with internet explorer.   I meant with Windows explorer.     I  did doublecheck and enhanced security is not enabled


"Caution: Internet Explorer Enhanced Security  Configuration is not enabled
Internet Explorer Enhanced Security Configuration is an option that  is provided in Windows Server 2003 operating systems. You can use it to quickly  enhance Internet Explorer security settings for all users."



Commented:
Does NSlookup resolve to that Server?

And is Netbios permitted on that Samba server so that Netbios broadcasts can populate the WINS records?
Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

Author

Commented:
This server is a newly installed Symantec Endpoint Protection server so it could be blocking something.  I will see if I can find anything in the setings.  But if it was blocking it I would expect it to be more consistent and never get through.

Commented:
To test, do a port query:

Portqry is a command line utility that comes from the 2003 server support tools.

Go to the command prompt of a server and type:
portqry -n problem_server -o 137,138,139,445 -p both

copy and paste your data into EE and let's see what we have.

Netbios and SMB shares are shared in two different ways simultaneously and use these ports:

1st way: (Netbios over SMB)
SMB port 445 TCP
Netbios datagram port 139 UDP

2nd way: (Netbios over TCP/IP)
Netbios/Wins port 137 TCP
Netbios datagram port 138 UDP
Netbios datagram port 139 UDP.

Author

Commented:
 
Querying target system called:  
   
 sav  
   
Attempting to resolve name to IP address...  
   
   
Name resolved to 192.168.0.8  
   
querying...  
   
TCP port 137 (netbios-ns service): NOT LISTENING  
   
UDP port 137 (netbios-ns service): LISTENING or FILTERED  
   
TCP port 138 (unknown service): NOT LISTENING  
   
UDP port 138 (netbios-dgm service): LISTENING or FILTERED  
   
Invalid port specified with -o option: `39  
Valid range 1-65535  

Author

Commented:
oops ... wrong one ...

 
Querying target system called:  
   
 sav  
   
Attempting to resolve name to IP address...  
   
   
Name resolved to 192.168.0.8  
   
querying...  
   
TCP port 137 (netbios-ns service): NOT LISTENING  
   
UDP port 137 (netbios-ns service): LISTENING or FILTERED  
   
TCP port 138 (unknown service): NOT LISTENING  
   
UDP port 138 (netbios-dgm service): LISTENING or FILTERED  
   
TCP port 139 (netbios-ssn service): LISTENING  
   
UDP port 139 (unknown service): NOT LISTENING  
   
TCP port 445 (microsoft-ds service): LISTENING  
   
UDP port 445 (microsoft-ds service): LISTENING or FILTERED  

Commented:
It appears Netbios over TCP/IP is turned off, or you have a firewall on the netbios ports 137 TCP and 139 UDP.

Try, as a test, to disable windows firewall.

Author

Commented:
Windows firewall is disabled .. HOWEVER, the SEP client is also installed on this system, which is an SEP server and that has some firewall configuration of it's own.

Author

Commented:
I'm sorry I jjust realized that in this thread I never mentioned that I was troubleshooting remote installs for an Antivirus server.  I guess I thought  that I was goign to find out this was  a SAMBA or DNS problem and was not linking it to a single server (client)

Commented:
SAMBA shares work on two paths simultaneously.

One is Netbios over TCP/IP

The second is SMB shares.

UDP port 139 is not listening. This is a datagram port needed for both methods of sharing.

Author

Commented:
I have turned off windows firewall andd Symantec Endpoint Protection (via services) and it still does not seem to be listening on upd 139.  Any other suggestions before I call Symantec?

Commented:
I don't know how to make exeptions to firewall ports with SEP.
Recommend this gets closed.  I have not found an answer, but I am able to work around my particular issue.

Author

Commented:
I NEED THIS CLOSED SO I CAN ASK ADDITIONAL QUESTION.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial