similar to: help with win2k and linux samba browsing

Hello all, I'm using a Windows machine, navalle, to copy files to my Linux box, lucifer, which will hopefully run Wine. I'm keeping a careful log of exactly how I install wine. This is what i've done so far: 1. Let ~ = lucifer:/home/p/.wine/fake_windows 2. apt-get install wine-doc winesetuptk wine-utils wine wine-lib: ii libwine 0.20011026.033 Windows Emulator (Library)

Given a DC environment where very few (1-3) hosts actually need to be discovered via browsing is there a good way to limit what is browseable? I'm thinking of something like a read-only WINS - where WINS provides only those servers that need be contacted and doesn't allow client registrations. Such as a wins.dat that only contains the following: ========================================

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 all, I have two servers ZEUS (MASTER - 192.168.2.11) and POSEIDON (SLAVE - 192.168.2.12) with HeartBeat+DRBD+SAMBA installed ; HeartBeat is controlling SAMBA. I have a big partition which are mirrored /share. I moved all important directory on it. For example: # mv /var/lib/samba /share/cluster/varlibsamba # mv /var/cache/samba /share/cluster/varcachesamba and I make a link for each one: # ln

PROBLEM: Cross-subnet browsing is not working. Browse lists on all machines contain only the machines on the local subnet. SUMMARY OF ANALYSIS: The Local Master Browser (LMB) running Windows XP (ZAYIN) never contacts the Domain Master Browser (DMB) running Samba (BETH) to initiate a synchronization of browse lists.

Hi there!! I 'm changing the distribution from Suse8 to Fedora Core3. I have installed a new PDC server with : fedora core3, openldap, samba, and smbtools (that was included in samba) All sw above mentioned were installed with fedora core3. Now, I have my server working but.. I can't add a new machine (wXP) to this domain server. All my configuration are ok (samba+smbtools+openldap),

Hi all, root@terra:/var/log/samba# nmblookup -S PDC querying PDC on 10.0.0.255 10.0.0.4 PDC<00> Looking up status of 10.0.0.4 PDC <00> - H <ACTIVE> root@terra:/var/log/samba# nmblookup -S testefinal querying testefinal on 10.0.0.255 10.0.0.100 testefinal<00> Looking up status of 10.0.0.100 TESTEFINAL

Hello everybody, i'm just setting up a samba server as pdc with ldap backend. everything but netbios works fine. The system is called aadmt00 and is a pdc (virtual) and is bound to the ip 192.168.53.180 hgest3201:~ # ip addr list 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255

Hi Peris, > some years ago i configured a `Primary Domain Controller` through > Samba and LDAP (slapd) on an Ubuntu machine (13.10) at 192.168.69.203 > which should be accessible by the string/name `SRV1`. I must note i > did not installed winbind. I've never had any issue and it looks like > it's working fine as about 10 Windows machines joined the PDC and > Windows

Hi, i've tried adding server max protocol = NT1 into /etc/samba/smb.conf and restarting smbd and nmbd services but it didn't do the trick. I feel like Windows clients are not able to resolve SRV1 into the PDC and so they can't event try to join the domain. On Fri, May 20, 2016 at 4:22 PM, Pau Peris <pau at webeloping.es> wrote: > Hi, > > thanks a lot for the tips. I

Hi all, I'm using Samba 3.0.7, OpenLDAP 2.2.17, smbldap-tools-0.8.5 It has been configured pdc with tls. tls work fine: ldapsearch -x -ZZ -h ldap.domain.com.br -D cn=suport,dc=domain,dc=com,dc=br -L -W ... ... # numResponses: 20 # numEntries: 19 my user has been found and accept password in the ldap root@terra:~# id fernando.ribeiro uid=1000(fernando.ribeiro)

I'm completely lost as i can ping SRV1 without issues but i'm starting to think that maybe Windows tries to join the domain through IPV6. ping -c6 SRV1 from this Windows 10 machine leads to host not found so i'm working on this direction right now. Any help will be really appreciated On Fri, May 20, 2016 at 5:04 PM, Gaiseric Vandal <gaiseric.vandal at gmail.com> wrote: > I

Right now i'm out of the office and i have no way to remotely work with the Windows machines so i've been upgrading the server to Ubuntu 16.04. Everything seems to be working as before but i'm wondering why right now the Master value is blank for Workgroup exedra.cat Any idea? # smbclient -L localhost WARNING: The "syslog" option is deprecated Enter root's password:

Are you running a wins server (maybe you already mentioned this.) That tends to help minimize some classic samba issues. On my PDC root at mypdc:~# testparm -v | more Load smb config files from /etc/samba/smb.conf rlimit_max: increasing rlimit_max (256) to minimum Windows limit (16384) Processing section "[netlogon]" WARNING: The

Hi, We have been using Samba 2.0.7 for a couple of years on Solaris 7. I am trying to move to a Samba 2.2.2 NT domain, with a Samba PDC offering WINS. I have downloaded the Solaris 7 package for 2.2.2 and installed it on a test machine as a domain master for domain "TEST" and "wins support = yes", but I am stumped almost immediately with a browsing problem. My new server

Colleagues- I'm experiencing a very odd problem that seems to be the root of some cross-subnet domain logon / browsing problems I am experiencing. Basically, I have a Samba 3.0.8 box acting as a PDC and WINS server for an NT style domain that is primarily on one subnet, but has a few users on others. On subnets other than the one the server resides on, domain logons fail sporadically.

Hi, thanks a lot for the tips. I already did the first one, importing the following into the registry: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters] "DomainCompatibilityMode"=dword:00000001 "DNSNameResolutionRequired"=dword:00000000 I didn't do the second tip but it looks like it's not

Hi all, some years ago i configured a `Primary Domain Controller` through Samba and LDAP (slapd) on an Ubuntu machine (13.10) at 192.168.69.203 which should be accessible by the string/name `SRV1`. I must note i did not installed winbind. I've never had any issue and it looks like it's working fine as about 10 Windows machines joined the PDC and Windows users can login against PDC on

I was trying to fix a problem on Windows 10 with Outlook 2013. Also running an NT4-style domain. The machine had already been joined to the domain and outlook had been working but recently not (probably after patch tuesday.) I also had had problems with Win 10 mail and RDP. I came across the following link.

You should be able to unbind ipv6 for the win 10 machine's network interface. does "nslookup SRV1" work? Also, you may want to try running tcpdump or ethereal or wireshark on our PDC and see what traffic is captres. On 05/20/16 13:24, Pau Peris wrote: > I'm completely lost as i can ping SRV1 without issues but i'm starting > to think that maybe Windows tries to