From owner-freebsd-questions Sun Nov 29 13:31:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06261 for freebsd-questions-outgoing; Sun, 29 Nov 1998 13:31:59 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06236 for ; Sun, 29 Nov 1998 13:31:56 -0800 (PST) (envelope-from Stanley.Hopcroft@ipaustralia.gov.au) From: Stanley.Hopcroft@ipaustralia.gov.au Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.1/8.9.1) id IAA18629 for ; Mon, 30 Nov 1998 08:31:44 +1100 (EST) X-Authentication-Warning: pericles.IPAustralia.gov.au: smap set sender to using -f Received: from noteshub01.aipo.gov.au(10.0.100.21) by pericles.IPAustralia.gov.au via smap (V2.0) id xma018627; Mon, 30 Nov 98 08:31:40 +1100 Received: by noteshub01.aipo.gov.au(Lotus SMTP MTA v4.6.2 (693.3 8-11-1998)) id 4A2566CB.007BCC8D ; Mon, 30 Nov 1998 08:32:12 +1000 X-Lotus-FromDomain: IP_AUSTRALIA To: questions@FreeBSD.ORG Message-ID: <4A2566CB.007BCC33.00@noteshub01.aipo.gov.au> Date: Mon, 30 Nov 1998 08:31:25 +1000 Subject: Samba: Your server software is being unfriendly Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Ladies and Gentlemen, I am writing to share my experience with this samba error on FreeBSD 2.2.7-STABLE Session request failed (0,0) with myname=TSITC2 destname=TSITC Unspecified error 0x0 Your server software is being unfriendly When the server is running in debug mode (-d3 or more) it logs 1998/11/28 11:43:51 changed root to / open_oplock_ipc: opening loopback UDP socket. open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was C an't assign requested address This message is generated by server.c when it trys to oplock_sock = open_socket_in(SOCK_DGRAM, 0, 0, htonl(INADDR_LOOPBACK)); if (oplock_sock == -1) { DEBUG(0,("open_oplock_ipc: Failed to get local UDP socket for \ address %x. Error was %s\n", htonl(INADDR_LOOPBACK), strerror(errno))); oplock_port = 0; return(False); which calls 'bind' in util.c if (bind(res, (struct sockaddr * ) &sock,sizeof(sock)) < 0) The samba documentation docs/DIAGNOSIS.txt suggests that this is a nameserver problem and to check resolv.conf, DNS configuration etc. In this case the DNS was resolving both 127.0.0.1 (aka 1000007f) and the servers name and IP addresscorrectly. Here, as is so often the case, rigourous adherence to first level problem determination (what has been changed ?) would have helped rather than fruitlessly pursuing the DNS stuff (change DNS, change to hosts etc). The server had been changed to a new Catalyst 2900 switch and the Intel PRO FX card had failed to work properly at 100 Mbps (characters typed to a telnet session would take up to 10 seconds to echo; responses from the remote host were also delayed) so its media type had been changed to 10baseT/UTP. In the process, the ifconfig for lo0 interface had been accidentally commented out, so it had no IP Address. Restoring 127.0.0.1 to lo0 fixed it up. Thank you, Yours sincerely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message