[plug] samba connection problems

Sun Feb 16 03:27:01 WST 2003

----- Original Message -----
From: Quintin Lette <quintin at arach.net.au>
Date: Sun, 16 Feb 2003 01:03:57 +0800
To: plug at plug.linux.org.au
Subject: Re: [plug] samba connection problems

> ok try adding the following line to you /etc/samba/smb.conf file in the global 
> section (probably next to, near the hosts allow line if that doesn't work 
> comment out (#) the hosts allow line)
> 
> interfaces = 127.0.0.1/8 192.168.0.3/24

no joy :-(

> 
> if that doesn't work, try emailing me (probably better off list) your samba 
> log file.  /var/log/samba/xpmachine.log

see below from a copy of a recent newsgroup post.

> 
> I am assuming ofcourse you can ping the Linux box from xp

yes, that's never been a problem

, and that you have 
> added the appropriate groups.(sambausers) on the boxes

On the linux box, yes.  I'm a member of that group, which I set up before this whole process started.

I have a gateway/firewall box on 192.168.0.1, an old e-smith server running samba just fine on 192.168.0.2, and then this new server on 192.168.0.3, with the XP box on 192.168.0.101

Here's a post I recently made to a linux newsgroup where a member was asking me a series of questions in an attempt to assist me:
-----------------------------------------------

>>iptables has caused me grief in the past when trying to >>setup samba. Can you confirm it's off ?
>>
>>iptables -L -n ?

# /etc/rc.d/init.d/iptables stop
Flushing all chains:                                       [  OK  ]
Removing user defined chains:                              [  OK  ]
Resetting built-in chains to the default ACCEPT policy:    [  OK  ]

>>The samba log files are generally very helpful too, the >>should give you some clues about where the process is >>breaking down, whether it's actually getting any packets >>or usernames are getting mangled or passwords cannot be >>found or something else..

I've included parts or whole log files below (I hope these are the one's you're referring to).

>>Try running 'tcpdump' on the linux while trying to connect >>to see if it can actually see the traffic coming from the >>other box ?

# /usr/sbin/tcpdump
tcpdump: listening on eth0
00:08:10.492699 192.168.0.101.netbios-ns > 192.168.0.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
00:08:10.505314 192.168.0.3.32769 > gatie.domain:  53258+ PTR? 101.0.168.192.in-addr.arpa. (44) (DF)
00:08:10.505874 gatie.domain > 192.168.0.3.32769:  53258*- 0/0/0 (44)
00:08:10.506790 192.168.0.3.32769 > gatie.domain:  53259+ PTR? 3.0.168.192.in-addr.arpa. (42) (DF)
00:08:10.507100 gatie.domain > 192.168.0.3.32769:  53259*- 0/0/0 (42)
00:08:10.511659 192.168.0.3.32769 > gatie.domain:  53260+ PTR? 1.0.168.192.in-addr.arpa. (42) (DF)
00:08:10.511985 gatie.domain > 192.168.0.3.32769:  53260- 1/0/0 PTR[|domain]
00:08:11.228960 192.168.0.101.netbios-ns > 192.168.0.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
00:08:11.979132 192.168.0.101.netbios-ns > 192.168.0.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
00:08:15.498689 arp who-has 192.168.0.3 tell gatie
00:08:15.498717 arp reply 192.168.0.3 is-at 0:40:95:30:7c:14

Okay...gatie is my firewall/router...have I missed something very basic here?  Server2 (the computer I'm trying to get samba working on) is 192.168.0.3, and the xp boz that's sending the netbios message is on 192.168.0.101. I'm not sure how to make use of this data from the tcpdump any further, though.

>>Try mapping directly to a share via the command line :
>>
>>net use q: \\server2\linux * /user:username ( the asterisk >>forces it to prompt for password )

The result of this, after entering the correct password, was:

System error 53 has occurred.

The network path was not found.

>>What's appearing in the log files ?

in log.smbd this is all that appears, only the dates and times change across the repeated entries of these lines:

[2003/02/16 00:02:05, 0] smbd/server.c:main(707)
  smbd version 2.2.7 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2002

for log.nmbd, here are the most recent entries:

[2003/02/16 00:02:05, 0] nmbd/nmbd.c:main(794)
  Netbios nameserver version 2.2.7 started.
  Copyright Andrew Tridgell and the Samba Team 1994-2002
[2003/02/16 00:02:09, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235)
  find_response_record: response packet id 24931 received with no matching record.
[2003/02/16 00:02:09, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235)
  find_response_record: response packet id 24932 received with no matching record.

for the smbd.log file:

[2003/02/15 04:02:03, 0] smbd/server.c:open_sockets(238)
  Got SIGHUP

is all that appears, similar to the nmbd.log file:

[2003/02/15 04:07:04, 0] nmbd/nmbd.c:terminate(59)
  Got SIGTERM: going down...

Here's the contents of server2.log.1, which are a bit more interesting (maybe):

[2003/02/15 03:11:38, 0] printing/pcap.c:pcap_printername_ok(260)
  Attempt to locate null printername! Internal error?
[2003/02/15 03:11:38, 0] smbd/service.c:make_connection(252)
  server2 (127.0.0.1) couldn't find service

>>What's the contents of /etc/samba/smbpasswd ?

Is that safe to post here?  I've made sure to set the password using the smbpasswd command, and the username does appear in that file (along with all the other names from the regular passwd file, except in smbpasswd there are a lot of xxxx after them all, except my username, which has a string of letters and numbers after it).

Thanks,

Ari
------------------------------------------

-- 
_______________________________________________
http://www.operamail.com
Now with OperaMail Premium for only US$29.99/yr

Powered by Outblaze