similar to: Samba's NMBD dumps core with FreeBSD 4.4-STABLE

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, A quick note to my previous message. When I removed "max smbd processes" from my smb.conf file, the testparm error was no more. Another thing, although it says the status parameter is set to no, I can still use smbstatus as always. Sincerely, Mario Doria

Hi guys, I want to update and add some content to this page: http://wiki.centos.org/HowTos/PackageManagement/Spacewalk The page have instructions for Spacewalk 0.6, but there's a newer version (0.7) and some changes are needed. I already updated my spacewalk install and would like to contribute with the wiki page. More information about spacewalk can be found here:

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 finally got a 10G card that is recognized by FreeBSD (9.1-stable): ... ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.4.8> port 0xecc0-0xecdf mem 0xd9e80000-0xd9efffff,0xd9ff8000-0xd9ffbfff irq 40 at device 0.0 on pci4 ix0: Using MSIX interrupts with 9 vectors ix0: RX Descriptors exceed system mbuf max, using default instead! ix0: Ethernet address: 90:e2:ba:29:c0:54

Hello, I have given myself quite the headache trying to make this VPN work correctly. I am attempting to use racoon to establish keys and construct an encrypted tunnel between one host(A.A.A.A) with a routable IP address and another that has a private address(10.0.0.2) with a cable modem(B.B.B.B) forwarding all ports to the private address(10.0.0.2). Here is a quick topographic dipiction of the

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 have just checked the Openbsd box on the if interface. fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 address: 00:02:55:30:54:28 media: Ethernet autoselect (100baseTX full-duplex) status: active inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::202:55ff:fe30:5428%fxp0 prefixlen 64 scopeid 0x1 xl0:

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 list! When em0 has an inet address while bridge0 doesn't, it seems to be OK: ----- bs1% uname -a FreeBSD bs1.sp34.ru 7.0-STABLE FreeBSD 7.0-STABLE #0: Sun May 25 20:15:26 MSD 2008 root@bs1.sp34.ru:/usr/obj/usr/src/sys/BSM i386 bs1% ifconfig em0; ifconfig tap0; ifconfig bridge0 em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

Okay, I'm starting to get excited now because I think someone from the Samba lists has pushed me in the right direction here. To recap: I can't ping my win machine (192.168.1.2) from my FreeBSD box (192.168.1.3) and vice versa. Both subnet masks are 255.255.255.0 and ipfw is not running. I loaded the dos config program for the card on my BSD machine (by booting off DOS floppy

Hi *, I recently triggered an error when setting up a jail-host: I configured the jail(s) like evry jail I set up in the past: On the jail-hosts /etc/rc.conf: # ---- Jail-Globals ---- jail_enable="YES" # Set to NO to disable starting of any jails jail_list="ftp mx1 relay" # Space separated list of names of jails

Referring to my previous post about degradation of voice quality when having more than 2 connection. The actual route is: pc xlite -> local asterisk box -> iaxtel -> local asterisk I have tried out a different situation: pc xlite -> local asterisk box -> iaxtel and the second connection pc xlite -> local asterisk box -> iaxtel -> local asterisk The same degradation

Hello Try install FreeBSD 6.3-prerelease on Intel SBXD132 blade (same as IBM HS21 XM) ifconfig bce0 report: bce0: flags=8847<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=3b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU> inet 172.0.0.199 netmask 0xffffff00 broadcast 172.0.0.255 ether 00:1a:64:33:29:c7 media: Ethernet autoselect (none) status: no carrier We are looking

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

su-2.05a# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes ping: sendto: No route to host ping: sendto: No route to host ^C --- 192.168.1.1 ping statistics --- 2 packets transmitted, 0 packets received, 100% packet rl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6

Hi list, since we activated 10gbe on ixgbe cards + jumbo frames(9k) on 9.0 and now on 9.1 we recognize that after a random period of time, sometimes a week, sometimes only a day, the system doesn't send any packets out. The phenomenon is that you can't login via ssh, nfs and istgt is not operative. Yet you can login on the console and execute commands. A clean shutdown isn't possible

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

I have been playing around with 3 ath based FreeBSD boxes and seem to have got everything going via WPA and a common PSK for 802.11x auth. However, I want to have a bit more certainty about things working properly. What tools do people recommend for sniffing and checking a wireless network ? In terms of IDS, is there any way to see if people are trying to bruteforce the network ? I see

I'm experiencing similar problems with a 3C996-T under 4.8-REL. In particular, connecting a 4.8-REL machine to a 5.1-REL machine leads to some interesting situations: I can do simple pings across the link, but ssh fails, and heavy pings crash the 4.8 machine. Similarly changing the interface configuration with ifconfig tends to crash the 4.8 machine (mtu, link0, up/down, etc). The