From owner-freebsd-questions@freebsd.org Tue Mar 13 21:05:45 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91A3EF50710 for ; Tue, 13 Mar 2018 21:05:45 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (ns.dreamchaser.org [66.109.141.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nightmare.dreamchaser.org", Issuer "nightmare.dreamchaser.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0EE0675D86 for ; Tue, 13 Mar 2018 21:05:44 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from breakaway.dreamchaser.org (breakaway [192.168.151.122]) by nightmare.dreamchaser.org (8.15.2/8.15.2) with ESMTP id w2DKqnEJ017717 for ; Tue, 13 Mar 2018 14:52:49 -0600 (MDT) (envelope-from freebsd@dreamchaser.org) From: Gary Aitken Subject: ARP issue, samba standalone connection problem Reply-To: FreeBSD Mailing List To: FreeBSD Mailing List Message-ID: <9caad981-4fe2-cc9d-da53-2193cbed5cf6@dreamchaser.org> Date: Tue, 13 Mar 2018 14:52:07 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2018 21:05:45 -0000 Trying to set up samba for the first time (4.7), local file sharing only. I have the server set up and can connect / log-on locally using smbclient. However, I can't connect from a win7 system; with log level set to 2 nothing shows up in /var/log/samba4/log.smbd Snooping packets, all I see is: (122 is fbsd samba machine; 123 is win7) ARP, Request who-has 192.168.151.122 tell 192.168.151.123, length 46 IP 192.168.151.123.50031 > 192.168.151.122.80: Flags [S], seq 2200471361, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0 IP 192.168.151.122.80 > 192.168.151.123.50031: Flags [R.], seq 0, ack 2200471362, win 0, length 0 IP 192.168.151.123.50031 > 192.168.151.122.80: Flags [S], seq 2200471361, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0 IP 192.168.151.122.80 > 192.168.151.123.50031: Flags [R.], seq 0, ack 1, win 0, length 0 IP 192.168.151.123.50031 > 192.168.151.122.80: Flags [S], seq 2200471361, win 8192, options [mss 1460,nop,nop,sackOK], length 0 IP 192.168.151.122.80 > 192.168.151.123.50031: Flags [R.], seq 0, ack 1, win 0, length 0 ARP, Request who-has 192.168.151.112 tell 192.168.151.123, length 46 Questions: Why isn't the fbsd machine replying to the ARP requests? Any idea why the win7 machine is hitting port 80? Why is port 80 on the fbsd system replying instead of simply dropping the packet? (there's no httpd running) pings work both ways. Thanks for any insights, Gary