search for: addrees

Hello, I have a problem. I set up a Samba4 AD with bind9 and isc-dhcp-server for dynamic DNS-updates. That works well. I put the Linux PCs in the domain and at the beginning they work fine but when the IP address changes by the DHCP, the DNS is updated well, but the users can not enter the domain. Any ideas? Regards.

Yes, I set up a Samba4 AD with bind9 and isc-dhcp-server for dynamic DNS-updates and works well. The problem is with the Linux Client and the domain when the IP addrees change (Linux Clients are in the domain). Is possible that the Client are registers with one IP address in the domain and when the IP address change beginning the problem. Siovel. ----- Original Message ----- From: "samba" <samba at lists.samba.org> To: "samba" <samba...

..._log . . . Superblock backups stored on blocks: 32768, 90304, 163840, 229376, 294912, 819200, 884736, 1605632 and ran: e2fsck -b 32768 /dev/mapper/vg_voinet01-lv_log The superblock could not be read or does not describe a correct ext2 The same thing happened for the next backup superblock addrees. And all the rest reported an invalid argument error from e2fsck. Is this recoverable? How? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mail...

Robin Lynn Frank wrote: > I have an entire /8 blacklisted. The problem is there is a single IP in > it I want to exempt from this. Searching the web site, I note there > used to be (circa version 1.3) a whitelist feature, but I couldn''t find > a simple solution to what I want to do. > > What would be the bes/easiest way to accomplish this? I can''t think of a

I have a couple of problems with Samba that I would appreciate help with: 1. Since installing version 1.9.17p1, error messages such as "ERROR: set_share_mode: failed to ftruncate share mode file /var/smb/locks/share.9175085.1500224 to size 42 (Permission denied)" are appearing in log.smb. 2. When a directory on a UNIX machine contains a file named *, this file appears with the name ~16

Is there a way to prevent other users from being able to map a drive from windoww95/NT to anyother user directory on the system. For example I can map to anyone's account on the system and have read only access, is there a way to stop this in either the global or share level? Thanks