similar to: Problem T.38

After updating From Dovecot 1.07 (included with CentOS 5) to 2.11, NTLM authentication will not work. Attempts to authenticate against Samba version 4.0.4-GIT-20cb7de also fail with 'auth: Info: winbind(?,192.168.2.100): user not authenticated: NT_STATUS_UNSUCCESSFUL', despite the fact that the same user can sign on to the Samba domain and access files. What I'm really trying to

> - Indirectdata finally REALLY REALLY works now! > - More precise debug messages Hmmm ... I can't prove that using the CVS code I checked out this morning. Everything works like yesterday: I can ping the peer but I canot go beyond: *** SERVER *** Jun 27 09:04:56 lemon tinc.9[10186]: tincd 1.0pre3 (Jun 27 2000 08:53:56) startin g, debug level 4 Jun 27 09:04:56 lemon tinc.9[10186]:

https://bugzilla.netfilter.org/show_bug.cgi?id=870 Summary: Iptables cannot block outbound packets sent by Nessus Product: iptables Version: 1.4.x Platform: x86_64 OS/Version: Ubuntu Status: NEW Severity: normal Priority: P5 Component: iptables AssignedTo: netfilter-buglog at lists.netfilter.org

I'm having an issue I can't seem to work around after upgrading from Dovecot 1.0.7 to 1.2.17. After getting Dovecot 1.07 working on CentOS 5.9, I decided that it might be wise to upgrade to a later version, so I stuck with 1.x and went with 1.2.17, which I had to compile from source. CentOS was originally using /etc as the starting path for Dovecot files but the source distribution puts

hi, I cant ssh into my domU from the Dom0 even if i type the correct password. The ip of my domU is 192.168.2.100, and from my dom0 i type: #ssh root@192.168.2.100 The authenticity of host ''192.168.2.100 (192.168.2.100)'' can''t be established. RSA key fingerprint is 25:91:2c:63:6d:fc:ba:28:b8:54:2c:14:b1:c5:e5:cf. Are you sure you want to continue connecting (yes/no)?

https://bugzilla.netfilter.org/show_bug.cgi?id=1720 Bug ID: 1720 Summary: Time-zone bug in hour-of-day parsing or display Product: nftables Version: 1.0.x Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: nft Assignee: pablo at netfilter.org

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal I cannot find a use the network-nat and vif-nat provided in the general case, where I'd like to NAT between vifx.0 and ethx interfaces. I have setup the following in /etc/xen/xend-config.sxp : ## Use the following if network traffic is routed with NAT, as an alternative # to the settings for bridged networking given above.

https://bugzilla.netfilter.org/show_bug.cgi?id=1317 Bug ID: 1317 Summary: ulogd missed flow.start.sec and flow.start.usec fields Product: ulogd Version: 2.0.0beta1 Hardware: All OS: Debian GNU/Linux Status: NEW Severity: major Priority: P5 Component: ulogd Assignee:

hello, when I use rsync from commandline (RH 7.2, ssh2), it works fine. rsync -e ssh -a -v zaloha@192.168.2.100:/home/samba/m/aaa.txt /home/m/aaa.txt but when I try to use it in crontab such as 33 11 * * * rsync -e ssh -a -v zaloha@192.168.2.100:/home/samba/m/aaa.txt /home/m/aaa.txt </dev/null or 33 11 * * * rsync -e ssh -a -v zaloha@192.168.2.100:/home/samba/m/aaa.txt /home/m/aaa.txt

Package: xen-utils-common Followup-For: Bug #430778 Here's a patch I made to have working rules here... feel free to comment/adapt. Hope this helps -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-xen-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8,

On 1/26/2016 5:37 AM, lejeczek wrote: > > I'm having a, I'd like to think a "regular" VPN with IPsec/xl2tpd and > it all works OK, except.. > One thing that I never needed but now I do and I wonder.... is it my > iptables, or/and routing or maybe VPN server config..? > > vpn clients with established tunnels can get to VPN server's NICs/IPs > but

On 26/01/16 16:26, John R Pierce wrote: > On 1/26/2016 5:37 AM, lejeczek wrote: >> >> I'm having a, I'd like to think a "regular" VPN with >> IPsec/xl2tpd and it all works OK, except.. >> One thing that I never needed but now I do and I >> wonder.... is it my iptables, or/and routing or maybe VPN >> server config..? >> >> vpn

Hello, do you know about that kind of problem: I've tried to connect an apple macintosh os x (10.2.4) to my linux samba-server (take a look to my smb.conf in the attachement), but i've only got a connection to my homedirectory. If I tried to connect to my other shares, i got only the error message 5023. Do you may know that problem???? It would be very nice to here from you..

I have the following problem, and I would l like to know if Samba can help. (I suspect that it cannot, but feel free to prove me wrong.) My scenario is this: My site is just one of many, with the `Domain Master Browser` being off-site. My site has 10 VLANS, and in the current, purely Windows environment I have assorted problems with the browser list being maintained across all 10 VLANS. I would

Hi, I was wondering if anyone had a good dhcpd.conf and /tftpboot files for a EPIA-M motherboard with RedHat 9.0.... Or maybe just a configuration that works with the EPIA-M (doesn't matter which type of linux). I'm trying to boot the system from the network and it seems to be getting to downloading pxelinux.0 but then nothing happens after that.... I'm using ISC dhcpd V3.0pl2,

hi everybody I'm having a, I'd like to think a "regular" VPN with IPsec/xl2tpd and it all works OK, except.. One thing that I never needed but now I do and I wonder.... is it my iptables, or/and routing or maybe VPN server config..? vpn clients with established tunnels can get to VPN server's NICs/IPs but cannot get through to the net behind the server. Well... they can,

Hello, I have some questions regarding the proper tinc configuration to allow IP-broadcasting, IPX etc. aka the complete gaming setup. I searched the net and did not find a working (or well enough documented) solution for my needs. Let me describe what I want and what I tried so far and what worked or failed. I want to use the following setup with three machines (all with the same tinc

On 01/26/2016 05:37 AM, lejeczek wrote: > vpn clients with established tunnels can get to VPN server's NICs/IPs > but cannot get through to the net behind the server. > Well... they can, but only if on a host (eg. 192.168.2.33) on VPN > server's net I do: > > route add -host 192.168.2.10 gw 192.168.2.100 # 192.168.2.10 is VPN > client If the VPN isn't

On 1/26/2016 9:14 AM, Gordon Messmer wrote: > On 01/26/2016 05:37 AM, lejeczek wrote: >> vpn clients with established tunnels can get to VPN server's NICs/IPs >> but cannot get through to the net behind the server. >> Well... they can, but only if on a host (eg. 192.168.2.33) on VPN >> server's net I do: >> >> route add -host 192.168.2.10 gw

I have two interfaces on a centos machine with IPs 192.168.2.15 and 192.168.3.15. The routing table is: # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.3.0 * 255.255.255.0 U 0 0 0 eth1 192.168.2.0 * 255.255.255.0 U 0 0 0 eth0 169.254.0.0 *