similar to: Automatically inferring %d on multi-domain virtual install ?

On Fri, Feb 19, 2016 at 08:41:15AM +0100, Steffen Kaiser wrote: > >I'm trying to allow domain-less logins for a multi-domain virtual IMAP > >server, and wondering if I can automatically infer the domain (value of > >variable %d) from the local IP (%l) or the hostname used by the client > >when connecting to my server. > > > >Let's say I have two host

very intrigued by your solution Timo, have attempted something similar in the past to no avail. When I tried I was unable to retain the user at domain when setting the domain as extra field - protected is new to me and can't find documentation - but also doesn't work :( # cat passwd.domains 10.100.1.1:::::::domain:protected=foo.org 10.100.1.2:::::::domain:protected=bar.org # cat

Hey, I have slow access when I first open shares. If I reboot my XP box and then go to access a share, it takes a good 10 seconds for files to come up, even after I've typed in my username and password. Once accessed it runs fine and is fast. But, if I don't access it for 30 minutes, when I access it again it sits for like 10 good seconds before it does anything. This is very annoying.

Hi, I have a samba server sharing some stuff. Now i want to enable access to some share only to SOME users on the domain. this is the smb.conf : [global] netbios name = DATASVR server string = DATASVR socket options = TCP_NODELAY SO_RCVBUF=16384 SO_SNDBUF=16384 idmap uid = 10000-20000 idmap gid = 10000-20000 winbind enum users = yes

FreeBSD psg.com 11.3-RELEASE-p3 FreeBSD 11.3-RELEASE-p3 dovecot 2.3.6 (7eab80676) (latest from binary package system) symptom: multiple imap4s users complain that they can not fetch mail stopping and restarting dovecot is a temporary workaround dovenull 3713 0.0 0.0 11036 6816 - I 02:27 0:00.17 dovecot/imap-login user19 3714 0.0 0.0 9464 4756 - S 02:27

Hi Folks, I am a Samba newbie and needed some assistance with my configuration. I am trying to run Samba 2.2.2 (on Solaris 8 Intel Version) downloaded from Sunfreeware.com and have a Windows 2000 Professional box. I believed I followed the directions in SAMBA-How-To carefully but cannot get connection from a DOS prompt. When I run the command below from my UNIX box, here is what I get: The

Hi, Guus I did some test regarding the points you mentioned below, and yes, you’re right, but some of points may need further adjusted: 1. The destination of IPv4 wouldn’t be changed, Yes I agree, that’s the goal and final destination for the communication. But during the path, it may be encapsulated into another packet(tunnel mode), where the outside IP header is the physical address, but the

Hello list, I've upgraded from Samba 3.0.14a to 3.0.27a (Samba is a domain member of a W2k3 native AD) and I see that in the /var/lib/samba/smb_krb5 directory a krb5.conf file is created. Is this krb5.conf file extracted from my original /etc/krb5.conf? Or is this file created from the "password server =" entry in my smb.conf file? My original /etc/krb5.conf contains the DC's in

Thanks very much! It's alive! For others who are having problems, this is a summary of the differences I needed between Linux and OS X: You'll need to install http://tuntaposx.sourceforge.net/ manually. On tinc.conf: > Linux Name = ntwigg2014linux AddressFamily = ipv4 Interface = dpsfVPN ConnectTo = dpserver001 > Mac Same, but remove the Interface line entirely On tinc-up: >

I'm stumped. We have a CentOS 4.4 box with something like the following IPs: eth0: 64.61.61.100 eth0:0 64.61.61.112 eth1: 10.0.0.100 lo: 127.0.0.1 (of course) We want requests to 64.61.61.112:80 to be NAT'ed to 127.0.0.1:8080. This seems like it should be really simple -- maybe the following? -- I've tried variants combining this rule with a POSTROUTING rule, tried dnat,

Hello For testing purposes, i would like to make a connection between 2 network interfaces on the same machine. For example, i have eth0 (10.0.0.100) and eth1 (10.0.0.101) and would like to have the traffic going on the "wire", not just taking the "shortcut" inside the protocol stack. I have played around a little bit with the routing table, but did not succeed. Does

>> Hello, >> >> I am using Debian Sarge, with Shorewall 2.2.3, >> >> for access control I am using hosts.allow : >> >> ALL: 144.131.xxx.xxx >> >> and hosts.deny: >> >> ALL: ALL >> >> I have a virtual machine that is being port forwarded to with Shorewall : >> >> DNAT net loc:10.0.0.100 tcp 3389

Hello PXE folk, I mentioned in another thread that I had problems finding an etherboot that actually works with a 486 and Realtek 8019/NE2000 card. Etherboot worked up until v 5.3.5-mc1 with the ne driver but then stopped working between 5.3.7 to 5.3.13 (anoying since 5.3.7 started supporting PXELINUX. But then I downloaded 5.3.14 and it seems to work again with the ne driver (finally

> > Have you tried 5.10 in your environment on a BIOS machine to see whether > that works and which port numbers it uses? > > -- > Matt Fleming, Intel Open Source Technology Center > Hi Matt, I think I've found the problem. In /core/fs/pxe/tftp.c in function tftp_open: First you do a core_udp_connect to port 69 (TFTP) at line 264. -> source port = x After that

Hi All, I'm trying to connect to a SIP carrier who never connected with Asterisk. I managed to connect with a sipura phone or a grandstream, no problem. When I configure asterisk, I'm able to send out calls to the carrier no problems, however, receiving calls doesn't work, and I keep getting the following messages: <-- SIP read from 69.xx.xx.xx:5060: INVITE

Hello all, I'm testing a home LAN server inside Virtualbox - figured it'd be easier to build (and fix) things inside a virtual sandbox first, and then migrate over to a physical install once I have most of the kinks worked out. The host OS is Windows Vista; the guest OS will be various Linux distributions for education/entertainment purposes. First, a little explanation on the

On Wed, 9 Mar 2005, Quinn wrote: > I have now also tried etherboot on a AMD Athlon machine with a 3Com 905B > NIC, etherboot 5.3.14 and pxelinux.0-3.08-pre5. Here is the results: > > Etherboot 5.3.14 (GPL) http://etherboot.org > Drivers: 3C90X Images: NBI ELF PXE Exports: PXE > Protocols: DHCP TFTP > Relocating _text from: [00010420,00022880) to [5feedba0,5ff00000) >

Hello, I tried to boot the new syslinux.efi (32bit) from the released syslinux 6 via PXE. In a wireshark trace I can see that the syslinux.efi was loaded successfully via TFTP. Then the client try to load ldlinux.e32. I see the request and also the acknoledgement in the trace. After that the client try to load the file, but the source port is changed to tftp request port + 1. For example:

Hi, I am trying to infer the dimension of an opened bitmap (png, jpeg, bitmap device...) from par() parmeters. From the help on par(), I found that: > dim <- c(400, 200) > png("foo.png", width=dim[1], height=dim[2]) > dim2 <- par("din") * par("cra") / par("cin") > dev.off() > dim2 [1] 399.9999 199.9999 I've tried the above on

On Tue, 25 Jun, at 01:51:52PM, Michael Szerencsits wrote: > Hi Matt, > > I think I've found the problem. Thanks for doing this analysis. > In /core/fs/pxe/tftp.c in function tftp_open: > First you do a core_udp_connect to port 69 (TFTP) at line 264. -> source port = x > After that you sent the filerequest at line 265 > You receive the fileinfo and also the used port