What is causing a windows XP to be inconsistant in connecting to a share point located on a Ubuntu based server?

One Windows XP PC out of several that are attached to an Ubuntu Linux server running Samba inconsistently is unable to connect to the Samba share point.  When this happens, this message appears in the /var/log/samba/log.nmbd file:

[2008/01/29 08:24:28, 0] nmbd/nmbd_namequery.c:query_name_response(101)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.199 for name BAW<1d>.
  This response was from IP 192.168.0.20, reporting an IP address of 192.168.0.20.

The workgroup name in this PC is the same as all the other PC's - BAW.

What is causing this message, does it have anything to do with being unable to connect to a share point?
The final question is how to make this one PC as reliable as the others when connecting to a share point?
gmbrammerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

olehbCommented:
1. Check netbios name of this one XP PC, it definitely have to not be BAW.
2. Does it have 192.168.0.20 IP?
3. Could you please attach smbd & nmbd logs in that period of time when a problem happens?
0
gmbrammerAuthor Commented:
1. The netbios name of the PC is definitely not BAW.
2. The IP address of the PC is set to 192.168.0.20
3. This is from /var/log/log.nmbd:

[2008/02/01 08:48:29, 0] nmbd/nmbd_namequery.c:query_name_response(101)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.199 for name BAW<1d>.
  This response was from IP 192.168.0.20, reporting an IP address of 192.168.0.20.
[2008/02/01 09:23:30, 0] nmbd/nmbd_namequery.c:query_name_response(101)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.199 for name BAW<1d>.
  This response was from IP 192.168.0.20, reporting an IP address of 192.168.0.20.
[2008/02/01 11:08:25, 0] nmbd/nmbd_namequery.c:query_name_response(101)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.199 for name BAW<1d>.

This log is from /var/log/log.smbd

Thanks for the resonse.
Gary Brammer


0
gmbrammerAuthor Commented:
Here is the log from /var/log/samba/log.smbd:

[2008/02/01 07:01:22, 1] smbd/service.c:make_connection_snum(693)
  time (192.168.0.115) connect to service timewolf initially as user nobody (uid=65534, gid=65534) (pid 17520)
[2008/02/01 07:03:37, 0] lib/util_sock.c:write_data(557)
[2008/02/01 07:03:37, 1] smbd/service.c:make_connection_snum(693)
  192.168.0.101 (192.168.0.101) connect to service Today'sArt initially as user nobody (uid=65534, gid=65534) (pid 17522)
[2008/02/01 07:03:37, 1] smbd/service.c:make_connection_snum(693)
  192.168.0.101 (192.168.0.101) connect to service Xfer initially as user nobody (uid=65534, gid=65534) (pid 17522)
[2008/02/01 07:03:37, 1] smbd/service.c:make_connection_snum(693)
  192.168.0.101 (192.168.0.101) connect to service Yesterday initially as user nobody (uid=65534, gid=65534) (pid 17522)
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

olehbCommented:
Could you please increase samba log level and attach log file? In section [global] of /etc/samba/smb.conf add string
log level = 2 passdb:3 auth:4
By the way, what is error response on XP PC?
0
olehbCommented:
Also you need to reload samba configuration using commands:
/etc/init.d/smb reload
/etc/init.d/nmb reload
0
gmbrammerAuthor Commented:
I have reloaded the conf files to the daemons and done a stop/start on the smbd and nmbd.  However, this server is for a small business and won't have any share point attachments until Monday.  Thanks for your suggestions so far; hopefully you will see something in th log files on Monday.
0
gmbrammerAuthor Commented:
Attached are today's logs from /var/log/samba.  Sorry it took so long to get them.  The PC having difficulty in attaching to a share point on the bawsvr Linux server is "jeffe" 192.168.0.20
log.smbd.txt
log.nmbd.txt
0
olehbCommented:
Looks like this BAW PC somehow differs from others as it provides user credentials during authentication phase:

[2008/02/07 11:19:21, 3]   check_ntlm_password:  Checking password for unmapped user [BAW]\[nobody]@[graphics] with the new password interface
[2008/02/07 11:19:21, 3]   check_ntlm_password:  mapped user is: [BAWSVR]\[nobody]@[graphics]
[2008/02/07 11:19:21, 3]   ntlm_password_check: NO NT password stored for user nobody.
[2008/02/07 11:19:21, 3]  ntlm_password_check: NEITHER LanMan nor NT password supplied for user nobody
[2008/02/07 11:19:21, 2] check_ntlm_password:  Authentication for user [nobody] -> [nobody] FAILED with error NT_STATUS_WRONG_PASSWORD

another PC's use windows "guest"  account :
[2008/02/07 11:19:21, 3]
  check_ntlm_password:  Checking password for unmapped user []\[]@[] with the new password interface
[2008/02/07 11:19:21, 3]
  check_ntlm_password:  mapped user is: []\[]@[]
[2008/02/07 11:19:21, 3]
  check_ntlm_password: guest authentication for user [] succeeded

What file "username map =" key points to? Considering username map = /etc/samba/smbusers, then check what users or groups are mapped there.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gmbrammerAuthor Commented:
Indirectly, your help with the details of the samba logs pointed me toward the answer.  This and other PC's were connected to the server via 802.11g wireless lan.  The PC I was having problems with connecting to samba showed a good connection at the PC, but when I checked the log at the access point (a DD-WRT based Linksys WRT54GS router), there were receive errors from the PC with samba connect problems.  Although you didn't give me the answer, your help lead me to the answer to a problem that was driving me crazy.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Software

From novice to tech pro — start learning today.