[Samba] Pruning embedded samba 3.6 installation
I'm using the Yocto Project to build an embedded distro, to which I'm adding Samba 3.6 from OpenEmbedded. Doing so increases my root file system from about 63MB to 175MB. I seem to be building a large Samba server with a small ancillary operating system tacked onto it. I listed the files in my file system image, and see that lots of the commands are quite large. I understand that Samba 4 is better behaved in this way, but writing my own bitbake recipe to include such a large complex system is waaay beyond me, so I have to wait until someone else does it. I can, however, figure out how to prune various unneeded files from the image to make it smaller. But what's unneeded? I'd like to know what commands will NEVER be used if I don't explicitly invoke them myself. That is, commands that aren't invoked from init scripts, or by smbd and nmbd, or by other commands. (And what shared libraries won't be used, although they're typically a lot smaller.) I'm running a simple standalone server with a single file share using share level security, and one password for anonymous access. It assumes a remote DHCP server, and needs to appear on Windows systems under a particular name, and be browsable. I don't need a client, it won't be part of a domain, it won't be a WINS server, and so on. Its configuration will never change, other than possibly the machine name, the workgroup name, and the single password used to access the share. These are most of the files, and their sizes. I'm not sure all of these are really part of Samba, but they all got added as a result of adding the OE Samba package. They add up to about 83MB, and if I could cut that in half, that would be a big win. Any guidance as to what I could prune would be greatly appreciated. 1800096 usr/bin/eventlogadm 4607 usr/bin/findsmb 8351180 usr/bin/net 1526820 usr/bin/nmblookup 1826880 usr/bin/pdbedit 1465348 usr/bin/profiles 7457348 usr/bin/rpcclient 1440772 usr/bin/sharesec 5946532 usr/bin/smbcacls 5979364 usr/bin/smbclient 1465604 usr/bin/smbcontrol 5942436 usr/bin/smbcquotas 6200476 usr/bin/smbget 5966980 usr/bin/smbpasswd 3284036 usr/bin/smbspool 1514500 usr/bin/smbstatus 4910 usr/bin/smbtar 1440736 usr/bin/smbta-util 5872800 usr/bin/smbtree 30216 usr/bin/tdbbackup 26064 usr/bin/tdbdump 30180 usr/bin/tdbrestore 34600 usr/bin/tdbtool 1444868 usr/bin/testparm 166092 usr/bin/udevadm 1024 usr/lib/auth 9476 usr/lib/auth/script.so 1024 usr/lib/charset 5356 usr/lib/charset/CP437.so 5356 usr/lib/charset/CP850.so 15 usr/lib/libtdb.so.1 87516 usr/lib/libtdb.so.1.2.9 62908 usr/lib/libwbclient.so.0 131072 usr/lib/lowcase.dat 131072 usr/lib/upcase.dat 65536 usr/lib/valid.dat 1024 usr/lib/vfs 30704 usr/lib/vfs/acl_tdb.so 26612 usr/lib/vfs/acl_xattr.so 18256 usr/lib/vfs/aio_fork.so 10052 usr/lib/vfs/audit.so 18316 usr/lib/vfs/cap.so 18320 usr/lib/vfs/catia.so 5908 usr/lib/vfs/crossrename.so 5848 usr/lib/vfs/default_quota.so 1 usr/lib/vfs/dirsort.so 10004 usr/lib/vfs/expand_msdfs.so 14184 usr/lib/vfs/extd_audit.so 5844 usr/lib/vfs/fake_perms.so 47432 usr/lib/vfs/full_audit.so 9976 usr/lib/vfs/linux_xfs_sgid.so 14160 usr/lib/vfs/netatalk.so 10064 usr/lib/vfs/preopen.so 9972 usr/lib/vfs/readahead.so 18244 usr/lib/vfs/readonly.so 22384 usr/lib/vfs/recycle.so 26516 usr/lib/vfs/scannedonly.so 30676 usr/lib/vfs/shadow_copy2.so 10004 usr/lib/vfs/shadow_copy.so 22460 usr/lib/vfs/smb_traffic_analyzer.so 18296 usr/lib/vfs/streams_depot.so 22424 usr/lib/vfs/streams_xattr.so 10032 usr/lib/vfs/syncops.so 43188 usr/lib/vfs/time_audit.so 22388 usr/lib/vfs/xattr_tdb.so 7288 usr/sbin/genl-ctrl-list 10668 usr/sbin/nl-class-add 9428 usr/sbin/nl-class-delete 7376 usr/sbin/nl-classid-lookup 8824 usr/sbin/nl-class-list 10596 usr/sbin/nl-cls-add 9920 usr/sbin/nl-cls-delete 9516 usr/sbin/nl-cls-list 8760 usr/sbin/nl-link-list 8628 usr/sbin/nl-pktloc-lookup 9972 usr/sbin/nl-qdisc-add 9572 usr/sbin/nl-qdisc-delete 10028 usr/sbin/nl-qdisc-list 3488896 usr/sbin/nmbd 9822288 usr/sbin/smbd -- Ciao, Paul D. DeRocco Paulmailto:pdero...@ix.netcom.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] The network path was not found.
Looking at the dns srv records samba4 creates, I don't see any that cover what smbd is using. Does anyone have a reference for what srv records affect what ports windows looks for for registering with a domain? How do I change the ports smbd is using? I know there is a way, because \\live.sysinternals.com\Tools works through the comcast filtered ports. --hef On Wed, Apr 10, 2013 at 9:07 AM, Chris Weiss wrote: > On Wed, Apr 10, 2013 at 8:52 AM, Hef wrote: > >> After doing an nmap scan and some googling, I discovered Comcast, One of >> my >> ISPs, blocks outgoing ports 135, 139, and 445. >> >> Does anyone know a good way around those ports being blocked? >> Can I reassign them in samba, and then update srv records to match? >> >> > yes, use a VPN. smb over the wide internet is not a great idea. it's a > good thing that your ISP blocks those ports, it prevents viruses from > spreading over their networks, as well as reducing traffic from infected > machines trying to hack into machines that are not properly firewalled. > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Dynamic DNS updates not working with BIND DLZ
Hi, A while ago I setup Samba4 on CentOS 6. Samba version was 4.0.0 using the RPM from SOGo. I used the DLZ BIND backend with BIND 9.8. I tested with a Windows 7 VM client. When I joined the client to the domain it was automatically added to the AD DNS and appeared in the Windows DNS Manager. The VM had a static IP, but if I changed the IP address that change was automatically reflected in the DNS entry. I am now adding new real clients to the domain and find that they are not added to the AD domain DNS. The client has a dynamic IP, but I have tried changing to a fixed IP address and it makes no difference. The only changes I can recall between the initial setup and now are: 1. Samba upgrade to 4.0.1. After upgrading I followed the procedure and ran samba-tool dbcheck --cross-ncs --fix samba-tool ntacl sysvolreset The upgrade changed the permissions of /var/lib/samba4/private back to root:root 700, which is no good, so I changed back to root:named 750. I also added "server services = -dns" to smb.conf as per the instructions because internal DNS is now default. 2. Tested OpenChange. But, prior to doing anything I backed up entire /var/lib/samba4 directory. When I removed OpenChange (as it is just not stable yet) I removed /var/lib/samba4 and replaced it with the backup. So this should not have any effect. I have checked everything against my notes made when installing Samba4 and can't find anything wrong. In terms of DNS, /etc/named.conf contains include "/var/lib/samba4/private/named.conf"; which loads the DLZ module for BIND 9.8. The /etc/named.conf also has in the options tkey-gssapi-keytab "/var/lib/samba4/private/dns.keytab"; Permissions of files: /var/lib/samba4/private/named.conf root:named 640 /var/lib/samba4/private/dns.keytab root:named 640 /var/lib/samba4/private/dns/ root:named 770 It all seems OK (I think), but no dynamic DNS updates. There is nothing in the samba.log file to suggest a problem. The system log has messages client : update 'example.local/IN' denied samba_dlz: cancelling transaction on zone example.local Is there something I need to set in smb.conf? I see there are new options like "allow dns updates" and "dns update command", which I do not have specifically set, but I don't know if these only apply to Samba internal DNS. There is still really no documentation about smb.conf for Samba4. Can someone please explain what might be wrong or what I should look for. Regards, Stephen Jones -- Stephen Jones lloydsyst...@fastmail.com.au -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba crash (while logging in as administrator?)
I just had samba4 (git 69b3d19 from yesterday) crash while logging in as administrator. The login stalled, and on the samba4 AD DC, winbind stopped responding -- "getent passwd" stopped showing the domain entries, and commands that showed some samba users (e.g. "ls" in a directory with domain owners, "htop", etc.) would hang. dmesg shows: traps: samba[3728] trap invalid opcode ip:7fbaaff2e780 sp:7fff6859f158 error:0 in libservice.so[7fbaaff29000+7000] I'll follow up if I can reproduce this, just wanted to start a thread in case anyone else sees this. - Nick -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] missing libgnutls.so.26
On Tue, 2013-04-09 at 12:10 -0700, Phil Quesinberry wrote: > No I didn't do that... honest. > > I did a yum remove of python26 which also removes python26-devel and > python26-libs and went around the system cleaning up leftover copies of the > python 2.6 executable. After that I re-installed the above packages and > pdbedit worked once again. So, I'm getting rather confused again. You keep ripping your system apart, putting it back together again, and still having trouble. Can we do this exactly one step at a time? After installing python26-devel, and then applying the patch I sent to git master or 4.0.5 with 'git am patchfile', and running 'git clean -x -f -d', and building Samba with: PYTHON=python26 ./configure && make -j && sudo make install what still fails? Please do NOT run install_with_python.sh, as you have a working python on your system via the python26 package. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4 member of an another « Samba4 » domain
Le 10/04/2013 06:59, Gémes Géza a écrit : > You should check rfc2307 on the samba AD, if your users do not have > uidNumber gidNumber attributes they are going to be ignored by the > winbind daemon if you specify rfc2307 schema mode on the domain member. If I have understood, when I don't use rfc2307 in the dc server (this is the default) and if I don't use rfc2307 in the member server with this config: --- # No refer to "rfc2307". [global] workgroup = CHEZMOI security = ADS realm = CHEZMOI.PRIV encrypt passwords = yes idmap config *:backend = tdb idmap config *:range = 70001-8 winbind trusted domains only = no winbind use default domain = yes winbind enum users = yes winbind enum groups = yes --- It seems to work well, but the uid and the gid of the domain accounts are different between the dc and the member. And if I use the rfc2307, then it's possible to have the same uid and gid on the dc and the member. Is it correct ? For the moment, I don't succeed in the use "rfc2307" with a dc and a member. Without "rfc2307", I think It works well with: 1. For the dc: --- [global] workgroup = CHEZMOI realm = CHEZMOI.PRIV netbios name = WHEEZY-SERVER server role = active directory domain controller dns forwarder = 212.27.40.241 [netlogon] path = /usr/local/samba/var/locks/sysvol/chezmoi.priv/scripts read only = No [sysvol] path = /usr/local/samba/var/locks/sysvol read only = No --- 2. And for the member: --- [global] workgroup = CHEZMOI security = ADS realm = CHEZMOI.PRIV encrypt passwords = yes idmap config *:backend = tdb idmap config *:range = 70001-8 winbind trusted domains only = no winbind use default domain = yes winbind enum users = yes winbind enum groups = yes --- It works well (imho), but, for each account, the uid/gid are different between the dc and the member, and I don't like it. When I try to use "rfc2307", it doesn't work for me (but I should make mistakes). For example, I have tried this: 1. On the dc server: # samba-tool domain provision --realm=CHEZMOI.PRIV --domain=CHEZMOI --server-role=dc --dns-backend=SAMBA_INTERNAL --adminpass='+toto123' --use-rfc2307 that creates this smb.conf: --- [global] workgroup = CHEZMOI realm = CHEZMOI.PRIV netbios name = WHEEZY-SERVER server role = active directory domain controller dns forwarder = 212.27.40.241 idmap_ldb:use rfc2307 = yes [netlogon] path = /usr/local/samba/var/locks/sysvol/chezmoi.priv/scripts read only = No [sysvol] path = /usr/local/samba/var/locks/sysvol read only = No --- Next, I use winbind in nsswitch.conf in order to resolv the uid/gid --> names. 2. On the member, I edit this smb.conf file (found here https://wiki.samba.org/index.php/Samba4/Domain_Member#Setting_up_a_basic_smb.conf): --- [global] workgroup = CHEZMOI security = ADS realm = CHEZMOI.PRIV encrypt passwords = yes idmap config *:backend = tdb idmap config *:range = 70001-8 idmap config CHEZMOI:backend = ad idmap config CHEZMOI:schema_mode = rfc2307 idmap config CHEZMOI:range = 500-4 winbind nss info = rfc2307 winbind trusted domains only = no winbind use default domain = yes winbind enum users = yes winbind enum groups = yes --- and I join the server with "net ads join" (next I use winbind too in nsswitch.conf). Next, I create a account in the dc (samba-tool user add test1 --random-password) and, under a Windows station, I edit this account with dsa.msc and I set: - the UID attribute in the "Unix attributes" tab - the GID attribute in the "Unix attributes" tab But, the dc and the member seems to ignore this value and, for example, with "getent passwd" the uid/gid are different for each user between the dc and the member. If you are advices or links to install dc and member so that the uid/gid are the same between the dc and the member, It interest me very much. :-) Thanks in advance. PS: and very sorry for my poor english. -- François Lafont -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Winbind using 100% CPU
On Wed, Apr 10, 2013 at 06:46:48PM -0400, Dylan Klomparens wrote: > I am trying to figure out why winbind is using 100% CPU on my file server. > I am using Samba version 4.0.4. Everything is fine for a few minutes when I > start winbind, however after a while it begins using 100% CPU. I haven't > been able to narrow down what triggers this CPU usage spike, but I did > attach the GNU debugger to find out what's going on in the process. The > backtrace revealed this information: > > #0 0x0041cf30 in _talloc_free@plt () > #1 0x00452320 in winbindd_reinit_after_fork () > #2 0x004524e6 in fork_domain_child () > #3 0x00453585 in wb_child_request_trigger () > #4 0x00381d2048e2 in tevent_common_loop_immediate () from > /lib64/libtevent.so.0 > #5 0x7fbed6b98e17 in run_events_poll () from /lib64/libsmbconf.so.0 > #6 0x7fbed6b9922e in s3_event_loop_once () from /lib64/libsmbconf.so.0 > #7 0x00381d204060 in _tevent_loop_once () from /lib64/libtevent.so.0 > #8 0x0042049a in main () > > Apparently it's stuck in the winbindd_reinit_after_fork (and more > specifically the _talloc_free function). This code resides in > $SOURCE_HOME\source3\winbindd\winbindd_dual.c. > > Perhaps I have configured Samba incorrectly? Here are the parameters I am > using that have to do with winbind: > idmap config * : backend = nss > idmap config * : range = 1000 - 30 > > What are some reasons that winbind is using 100% CPU and how can I resolve > this? > > (Also, would this be an appropriate question to post to the Samba > developer's list? If so, I will repost it there.) Yes - please post to samba-technical, I'll follow up there. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Winbind using 100% CPU
I am trying to figure out why winbind is using 100% CPU on my file server. I am using Samba version 4.0.4. Everything is fine for a few minutes when I start winbind, however after a while it begins using 100% CPU. I haven't been able to narrow down what triggers this CPU usage spike, but I did attach the GNU debugger to find out what's going on in the process. The backtrace revealed this information: #0 0x0041cf30 in _talloc_free@plt () #1 0x00452320 in winbindd_reinit_after_fork () #2 0x004524e6 in fork_domain_child () #3 0x00453585 in wb_child_request_trigger () #4 0x00381d2048e2 in tevent_common_loop_immediate () from /lib64/libtevent.so.0 #5 0x7fbed6b98e17 in run_events_poll () from /lib64/libsmbconf.so.0 #6 0x7fbed6b9922e in s3_event_loop_once () from /lib64/libsmbconf.so.0 #7 0x00381d204060 in _tevent_loop_once () from /lib64/libtevent.so.0 #8 0x0042049a in main () Apparently it's stuck in the winbindd_reinit_after_fork (and more specifically the _talloc_free function). This code resides in $SOURCE_HOME\source3\winbindd\winbindd_dual.c. Perhaps I have configured Samba incorrectly? Here are the parameters I am using that have to do with winbind: idmap config * : backend = nss idmap config * : range = 1000 - 30 What are some reasons that winbind is using 100% CPU and how can I resolve this? (Also, would this be an appropriate question to post to the Samba developer's list? If so, I will repost it there.) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Wrong local DNS responses from samba4
Am 10.04.2013 20:29, schrieb Nick Semenkovich: I'll take a look -- by what mechanism do clients update the AD with their current IPs? (I think these were the IPs the machines had during domain creation). In the settings of the IP protocol of the network adapter you can find in the DNS tab a checkbox 'register adresses of this connection in DNS' (don't know the exact english wording). Here is a description about dynamic DNS update: http://technet.microsoft.com/en-us/library/cc784052%28v=ws.10%29.aspx You can try forcing your machine to update the DNS registration: # ipconfig /registerdns [Can I force samba to pass any missing record requests up to the relay DNS? I'm not sure if you can do this. The samba DNS is authorative for the zone. Why should not resolvable records of it's own zone forwarded to a foreign server? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Wrong local DNS responses from samba4
On Wed, Apr 10, 2013 at 1:00 PM, Marc Muehlfeld wrote: > Am 10.04.2013 04:54, schrieb Nick Semenkovich: > > - If you look into the zone via the windows DNS snap-in - do you see the >>> correct IP for this record there? >>> >> >> No, it shows the incorrect record. >> > > > If you see the wrong IP in the DNS snap-in too, the it's really inside the > AD database and doesn't come from somewhere outside. > > If you correct the record inside the DNS snap-in by hand, does it switch > back to the wrong one after a while (e.g. reboot)? Or if you add new > machines to the domain? > I'll take a look -- by what mechanism do clients update the AD with their current IPs? (I think these were the IPs the machines had during domain creation). [Can I force samba to pass any missing record requests up to the relay DNS? e.g. if I delete aio1.corp.example.com from the AD database, and there's a DNS lookup to samba, can I make samba ask its upstream DNS? Last I tried this (with some printers that aren't AD members), samba simply returned NXDOMAIN, rather than asking upstream. ] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Wrong local DNS responses from samba4
Am 10.04.2013 04:54, schrieb Nick Semenkovich: - If you look into the zone via the windows DNS snap-in - do you see the correct IP for this record there? No, it shows the incorrect record. If you see the wrong IP in the DNS snap-in too, the it's really inside the AD database and doesn't come from somewhere outside. If you correct the record inside the DNS snap-in by hand, does it switch back to the wrong one after a while (e.g. reboot)? Or if you add new machines to the domain? Maybe increase the samba log level. Maybe the logs give a hint. Regards Marc -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba 4 - problems with name resolution on Windows 7 clients
On 04/10/2013 09:48 AM, X-Dimension wrote: We have a strange name resolution problem on Windows 7 clients. (Windows XP clients are working fine!) If a Windows 7 client is connected more than 7 or 8 hours to our Samba 4 active directory server, we can't do "ping servername" anymore, but "ping servername.domainname" works fine. After logout and login again to the Windows 7 clients everything works! Can you check what is the ipconfig /all output on windows 7 clients ? also you should do a tcpdump/wireshark trace on your client to see which DNS request it is doing. The main problem is, that all Windows clients access the samba shares by \\servername\sharename and not \\servername.domainname\sharename and after 7 or 8 hours our users can't access the files or programs on these shares. What goes wrong here and what is the best way to fix this? I can change some GPOs and set all shares to \\servername.domainname\sharename, but if there is a better solution i would prefer this. Thx for help! :) Matthieu. -- Matthieu Patou Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba 4 - problems with name resolution on Windows 7 clients
We have a strange name resolution problem on Windows 7 clients. (Windows XP clients are working fine!) If a Windows 7 client is connected more than 7 or 8 hours to our Samba 4 active directory server, we can't do "ping servername" anymore, but "ping servername.domainname" works fine. After logout and login again to the Windows 7 clients everything works! The main problem is, that all Windows clients access the samba shares by \\servername\sharename and not \\servername.domainname\sharename and after 7 or 8 hours our users can't access the files or programs on these shares. What goes wrong here and what is the best way to fix this? I can change some GPOs and set all shares to \\servername.domainname\sharename, but if there is a better solution i would prefer this. Thx for help! :) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Passwording a simple anonymous share
From: "Paul D. DeRocco" Date: Tue, 9 Apr 2013 14:38:34 -0700 > I have an embedded box (Yocto Project based linux distro) to which I'm > adding Samba 3.6 (from OpenEmbedded). All I need it for is to provide one > browsable file share that allows read/write access to anyone on the network. > But I want it to be password protected. Try these settings: [sharename] path=/sharedfiles users = root read only = yes And to set password to "root" with smbpasswd command. --- TAKAHASHI Motonobu / @damemonyo facebook.com/takahashi.motonobu -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] The network path was not found.
On Wed, Apr 10, 2013 at 8:52 AM, Hef wrote: > After doing an nmap scan and some googling, I discovered Comcast, One of my > ISPs, blocks outgoing ports 135, 139, and 445. > > Does anyone know a good way around those ports being blocked? > Can I reassign them in samba, and then update srv records to match? > > yes, use a VPN. smb over the wide internet is not a great idea. it's a good thing that your ISP blocks those ports, it prevents viruses from spreading over their networks, as well as reducing traffic from infected machines trying to hack into machines that are not properly firewalled. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] The network path was not found.
After doing an nmap scan and some googling, I discovered Comcast, One of my ISPs, blocks outgoing ports 135, 139, and 445. Does anyone know a good way around those ports being blocked? Can I reassign them in samba, and then update srv records to match? On Wed, Apr 10, 2013 at 1:02 AM, Hef wrote: > More information: I attempted to connect to the server via \\ > ad.redacted.com\Test. The diagnose button shows this: > > Problems found > > file and price resource( auth.ad.redacted.com) is online but isn't > responding to connection attempts. > > I grabbed Active Directory Explorer from sysinternals, and was able to > explore the directory using the Administrator account. > > --hef > > Again, sorry for misusing the reply button. > > On Tue, Apr 9, 2013 at 9:04 AM, Hef wrote: > >> The realm is ad.redacted.com and the samba4 server is >> auth.ad.redacted.com. >> >> both ad.redacted.com and auth.ad.redacted.com have A and records >> that correctly point to auth.ad.redacted.com public ip addresses, >> verified by ping and ping6 from my linux desktop. The windows 7 VM is able >> to ping both as well, and uses the ipv6 address. The windows 7 VM is able >> to ping the ipv4 address if I don't use a dns name. >> >> >> On Tue, Apr 9, 2013 at 12:46 AM, Daniel wrote: >> >>> From the client what is the results of a nslookup on redacted.com and >>> ad.redacted.com >>> >>> Could be a simple dns entry missing >>> >>> >>> Regards, >>> Daniel >>> -- >>> From: Hef >>> Sent: 9/04/2013 2:43 PM >>> >>> To: samba@lists.samba.org >>> Subject: [Samba] The network path was not found. >>> >>> I am attempting to join a windows 7 computer running in virtual box to a >>> samba4 domain (version 4.1.0pre1-GIT-243278a). >>> >>> I get prompted for credentials, I use the provisioned Administrator >>> account, and then get the following: >>> >>> The Following error occured attempting to join the domain >>> "ad.redacted.com" >>> >>> The network path was not found. >>> >>> >>> (I have replaced the actual domain with redacted for this email) >>> >>> I have a ns record for ad.redacted.com pointing to the samba 4 instance, >>> but the samba4 server is running on a vm instance in several hundred >>> miles >>> away. >>> >>> What am I doing wrong? What else can I do to debug this problem? >>> >>> --hef >>> -- >>> To unsubscribe from this list go to the following URL and read the >>> instructions: https://lists.samba.org/mailman/options/samba >>> >> >> > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
