similar to: Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12

Displaying 20 results from an estimated 3000 matches similar to: "Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12"

2018 Oct 13
2
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
Hello Andrew, > Do you actually have any ethernet interfaces up? Why are you not > binding Samba to that? I do, but I run multiple samba servers on one machine. I have a few active directory controllers bound on a per VLAN basis to different interfaces. And one additional samba just for shares that should serve all VLANs. That is why I have the 10.10.10.1 on the lo interface. I use that
2018 Oct 13
2
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
Hello Rowland, > Stop me if I am wrong (and I often am), but doesn't the 'loopback' > device do exactly that ? Anything 'lo' receives on its input just gets > shoved out of its output, or to put it another way, it just goes > around in a circle, so how does this work with Samba etc ? Not saying > it will not work, trying to understand how it works if it does
2018 Oct 13
2
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
Hello everyone, when using samba 4.9.1 as a standalone filer, I need to start smbd and nmbd, don't I? I'm using: /local/samba/sbin/smbd -s /local/samba-config/common/smb.conf /local/samba/sbin/nmbd -s /local/samba-config/common/smb.conf However smbd. Seems to ignore my lock directory: (infra) [/local/samba-config/common] grep gencache_notrans.tdb log/smbd Opening cache file at
2018 Oct 13
2
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
Hallo Rowland, > How are you checking, what is the actual command you are using ? the problem was that the debian samba was listing on all interface even if I told him not to do so. So the new one never worked for me. I only thought it would but it was actually served by the old one. The current smbd seems to still choke on me not having winbind. Is there a way to disable winbind? Current
2018 Oct 13
2
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
Hello Rowland, > There are actually 4 Samba processes: > samba, only used on a DC and this starts any other required processes. > smbd, this is the cifs process > nmbd, the netbios browsing process > winbind, authentication process > The above is a rather simplistic view, but I hope you get the idea. > on a standalone server, you need the smbd process to be running and
2018 Oct 13
2
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
Hello Rowland, > cache directory = /local/samba-config/common/cache > lock directory = /local/samba-config/common/lock > log file = /local/samba-config/common/log/%m > pid directory = /local/samba-config/common/pid > private dir = /local/samba-config/common/private > state directory = /local/samba-config/common/state > You will
2018 Oct 13
0
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
On Sat, 13 Oct 2018 10:17:19 +0200 Thomas Glanzmann via samba <samba at lists.samba.org> wrote: > Hello Andrew, > > > Do you actually have any ethernet interfaces up? Why are you not > > binding Samba to that? > > I do, but I run multiple samba servers on one machine. I have a few > active directory controllers bound on a per VLAN basis to different >
2018 Oct 13
0
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
On Sat, 13 Oct 2018 10:43:31 +0200 Thomas Glanzmann via samba <samba at lists.samba.org> wrote: > Hello Rowland, > > > Stop me if I am wrong (and I often am), but doesn't the 'loopback' > > device do exactly that ? Anything 'lo' receives on its input just > > gets shoved out of its output, or to put it another way, it just > > goes around
2018 Oct 13
0
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
On Sat, 13 Oct 2018 16:14:44 +0200 Thomas Glanzmann <thomas at glanzmann.de> wrote: > Hello Rowland, > > > cache directory = /local/samba-config/common/cache > > lock directory = /local/samba-config/common/lock > > log file = /local/samba-config/common/log/%m > > pid directory = /local/samba-config/common/pid > >
2020 Sep 06
2
debian 10, vm cant connect to the host bridge
This is my system info: Debian Release: 10.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.60-1-pve (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh
2008 Sep 19
8
bridge + arp
Hi, this is propably bridge related and not really a xen problem, but it might help someone: Some of our domUs are not able to arp. Arp -n show (incomplete), and doing a tcpdump shows, that on the dom0''s eth0 the arp request goes out, the response comes in, but on the vifX.0 interface the arp response is gone. dom0# tcpdump -ni eth0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply
2020 Sep 22
4
nmcli: unwanted secondary ip-address
Dear CentOS-Community, we are facing the following issue: A secondary ip address seems to be automatically added to a nic which causes several issues in our setup. This server is equipped with four nics which are currently in use: # nmcli con show NAME????? UUID????????????????????????????????? TYPE????? DEVICE eno2????? cb6fcb54-be52-4ab6-8324-88091a0ea1a0? ethernet? eno2 eno4?????
2020 Sep 07
1
AW: debian 10, vm cant connect to the host bridge
someone recommended that i should give br0 the same hardware address as eno2. I did that, and restarted the vm, and it still does not work. Here is my current host interface config: ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft
2016 Aug 29
2
IAX UNREACHABLE : Ignoring bindport/bindaddr on reload
Hi, see the log below root at AsteriskSlave:~# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: p3p1: <BROADCAST,MULTICAST> mtu
2015 Mar 16
2
Re: still possible to use traditional bridge network setup ?
Laine wrote: > -----Original Message----- > From: sendmail [mailto:justsendmailnothingelse@gmail.com] On Behalf > Of Laine Stump > Sent: Monday, March 16, 2015 4:12 PM > To: libvirt-users@redhat.com > Cc: Lentes, Bernd > Subject: Re: [libvirt-users] still possible to use traditional bridge network > setup ? > > On 03/16/2015 10:08 AM, Lentes, Bernd wrote: > >
2017 Jul 19
6
Re: SSH from host to domain using hostname
18. Juli 2017 16:45, "Michal Privoznik" <mprivozn@redhat.com> schrieb: > On 07/18/2017 04:31 PM, c.monty@web.de wrote: > >> Hello! >> >> I have upgraded all libvirt packages to version 3.5.0-655.1 and restarted host. > > That wasn't necessary. It's not Windows ;-) > >> This is the current default network config: >> ld4004:~
2018 Dec 16
3
macvtap and tagged VLANs to the VM
Hi, I would like to run a network firewall as a VM on a KVM host. There are ~ 25 VLANs delivered to the KVM host on three dedicated links, no LACP or other things. I have the VLANs 100-180 on the host's enp1s0, the VLANs 200-280 on the host's enp2s0 and the VLANs 300-380 on the host's enp3s0. To save myself from configuring all VLANs on the KVM host, I'd like to hand the entire
2016 Aug 29
2
IAX UNREACHABLE : Ignoring bindport/bindaddr on reload
I just see warning? 2016-08-29 11:30 GMT-03:00, Telium Technical Support <support at telium.ca>: > This shows that asterisk's IAX is already bound to all adapters - so that's > good. Symptomatically does your IAX stop working? Or do you just see a > warning? > > -----Original Message----- > From: asterisk-users-bounces at lists.digium.com >
2020 Oct 21
1
about the new added attributes "check" and "type" for interface mac element
Hi all, I have done some tests for the new attributes "check" and "type", could you please help to have a check? And I have some questions about the patch, please help to have a look, Thank you! The questions: 1. in step 4 below, the error message should be updated: Actual results: XML error: invalid mac address **check** value: 'next'. Valid values are
2005 Apr 01
2
Problems using VMWare with a Bridged Firewall
Hi I am using Shorewall with a bridged Firewall using the "bridging utils" from Debian. eth0 is connected to the router and eth1 is connected to the local lan. eth0 and eth1 are both assigned zero addresses and br0 is assigned the Firewall server address of 192.168.0.1 I should point out that Shorewall is working fine in Bridge mode, but I have hit some problems while evaluating