similar to: Additional info on loopback, UDP, session request failed

Hello samba@lists.samba.org ----- Original message ----- When i am first run samba from script ("-D" param) log looks like this: [2001/11/12 13:46:42, 3] lib/util_sock.c:open_socket_in(878) bind succeeded on port 139 [2001/11/12 13:46:42, 2] smbd/server.c:open_sockets(181) waiting for a

Machine Arch: x86 (Pentium) Machine OS: FreeBSD OS Version: 5.2.1 Kernel: FreeBSD 5.2.1 generic (unaltered binary) Compiler: gcc 3.3.3 Libc Version: (Default libc for FreeBSD 5.2.1) Samba Version: 2.2.8a Network Layout (description): Simple 8-machine 100 mbit ethernet LAN with Windows clients and one FreeBSD machine hosting Samba shares on a simple workgroup. What else is on machine (services,

Hi, I?m running SuSE 6.1 with a 2.2.5 Kernel on a PentiumPro machine. If I use the standard SuSE Kernel, Samba functions without any problems. If I make a new one I get following error: [1999/05/14 11:57:01, 0] smbd/oplock.c:open_oplock_ipc(80) open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested address Wich part off the kernel swichted I off

I get the following errors in the smb.log file. If anyone has any ideas about this please let me know. [2001/05/01 09:51:46, 0] lib/util_sock.c:set_socket_options(154) Failed to set socket option TCP_NODELAY (Error Connection reset by peer) [2001/05/01 09:51:46, 0] lib/util_sock.c:open_socket_in(827) Get_Hostbyname: Unknown host [2001/05/01 09:51:46, 0] smbd/oplock.c:open_oplock_ipc(93)

Hi, i've got this problem with my jail and i'm abolutly lost as in the why of it. I previously posted this on comp.unix.bsd.freebsd.misc but i was advised to send here I was unable to find help on google :( To resume quick, when i'm in a jail, netstat doesn't work properly. Hopefully i have provided sufficient information for anyone willing to help me :p First of all, my system :

I just made one of my 4.x remote servers inaccessible and just tested it on my 5.x laptop, and it does the same thing ... not sure if this is considered a 'desirable' effect, or a but ... but ... 'ifconfig <device> -alias' will wipe out all IPs on the device: mobile# ifconfig -a lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask

Hello, My computer is not connecting to the local network with the following configuration: dmesg.boot contains the following lines: ----------------------------------------- vr0: <VIA VT3043 Rhine I 10/100BaseTX> port 0xec00-0xec7f mem 0xfeafbc00-0xfeafbc7f irq 11 at device 12.0 on pci2 vr0: Ethernet address: 00:40:05:a5:00:04 miibus0: <MII bus> on vr0 amphy0: <Am79C873 10/100

Hello all, After upgrading to 3.0.23c on my FreeBSD 6.1 box Samba stopped working on any connections. When connecting to smbd, tcp session is established (SYN, SYN+ACK, ACK) then a client send a NEGOTIATION packet, and after some timeout (about 10-15 seconds) this tcp session is closed (by the client) because no response to NEG. packet was received. Then after 75 seconds (counting from the

I'm not really sure if this is a samba problem or a linux network problem, I have checked the newsgroups and ive seen this question pop up a few times, w/o answer. Here is the issure I am having, whenever the i do a smbclient -L hostname for this particular server I get the following message in the logs: open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot

I recently reconfigured a box running FreeBSD 5.3 with Samba v. 3.0.7 running as PDC. It was servicing 2 networks, processing logons for 192.168.200.0/24 and 192.168.115.0/24. The reason for 2 networks was security, 115.0/24 had some stuff on it that the users on 200.0/24 shouldn't have access to. Before the reconfiguration, the system was working 100%. To make everything better I flattened

Hi, in the kernel I have these lines: [...] device miibus # MII bus support device rl device ed options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_VERBOSE_LIMIT=0 #limit verbosity options IPDIVERT #divert sockets options DUMMYNET

Hello Samba folks, I thought you might be able to help me. I have 2 machines, 1 is FreeBSD, 1 is win95. They can't ping each other, but the bsd box comes up in Network Nieghborhood when Samba is active. What's going on? Is it not possible to ping a windows machine from a unix box? They are on the same hub via UTP. IPs are 192.168.1.x and netmasks are same (255.255.255.0).

Hello, I have installed samba 2.2.2 from the ports collection in FreeBSD. It dumps core whenever someone tries to use the nmbd server. I can connect OK if I do smbclient //10.25.165.3 -U user but not by doing smbclient //server -U user Here's the relevant part of the samba logfile: [2001/12/21 14:23:20, 2] lib/interface.c:add_interface(85) added interface ip=127.0.0.1

Hi, I am new to DTrace. Want to capture (for specific port #s) the loopback interface (lo0) tcp message flow with the complete message body. Is this possible with DTrace? Are any examples available? Thanks, Joe ____________________________________________________________________________________ Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.

I am running samba2.2.3a6 on my RedHat7.3 computer. Whenever I try to access it from my Windows 2000 computer, it says "Network path not found" and the log.smb reports: [2002/07/06 18:15:02, 0] smbd/oplock.c:init_oplocks(1189) open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested address Have any ideas on how to fix this? Greg

i am not sure whether this is by default or not, but i think i found a tiny bug. (maybe by design, i am not a samba guru) Steps to reproduce: Create a loopback device without asigning an ip to it. (not sure whether it is also reproducable without the loopback device at all) set in smb.conf: bind interfaces only = yes interfaces = yourip According to what i could find in the docs it should now

Hi there. This is with regards to samba-3.0.23c, on FreeBSD 6.0-RELEASE-p12 Previously I had Samba up and running without any problems. Then I decided to do a tiny upgrade by simply switching to a new motherboard, while keeping all other hardware and software aspects the same. However, after the upgrade, netbios name resolution seems to have stopped working somehow. \\servername lookups no

I tried to get Samba running on my new Trustix installation all day yesterday with no luck. I'm a newbie, so there's a lot I don't know yet. At any rate, I have the Smb, nmbd, and smbd services running. I've got my smb.conf file set up properly from what I can tell. When I try the following command on my Linux box: smbclient //192.168.1.102/backup -U jesse I get the error,

Are you sure you're running dhclient prior to starting the samba daemons? ------------------------ "Zuccarelli, Pablo" <Pabloz@argentina.strykercorp.com> wrote: ------------------------ Hi list. > > Im trying to configure a fileserver in a linux RH 8.0 client machine >that gets IP configuration from a NT4 DHCP server. Running just >dhclient, I >get an IP

Couple of little things I noticed with a new RELENG_7 AMD64 box (as of yesterday) ifstat from the ports cannot seem to find interfaces for some reason ? It works fine on i386 [ns8]# ifstat -b ifstat: no interfaces to monitor! [ns8]# [ns8]# ifconfig em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500