asked on

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?

olehb

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?

gmbrammer

ASKER

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

gmbrammer

ASKER

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)

olehb

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?

olehb

Also you need to reload samba configuration using commands:
/etc/init.d/smb reload
/etc/init.d/nmb reload

gmbrammer

ASKER

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.

gmbrammer

ASKER

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

ASKER CERTIFIED SOLUTION

olehb

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

gmbrammer

ASKER

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.