AW: [Samba] remote samba connection
Hello, of corse it is! You need a dyndns adress and a router in your office that will forward dyndns to your linux box. Example1: on which is running davenport: http://davenport.sourceforge.net/. Configure davenport to fit your needs On Your XP Client you should install novell s netdrive. Example2: on a html basis- http://prdownloads.sourceforge.net/[..]bclient/smbwebclient-2.9.php.gz?d ownload Daniel -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Bahadir Tonguc / Supramar Gesendet: Montag, 22. September 2008 21:09 An: samba@lists.samba.org Betreff: [Samba] remote samba connection dear friends, I have just installed Samba on my Ubuntu machine in the office and could successfully connect from WinXP within the office network. As you might have guessed, Vista computers all failed to connect to Samba. The problem or the question is; would it still be possible for me to access the shared folder on the Ubuntu machine from my XP laptop from home ??? Ubuntu pc has static IP however when I try to connect using "start > run > \\xxx.yyy.zzz.aa\" it failed to connect. Is there a way to connect from home to office? Thanks for all your assistance Regards Bahadir Tonguc -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] need migration/upgrade help
- Original Message From: Rubin Bennett <[EMAIL PROTECTED]> To: samba list Sent: Monday, September 22, 2008 5:48:15 PM Subject: Re: [Samba] need migration/upgrade help You should only ever need to copy your passdb.tdb and secrets.tdb file from the old system to the new. The rest of the files will be generated for you when you start smbd. The trick I've found is that often different versions and/ or distros store those tdb files in different places, i.e.: Mandriva likes /var/lib/samba or /var/lib/samba/private and Centos likes /etc/samba. So if you try to modify the tdbsam directive in your config file you only end up with 1/2 the solution, i.e. on CentOS set: passdb backend = tdbsam:/var/lib/samba/private/passdb.tdb This would return a valid looking output from pdbedit -Lv but all the passwords would be wrong because it's quietly still looking at the (empty) secrets.tdb in /etc/samba! Does it sould like I've been through this before? :) Anyway, what I've learned to do is: Make a backup copy of passdb.tdb and secrets.tdb Delete all the tdb files in /etc/samba /etc/samba/private /var/lib/samba and /var/lib/samba/private. Copy my smb.conf file, and set passwd backend=tdbsam in it. Run smbpasswd -a and look for the newly created passdb.tdb and secrets.tdb files. Shut Samba down, and replace those new files with my backup copies. Restart Samba. This will return valid output (i.e. your list of users and computers) from pdbedit -L, and their passwords will actually work. Hope this saves you some pain! Rubin -- Rubin Bennett RB Technologies http://thatitguy.com [EMAIL PROTECTED] (802)223-4448 Think for yourselves and let others enjoy the privilege to do so, too. ~Voltaire On Mon, 2008-09-22 at 17:36 -0700, g s wrote: > Hello All, > > I am trying to migrate samba from a box with Mandrake 10.1 with Samba > 3.0.10 to a new box running CentOS 5.2 with Samba 3.0.28. The two > versions of samba are too differnet to simply copy the config and tdb > files over to the new box and the Mandrake box won't upgrade past > 3.0.10. I could really use some suggestions. Thanks > > The problem when I do that is the Centos box with Samba 3.0.28 generates > an schannel_store.tdb in the "private" dir when I attempt to login from a > client machine. It allows the login but denies access to the users home > dir on the samba server. In the schannel_store.tdb some machine info is > placed similar to what you see in the secrets.tdb file. This causes problems > with the client machines not being able to find the user profile...etc. I > would > like to fix this issue the "right way" whatever that is, instead of starting > over > and rejoining all the machines in the domain again. Any insights would be > appreciated. Thanks. > > > Greg > > > > Woops...my yahoo decided to include my last post in your signature. In case it was missed, here it is: Rubin, Ok...that makes sense, thank you for the very thorough explination. I was thinking of just backing up the smbpasswd and secrets.tdb files, although the docs also say to copy certain .tdb files, in my case, from the /var/cache/samba dir. But this is beside the point. I was wondering how your description would be different with an smbpasswd backend. Since I am not using the tdbsam backend. Just do the same as described above and replace the generated smbpasswd and secrets.tdb files? Thanks again! Greg Strohecker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] need migration/upgrade help
- Original Message From: Rubin Bennett <[EMAIL PROTECTED]> To: samba list Sent: Monday, September 22, 2008 5:48:15 PM Subject: Re: [Samba] need migration/upgrade help You should only ever need to copy your passdb.tdb and secrets.tdb file from the old system to the new. The rest of the files will be generated for you when you start smbd. The trick I've found is that often different versions and/ or distros store those tdb files in different places, i.e.: Mandriva likes /var/lib/samba or /var/lib/samba/private and Centos likes /etc/samba. So if you try to modify the tdbsam directive in your config file you only end up with 1/2 the solution, i.e. on CentOS set: passdb backend = tdbsam:/var/lib/samba/private/passdb.tdb This would return a valid looking output from pdbedit -Lv but all the passwords would be wrong because it's quietly still looking at the (empty) secrets.tdb in /etc/samba! Does it sould like I've been through this before? :) Anyway, what I've learned to do is: Make a backup copy of passdb.tdb and secrets.tdb Delete all the tdb files in /etc/samba /etc/samba/private /var/lib/samba and /var/lib/samba/private. Copy my smb.conf file, and set passwd backend=tdbsam in it. Run smbpasswd -a and look for the newly created passdb.tdb and secrets.tdb files. Shut Samba down, and replace those new files with my backup copies. Restart Samba. This will return valid output (i.e. your list of users and computers) from pdbedit -L, and their passwords will actually work. Hope this saves you some pain! Rubin On Mon, 2008-09-22 at 17:36 -0700, g s wrote: > Hello All, > > I am trying to migrate samba from a box with Mandrake 10.1 with Samba > 3.0.10 to a new box running CentOS 5.2 with Samba 3.0.28. The two > versions of samba are too differnet to simply copy the config and tdb > files over to the new box and the Mandrake box won't upgrade past > 3.0.10. I could really use some suggestions. Thanks > > The problem when I do that is the Centos box with Samba 3.0.28 generates > an schannel_store.tdb in the "private" dir when I attempt to login from a > client machine. It allows the login but denies access to the users home > dir on the samba server. In the schannel_store.tdb some machine info is > placed similar to what you see in the secrets.tdb file. This causes problems > with the client machines not being able to find the user profile...etc. I > would > like to fix this issue the "right way" whatever that is, instead of starting > over > and rejoining all the machines in the domain again. Any insights would be > appreciated. Thanks. > > > Greg > > > > -- Rubin Bennett RB Technologies http://thatitguy.com [EMAIL PROTECTED] (802)223-4448 Think for yourselves and let others enjoy the privilege to do so, too. ~Voltaire Rubin, Ok...that makes sense, thank you for the very thorough explination. I was thinking of just backing up the smbpasswd and secrets.tdb files, although the docs also say to copy certain .tdb files, in my case, from the /var/cache/samba dir. But this is beside the point. I was wondering how your description would be different with an smbpasswd backend. Since I am not using the tdbsam backend. Just do the same as described above and replace the generated smbpasswd and secrets.tdb files? Thanks again! Greg Strohecker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba 4 installation problem
Hello, I'm trying install Samba 4 by this link http://wiki.samba.org/index.php/Samba4/HOWTO . The step 2 compile and step 3 install completed, but step 4 provisionhas following error: [EMAIL PROTECTED] setup]# ./provision --realm=sfa.local --domain=sfa --adminpass= --server-role='domain controller'Traceback (most recent call last): File "./provision", line 32, in ?import sambaImportError: No module named samba Could someone has experience to fix this problem ? Thanks _ Connect to the next generation of MSN Messenger http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] (no subject)
Ray, Tito wrote: Hello, I am using samba 2.2.2 in AIX 5.1 environment and planning to upgrade to a more stable samba. 1. Which version is most stable? 2. Do I need to pay for the Licence? 3. How can I upgrade? http://www.samba.org Also, don't send messages without a subject. Thank you! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] (no subject)
Hello, I am using samba 2.2.2 in AIX 5.1 environment and planning to upgrade to a more stable samba. 1. Which version is most stable? 2. Do I need to pay for the Licence? 3. How can I upgrade? Regards, Tito -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] need migration/upgrade help
On Mon, 2008-09-22 at 17:36 -0700, g s wrote: > Hello All, > > I am trying to migrate samba from a box with Mandrake 10.1 with Samba > 3.0.10 to a new box running CentOS 5.2 with Samba 3.0.28. The two > versions of samba are too differnet to simply copy the config and tdb > files over to the new box and the Mandrake box won't upgrade past > 3.0.10. I could really use some suggestions. Thanks Whoops, sorry to all for the top post :( 50 lashes with a wet noodle for me... Rubin -- Rubin Bennett RB Technologies http://thatitguy.com [EMAIL PROTECTED] (802)223-4448 Think for yourselves and let others enjoy the privilege to do so, too. ~Voltaire -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] need migration/upgrade help
You should only ever need to copy your passdb.tdb and secrets.tdb file from the old system to the new. The rest of the files will be generated for you when you start smbd. The trick I've found is that often different versions and/ or distros store those tdb files in different places, i.e.: Mandriva likes /var/lib/samba or /var/lib/samba/private and Centos likes /etc/samba. So if you try to modify the tdbsam directive in your config file you only end up with 1/2 the solution, i.e. on CentOS set: passdb backend = tdbsam:/var/lib/samba/private/passdb.tdb This would return a valid looking output from pdbedit -Lv but all the passwords would be wrong because it's quietly still looking at the (empty) secrets.tdb in /etc/samba! Does it sould like I've been through this before? :) Anyway, what I've learned to do is: Make a backup copy of passdb.tdb and secrets.tdb Delete all the tdb files in /etc/samba /etc/samba/private /var/lib/samba and /var/lib/samba/private. Copy my smb.conf file, and set passwd backend=tdbsam in it. Run smbpasswd -a and look for the newly created passdb.tdb and secrets.tdb files. Shut Samba down, and replace those new files with my backup copies. Restart Samba. This will return valid output (i.e. your list of users and computers) from pdbedit -L, and their passwords will actually work. Hope this saves you some pain! Rubin On Mon, 2008-09-22 at 17:36 -0700, g s wrote: > Hello All, > > I am trying to migrate samba from a box with Mandrake 10.1 with Samba > 3.0.10 to a new box running CentOS 5.2 with Samba 3.0.28. The two > versions of samba are too differnet to simply copy the config and tdb > files over to the new box and the Mandrake box won't upgrade past > 3.0.10. I could really use some suggestions. Thanks > > The problem when I do that is the Centos box with Samba 3.0.28 generates > an schannel_store.tdb in the "private" dir when I attempt to login from a > client machine. It allows the login but denies access to the users home > dir on the samba server. In the schannel_store.tdb some machine info is > placed similar to what you see in the secrets.tdb file. This causes problems > with the client machines not being able to find the user profile...etc. I > would > like to fix this issue the "right way" whatever that is, instead of starting > over > and rejoining all the machines in the domain again. Any insights would be > appreciated. Thanks. > > > Greg > > > > -- Rubin Bennett RB Technologies http://thatitguy.com [EMAIL PROTECTED] (802)223-4448 Think for yourselves and let others enjoy the privilege to do so, too. ~Voltaire -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] need migration/upgrade help
Hello All, I am trying to migrate samba from a box with Mandrake 10.1 with Samba 3.0.10 to a new box running CentOS 5.2 with Samba 3.0.28. The two versions of samba are too differnet to simply copy the config and tdb files over to the new box and the Mandrake box won't upgrade past 3.0.10. I could really use some suggestions. Thanks The problem when I do that is the Centos box with Samba 3.0.28 generates an schannel_store.tdb in the "private" dir when I attempt to login from a client machine. It allows the login but denies access to the users home dir on the samba server. In the schannel_store.tdb some machine info is placed similar to what you see in the secrets.tdb file. This causes problems with the client machines not being able to find the user profile...etc. I would like to fix this issue the "right way" whatever that is, instead of starting over and rejoining all the machines in the domain again. Any insights would be appreciated. Thanks. Greg -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Default Domain Not Working.
Hello, I have a AD group called sudo1 which has user user1 as its member both are members of Domain1 Now when I do getent group sudo1 the result is sudo1:x:202120:Domain1+user1 I dont want it show as Domains1+user1, just want it to show as user1 I have winbind default domain = yes. Anything has to be changed on smb.conf? thank you all.. ~LA -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] remote samba connection
dear friends, I have just installed Samba on my Ubuntu machine in the office and could successfully connect from WinXP within the office network. As you might have guessed, Vista computers all failed to connect to Samba. The problem or the question is; would it still be possible for me to access the shared folder on the Ubuntu machine from my XP laptop from home ??? Ubuntu pc has static IP however when I try to connect using "start > run > \\xxx.yyy.zzz.aa\" it failed to connect. Is there a way to connect from home to office? Thanks for all your assistance Regards Bahadir Tonguc -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba with 2 NICs
On Monday 22 September 2008 12:50:29 pm hamacker wrote: > interfaces = bond0, eth0, lo Odd that it doesn't work w/o eth0 in there. Suggest changing to the IP address instead of using the interface name: interfaces = 192.168.1.2, lo Also, be sure to tune your "modprobe bonding" arguments for the type of service you want, example: "modprobe bonding miimon=100 mode=1". Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and Vista profile probs
See : http://lists.samba.org/archive/samba-technical/2007-April/052674.html -- View this message in context: http://www.nabble.com/Samba-and-Vista-profile-probs-tp16764249p19612052.html Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba with 2 NICs
/etc/network/interfaces accept bond0 and runs fine, I change : interfaces = bond0, lo bind interfaces only = Yes in smb.conf I can ping from anywhere, but Samba can not autenticate any Windows. Then I change again and back in /etc/network/interfaces to eth0. And include in smb.conf : interfaces = bond0, eth0, lo bind interfaces only = Yes And now everything is OK, both WinXP e Win9x can logon into domain. But 'eth0' still disable, see : bond0 Link encap:Ethernet HWaddr 00:0c:76:97:04:f3 inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20c:76ff:fe97:4f3/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:290850 errors:0 dropped:0 overruns:0 frame:0 TX packets:285844 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:75906076 (72.3 MB) TX bytes:219213427 (209.0 MB) eth0 Link encap:Ethernet HWaddr 00:0c:76:97:04:f3 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:96067 errors:0 dropped:0 overruns:0 frame:0 TX packets:142953 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:28372347 (27.0 MB) TX bytes:109526393 (104.4 MB) Interrupt:18 Base address:0x2000 eth1 Link encap:Ethernet HWaddr 00:0c:76:97:04:f3 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:194783 errors:0 dropped:0 overruns:0 frame:0 TX packets:142891 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:47533729 (45.3 MB) TX bytes:109687034 (104.6 MB) Interrupt:19 Base address:0x9000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1324 errors:0 dropped:0 overruns:0 frame:0 TX packets:1324 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:106749 (104.2 KB) TX bytes:106749 (104.2 KB) I dont know Why change directly /etc/network/interfaces does not permit Win machines autenticate on Samba, but : # ifconfig bond0 192.168.1.2 netmask 255.255.255.0 # ifenslave -v bond0 eth0 eth1 # route add default gw 192.168.1.254 in terminal and changes in smb.conf, resolve my problem. Thanks a lot. 2008/9/20 Chris Smith <[EMAIL PROTECTED]>: > On Saturday 20 September 2008 11:35:42 am hamacker wrote: >> # ifconfig eth0 >> eth0 Link encap:Ethernet HWaddr 00:0c:76:97:04:f3 >> inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 > > eth0 should not have an address - it should belong only to bond0. > eth0 and eth1 are both slaves to the master bond0. > >> # The primary network interface >> auto eth0 >> iface eth0 inet static > > Should probably more like: > iface bond0 inet static > >> my smb.conf : >> [global] >> unix charset = UTF8 >> workgroup = VIDY2005 >> server string = %h server (Samba %v) >> interfaces = eth0, eth1 > > Should be: > interfaces = bond0, lo > bind interfaces only = Yes > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and Vista profile probs
Hi, My english is not very good, so french ! I had solve this problem, like this. Vista or 2008 server, search share with the name profiles.V2. If it doesn't existe Vista create in your $PATH/profiles your account $USER.V2, but dont update it ! So I made it happy (vista) with : smb.conf [profiles.V2] copy = profiles So now in $PATH/profiles there is all my profiles for XP, Vista, and vista doesn't cry any more ! -- View this message in context: http://www.nabble.com/Samba-and-Vista-profile-probs-tp16764249p19612004.html Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [SOLVED] Howto auth against an NT domain I don't control?
After many more hours of searching, I found someone else in the exact same
situation as me.
Not only him. I also had the same problem, but applied a simpler patch.
The client has already sent what it wants you to use, so just use it.
I can't see why you wouldn't want to do so. You have already decided
to trust a Windows authentication server, so why not send it the domain
that the client has asked you to? If the credentials as duff then the
Windows server will say so. To replace the domain name with one which
has absolutely *nothing* to do with the client, and hence makes the
authentication bound to fail, unless it happens to be the default domain
of the DC, seems completely wrong to me.
This was what I used:
===
--- auth_util.c.origWed May 28 13:41:11 2008
+++ auth_util.c Fri Jun 6 10:43:03 2008
@@ -173,7 +173,11 @@
and let the "passdb backend" handle unknown users. */
if ( !is_trusted_domain(domain) && !strequal(domain,
get_global_sam_name()) )
+ {
+/* XXX - Leave alone if SEC_SERVER */
+ if ( lp_security() != SEC_SERVER )
domain = my_sam_name();
+ }
/* we know that it is a trusted domain (and we are allowing
them) or it is our domain */
==
The original report, and reply, is at:
http://fixunix.com/samba/381697-samba-using-windows-dc-security-server-mode.html
How does one go about getting this fixed in the Samba code base?
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Binary packages for all SUSE and other Linux systems (was: Samba 3.2.4 Available for Download)
On Thu, Sep 18, 2008 at 04:52:34PM +0200, Karolin Seeger wrote: [ 8< ] > Binary packages will be made available on a volunteer basis from > > http://download.samba.org/samba/ftp/Binary_Packages/ RPM package installation sources of Samba 3.2.4 (STABLE) for SUSE Linux products are available at ftp.suse.com/pub/projects/samba/STABLE/ The same package installation sources are also available at http://download.Samba.org/samba/ftp/Binary_Packages/SuSE/ For easier collaboration Samba packages are also provided by the openSUSE Build Service for many different Linux flavors[1] at http://en.opensuse.org/Samba#openSUSE_Build_Service If you encounter any problems with these packages please don't blame the Samba Team. Instead file a bug to https://bugzilla.Samba.org/, pick product Samba 3.2, then select 'component' Packaging and set 'assign to' to samba-maintainers at suse dot de. Or use http://bugzilla.Novell.com/ with the same assignee instead. For general information about Samba as part of SUSE Linux based products see http://en.openSUSE.org/Samba For reporting bugs and how to collect advanced debugging information see http://en.openSUSE.org/Bugs/Samba Our customers, our products, our responsibility. Have a lot of fun... Lars Müller - for the Novell Samba Team [1] Currently these are CentOS, Fedora, Mandriva, RedHat Enterprise (RHEL), SUSE Linux Enterprise (SLE), and openSUSE. -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SuSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany pgpVdZzz0i4SV.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
