Samba is intended for Linux, allowing Linux users to interoperate with
Windows. But has anyone ever attempted building/using the Samba code on
Windows? Could Samba be used to do the protocol stuff in a Windows
application?
Seems like there's no reason to re-invent the wheel and dig through
write a CIFS/SMB client, when Samba has already done it? I
know Samba is intended for Linux, allowing Linux users to interoperate
with Windows. But has anyone ever attempted building/using the Samba
code on Windows? Could Samba be used to do the protocol stuff in a
Windows application?
Seems
Hi,
I'm bashing my head against a brick wall against a strange Win7 domain
login issue.
We have a Samba 3 CentOS server which for some months has been a problem
free PDC for a network of about 15 Win7Pro64 clients in a school.
Recently, for some reason, the following situation has now
Yes I am Polish but I didn't have time yet to investigate the problem.
Maybe it is language related... I can check it also (I have some
non-polish xp's). I'll let you know.
Daniel
W dniu 2012-01-27 13:19, BartekR pisze:
Hello !
I've upgraded samba to 3.6.1 during migration to new hardware.
Hello !
I've upgraded samba to 3.6.1 during migration to new hardware. Problem
remains the same.
Offtop. Are You Polish ? Nobody else reported similar problem. Perhaps
it is language related (language specyfic Windows update).
Thanks!
BartekR
W dniu 2012-01-26 21:59, Daniel Deptuła pisze:
Hello!
I'm afraid I have the same problem in my network. We have a domain where
Samba (3.5.11) is the PDC. Clients include Windows XP's and 7's. I
recently noticed that many stations are not visible in the browselist.
I'll investigate it and let you know about the results.
Daniel
W dniu
Hello !
I would like to refresh this topic beacuse I have discovered something
new. This problem relates only to machines with WINDOWS XP with
automatic system update enabled. Win XP sp2 (fresh install) with
disabled updates does not dissapear! So should i try to uninstall some
of updates
Hi
Version 4.0.0alpha18-GIT-bfc7481
In smb.conf I have:
[profiles]
path = /usr/local/samba/var/profiles
read only = no
The profiles are set to \\DOMAIN\profiles\%USERNAME% using dsa.msc
When a user first logs on, there is a message:
'You cannot access your files and files
On Fri, Dec 30, 2011 at 11:22 AM, steve st...@steve-ss.com wrote:
Hi
Version 4.0.0alpha18-GIT-bfc7481
In smb.conf I have:
[profiles]
path = /usr/local/samba/var/profiles
read only = no
The profiles are set to \\DOMAIN\profiles\%USERNAME% using dsa.msc
When a user first logs
The permissions on /usr/local/samba/var/profiles are:
drwxr-xr-x 6 root root 4096 Dec 30 16:31 profiles
Any ideas anyone?
I have the profiles folder set to 1777 (drwxrwxrwt)
bernd
--
To unsubscribe from this list go to the following URL and read the
instructions:
The only way to have Windows clients use Samba in the way that you want
is to use Samba4, as an AD DC. With Samba 3.x, Windows clients will not
use kerberos.
We have a migration script from Samba3, but not from Heimdal (but due to
recent requests, I'm going to see what I can do about
On Mon, 2011-11-21 at 11:25 +1300, brijesh patel wrote:
Does it mean i need to use samba4 and have to use inbuilt kerberos and
ldap server because this link says ldap backend is not supported.
Correct.
http://wiki.samba.org/index.php/Samba4/LDAP_Backend#.28De.29motivation
If yes how would i
to do
anything on those machines?)
Any help would be appreciated.
The only way to have Windows clients use Samba in the way that you want
is to use Samba4, as an AD DC. With Samba 3.x, Windows clients will not
use kerberos.
We have a migration script from Samba3, but not from Heimdal (but due
Hi,
I am sure someone may have already asked this question but i can't find any
useful documentation about this. I would like to use our existing kerberos
(openldap) setup to authenticate users against windows machines. So far i have
managed to authenticate users against ldap password with
----
Now the tutorial is on an earlier version so some changes may be
required,
but it's clear to see from my output that a domain is being set
rather than
a Workgroup. Any ideas?
Paul.
--
View this message in context:
http://samba.2283325.n4.nabble.com/Samba
From: phpMagpie phpmag...@webbedit.co.uk
Date: Tue, 6 Sep 2011 12:09:26 -0700 (PDT)
The first validation step is to run 'smbclient -L localhost -U%'.
*It should have returned something like:*
Sharename Type Comment
- ---
Plans
so some changes may be required,
but it's clear to see from my output that a domain is being set rather than
a Workgroup. Any ideas?
Paul.
--
View this message in context:
http://samba.2283325.n4.nabble.com/Samba-CentOS-Windows-7-Ultimate-64-no-login-tp3793880p3794292.html
Sent from the Samba
to have helped.
Could someone help me out here or direct me to a GOOD tutorial anywhere that
would guide me through this process from scratch?
Thanks, Paul.
--
View this message in context:
http://samba.2283325.n4.nabble.com/Samba-CentOS-Windows-7-Ultimate-64-no-login-tp3793880p3793880.html
Sent
From: phpMagpie phpmag...@webbedit.co.uk
Date: Tue, 6 Sep 2011 09:25:28 -0700 (PDT)
(snip)
Here is my /etc/samba/smb.conf:
[global]
workgroup = WEBBEDIT
netbios name = smbserver
security = SHARE
load printers = No
default service = global
path = /home
available = No
encrypt passwords =
as this is only
ro be used on my small internal network.
Thanks again, Paul.
--
View this message in context:
http://samba.2283325.n4.nabble.com/Samba-CentOS-Windows-7-Ultimate-64-no-login-tp3793880p3794189.html
Sent from the Samba - General mailing list archive at Nabble.com.
--
To unsubscribe from
.nabble.com/Samba-CentOS-Windows-7-Ultimate-64-no-login-tp3793880p3794292.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/options/samba
Just wanted to say thanks for the help! I've now got it working.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
or suggests using domain wide Group Policy Objects (GPO's). My
understanding is that GPO's can only be used if you have a Windows AD
server
or Samba 4 however I don't have a Windows server and Samba 4 is abit too
bleeding edge for a production deployment(?).
Not true. I use GPO's
documentation and details seem
quite scarce. However all the documentation I've found is targeted at
Windows XP or suggests using domain wide Group Policy Objects (GPO's). My
understanding is that GPO's can only be used if you have a Windows AD server
or Samba 4 however I don't have a Windows server
if you have a Windows AD server
or Samba 4 however I don't have a Windows server and Samba 4 is abit too
bleeding edge for a production deployment(?).
If anyone can point me to some good documentation it would be really useful,
I would love to see an updated The Official Samba HOWTO and Reference
On 21.07.2011, at 17:07, Tanuki uk wrote:
Hello,
I'm quite new to Samba administration and I've inherited a working samba
setup with roaming profiles however the login and logout times for users has
been growing and I'm starting to think it's time do something about it.
I'd be curious what
Group Policy Objects (GPO's). My
understanding is that GPO's can only be used if you have a Windows AD server
or Samba 4 however I don't have a Windows server and Samba 4 is abit too
bleeding edge for a production deployment(?).
If anyone can point me to some good documentation it would be really
only be used if you have a Windows AD server
or Samba 4 however I don't have a Windows server and Samba 4 is abit too
bleeding edge for a production deployment(?).
If anyone can point me to some good documentation it would be really useful,
I would love to see an updated The Official Samba HOWTO
On 07/21/2011 11:31 AM, Geert Mak wrote:
On 21.07.2011, at 17:07, Tanuki uk wrote:
Hello,
I'm quite new to Samba administration and I've inherited a working
samba setup with roaming profiles however the login and logout
times for users has been growing and I'm starting to think it's
time do
a look around at various documentation and details seem
quite scarce. However all the documentation I've found is targeted at
Windows XP or suggests using domain wide Group Policy Objects (GPO's). My
understanding is that GPO's can only be used if you have a Windows AD server
or Samba 4 however I
Hi!
Since there is no clean solution for this I wrote simple perl script.
Simplified algorithm:
1. Load /etc/hosts
2. Use arping to check every ip from /etc/hosts (belonging to local
network) for presence.
3. If there is an arp response check this host by issuing smbclient.
4. If there is an
So it is impossible to solve this issue ?
I don't have any other ideas except some kind of nasty workaround:
Ill write perl script. It would periodically check every machine in
/etc/ethers for presence and smb/nmb activity. Depending on that it will
maintain directory with windows-style
On Wed, May 11, 2011 at 7:58 AM, BartekR bojle...@gmail.com wrote:
So it is impossible to solve this issue ?
Maybe :)
Try running:
=
net config server /autodisconnect:-1
=
on the XP workstations.
Check the network device in device manager and make sure
W dniu 2011-05-11 15:41, Chris Smith pisze:
On Wed, May 11, 2011 at 7:58 AM, BartekRbojle...@gmail.com wrote:
So it is impossible to solve this issue ?
Maybe :)
Try running:
=
net config server /autodisconnect:-1
=
on the XP workstations.
No
BartekR wrote:
So it is Windows XP workstations to blame or maybe there is another
thing that i should check ?
The command
nmblookup -MS -- -
lists the status of all master browsers on your network. That will tell you
if the problem is caused by your server losing its master status, or by
W dniu 08.05.2011 21:48, Chris Smith pisze:
On Sun, May 8, 2011 at 1:59 PM, BartekRbojle...@gmail.com wrote:
So it is Windows XP workstations to blame or maybe there is another thing
that i should check ?
I run several Samba installations with no such issues with XP. So
unless your XP
# nmblookup -MS -- -
INFO: Current debug levels:
all: True/10
tdb: False/0
printdrivers: False/0
lanman: False/0
smb: False/0
rpc_parse: False/0
rpc_srv: False/0
rpc_cli: False/0
passdb: False/0
sam: False/0
auth: False/0
winbind: False/0
vfs: False/0
idmap: False/0
On Mon, May 9, 2011 at 10:41 AM, BartekR bojle...@gmail.com wrote:
name resolve order = wins host bcast
As You wrote below. Am I correct ?
3) make sure that your DHCP server (you seem to have enough systems
that manual configuration would be undesirable) provides the proper
information for
Hallo, Chris,
Du meintest am 08.05.11:
information for NetBIOS and WINS.
And fix the name resolve order in
smb.conf (you have a typo - hosts instead of host).
In smb.conf:
name resolve order = wins host bcast
Lastest log with log level = 3 (cat log.nmbd |grep BARTEKR -B1)
[2011/05/09 20:23:30.422987, 3]
nmbd/nmbd_namelistdb.c:250(add_name_to_subnet)
add_name_to_subnet: Added netbios name BARTEKR20 with first IP
192.168.7.121 ttl=299211 nb_flags=44 to subnet WINS_SERVER_SUBNET
--
[2011/05/09
W dniu 07.05.2011 22:25, Chris Smith pisze:
Try changing the above parameters.
Eliminate, or comment out:
===
# socket options = TCP_NODELAY SO_SNDBUF=16384 SO_RCVBUF=16384
===
Change the rest to either:
or
So it is Windows XP workstations to blame or maybe there is another
thing that i should check ?
Bartek R.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
On Sun, May 8, 2011 at 1:59 PM, BartekR bojle...@gmail.com wrote:
So it is Windows XP workstations to blame or maybe there is another thing
that i should check ?
I run several Samba installations with no such issues with XP. So
unless your XP installs are tweaked in some weird fashion I
Hello!
I have small network in my work. Workstations that connects to it runs
various kind of OS. This includes:
1x Windows 95 (Brother Printer)
8x Windows XP =problematic!
2x Windows Visa
2x Windows 7
1x Samba 3.5.8 (WINS,DNS, supose to be LMB)
There is a serious problem with a browselist
On Sat, May 7, 2011 at 3:38 PM, BartekR bojle...@gmail.com wrote:
socket options = TCP_NODELAY SO_SNDBUF=16384 SO_RCVBUF=16384
security = share
os level = 255
domain master = no
preferred master = yes
Try changing the above parameters.
Eliminate, or comment out:
: [Samba] Samba 3.5.8 / Windows error and system
errors while mapping network drive on some PC's
On Fri, Apr 15, 2011 at 12:36 PM, Dodson, Eric (COT)
ericn.dod...@ky.gov wrote:
Problem: We have a share defined using Samba 3.5.8 on AIX
6.1. Several
people can map a Windows Network Drive
Windows clients have:
Microsoft network client: Digitally sign communications (always) set
to Disabled
Our newer, failing-to-map-to-Samba Windows clients have:
Microsoft network client: Digitally sign communications (always) set
to Enabled
When I toggle the setting on the client and reboot
On Fri, Apr 15, 2011 at 12:36:04PM -0400, Dodson, Eric (COT) wrote:
Problem: We have a share defined using Samba 3.5.8 on AIX 6.1. Several
people can map a Windows Network Drive to the share and it works fine.
Several other people get Windows errors or system errors when trying to
map a drive
Problem: We have a share defined using Samba 3.5.8 on AIX 6.1. Several
people can map a Windows Network Drive to the share and it works fine.
Several other people get Windows errors or system errors when trying to
map a drive to the same share.
Command line errors (from the net use command):
On Fri, Apr 15, 2011 at 12:36 PM, Dodson, Eric (COT)
ericn.dod...@ky.gov wrote:
Problem: We have a share defined using Samba 3.5.8 on AIX 6.1. Several
people can map a Windows Network Drive to the share and it works fine.
Several other people get Windows errors or system errors when trying to
Hello,
I have been fighting with this particular problem for almost week.
I didnot find any solution till today!
I would like to share this one with you to help.
The network:
1. Samba PDC server (OpenSuse 11.2 - samba 3.4.3-3.6.1)
2. Windows 7 Pro 64bit clients
3. A lot
Hi,
I'm trying to configure a Domain trust between Samba 3.5.6 (TEST domain)
and Windows 2008 r2 (WTEST Domain). Samba is the trusting side and Windows
is the trusted side. I created the incoming trust in the W2K8 called TEST.
Then I executed the net rpc trustdom establish WTEST and got:
Enter
: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im
Auftrag von Götz Reinicke - IT-Koordinator
Gesendet: Dienstag, 1. Februar 2011 15:53
An: samba@lists.samba.org
Betreff: [Samba] Samba, LDAP, Windows XP - force passwordchange on first
login
Hello,
I was looking for the right
Hello,
I was looking for the right ldap attribute and setting to force users to
change there password when they log in for the first time.
Can somewone point me to the syntax or doc I did not found yet?
samba 3.5.4 and openldap-2.4.19
Thanks and regards,
--
Götz Reinicke
IT-Koordinator
Tel.
@lists.samba.org
Subject: Re: [Samba] Samba + Winbind + Windows 2003 AD
Hi Micheal
Sorry for not sending that information in the first place, but I though
that it was so basic that it wasn't necessary.
My nsswitch.conf:
# cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service
2010
Betreff: AW: Re: [Samba] Samba + Winbind + Windows 2003 AD
Hi Michael,
which version of Samba do you have?
Are you able to post your Samba configuration?
Thank you.
Tobias
Mit freundlichen Grüßen
Tobias Mucke
LFK-Lenkflugkörpersysteme GmbH
Serverpool, FCI4
Landshuter Straße 26
...@lists.samba.org] Im
Auftrag von Necos Secon
Gesendet: Montag, 19. Juli 2010 01:50
An: samba@lists.samba.org
Betreff: Re: [Samba] Samba + Winbind + Windows 2003 AD
I accidentally deleted the first set of messages in my email for this thread,
but does your DNS resolve properly? What does your resolv.conf look
: [Samba] Samba + Winbind + Windows 2003 AD
I accidentally deleted the first set of messages in my email for this
thread, but does your DNS resolve properly? What does your resolv.conf look
like? Also, what do these files look like:
krb5.conf
smb.conf
There's an option in smb.conf, winbind
from handheld via BlackBerry Server.
Von: Michael Lyon mjl...@gmail.com
An: Mucke, Tobias, FCI4; samba@lists.samba.org samba@lists.samba.org
Gesendet: Mon Jul 19 14:22:37 2010
Betreff: Re: [Samba] Samba + Winbind + Windows 2003 AD
I'm in a 2k8 r2 domain
Gesendet: Mon Jul 19 14:22:37 2010
Betreff: Re: [Samba] Samba + Winbind + Windows 2003 AD
I'm in a 2k8 r2 domain with SFU and home shells managed through the ADUC
console. I'm using Samba/WInbind and use samba shares as user home
directories that are mounted at login-time on Windows 7
) to keep the clocks in sync.
Hopefully, that helps some.
Date: Mon, 19 Jul 2010 11:22:15 -0500
From: mjl...@gmail.com
To: samba@lists.samba.org
Subject: Re: [Samba] Samba + Winbind + Windows 2003 AD
In all honesty, this is my first time using a binary samba package (I am a
native slackware user
Commercial Register: Amtsgericht Ingolstadt, HRB 4365
-Original Message-
From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On
Behalf Of Henrik Dige Semark
Sent: Sunday, July 18, 2010 1:35 AM
To: samba@lists.samba.org
Subject: [Samba] Samba + Winbind + Windows 2003
: Sunday, July 18, 2010 1:35 AM
To: samba@lists.samba.org
Subject: [Samba] Samba + Winbind + Windows 2003 AD
Hey out there.
I have to join my UNIX server with an existing Win2k3 AD network.
My system info:
Debian Lenny
Samba - 3.4.8
Winbind - 3.4.8
Windows Server 2003 with 2000-style-AD
My problem
On 18 July 2010 01:34, Henrik Dige Semark h...@semark.dk wrote:
Hey out there.
I have to join my UNIX server with an existing Win2k3 AD network.
My system info:
Debian Lenny
Samba - 3.4.8
Winbind - 3.4.8
Windows Server 2003 with 2000-style-AD
My problem is that, I have en UNIX server
18-07-2010 17:03, Michael Wood skrev:
On 18 July 2010 01:34, Henrik Dige Semarkh...@semark.dk wrote:
Hey out there.
I have to join my UNIX server with an existing Win2k3 AD network.
My system info:
Debian Lenny
Samba - 3.4.8
Winbind - 3.4.8
Windows Server 2003 with 2000-style-AD
My
for getent to function properly. There is a corresponding option for
groups as well. Look at them and let us know.
Date: Mon, 19 Jul 2010 01:12:41 +0200
From: h...@semark.dk
To: esiot...@gmail.com
CC: samba@lists.samba.org
Subject: Re: [Samba] Samba + Winbind + Windows 2003 AD
Hi Micheal
Hey out there.
I have to join my UNIX server with an existing Win2k3 AD network.
My system info:
Debian Lenny
Samba - 3.4.8
Winbind - 3.4.8
Windows Server 2003 with 2000-style-AD
My problem is that, I have en UNIX server that have to run auth up
against our existing windows 2003 AD.
I
I have setup Samba 3.4.7 as a network file server for a Windows XP machine and
have the basic sharing working. For my Windows files, I would like to preserve
the attributes and create/modify dates and my searches have found some mention
of modifying Samba to accomplish this. Has anyone made
On Fri, Jan 22, 2010 at 12:54 AM, Martin Hochreiter linux...@wavenet.atwrote:
Am 2010-01-21 23:42, schrieb Jeremy Allison:
On Thu, Jan 21, 2010 at 07:50:53PM +, nf-vale wrote:
Is this issue only related with Windows 7 clients or does it affect other
Windows versions too (I'm using
On Wed, Apr 21, 2010 at 06:45:24PM -0600, Robert LeBlanc wrote:
On Fri, Jan 22, 2010 at 12:54 AM, Martin Hochreiter
linux...@wavenet.atwrote:
Am 2010-01-21 23:42, schrieb Jeremy Allison:
On Thu, Jan 21, 2010 at 07:50:53PM +, nf-vale wrote:
Is this issue only related with
change the properties of the file, making it
readable?
Also, we found the running the same application from Linux through an NFS mount
or from a Windows workstation to a Windows server, the file was served as
expected.
It seems like Windows-to-Windows somehow enables buffered reading where
Windows
.
It seems like Windows-to-Windows somehow enables buffered
reading where Windows-to-Samba does not. We can't find
any obvious Samba settings that would make this work and
it doesn't seem to be a Windows issue.
Can you please create a network trace of the
Windows-Windows transfer as well
was served
as expected.
It seems like Windows-to-Windows somehow enables buffered reading where
Windows-to-Samba does not. We can't find any obvious Samba settings that
would make this work and it doesn't seem to be a Windows issue.
Has anybody seen anything like this or have any ideas
On 2010-03-24 02:10, David Harrison wrote:
Here is my smbldap-tools configuration in smb.conf:
add machine script = /usr/sbin/smbldap-useradd -w %u
Is your add machine script directive similar/the same?
Hi David
Mine looked like this:
add machine script = /usr/sbin/smbldap-useradd -i
On 03/29/2010 6:38 AM, Torkil Svensgaard wrote:
On 2010-03-24 02:10, David Harrison wrote:
Here is my smbldap-tools configuration in smb.conf:
add machine script = /usr/sbin/smbldap-useradd -w %u
Is your add machine script directive similar/the same?
Hi David
Mine looked like this:
...@yahoo.com
To: samba@lists.samba.org
Sent: Mon, March 22, 2010 7:05:57 AM
Subject: Re: [Samba] Samba 3.4 Windows 95/98 logon problem
The domain controller is an old NT4, not the samba server. The password there
works fine because the machines can connect to the PDC's shares no problem. The
key
Hi list
I'm running a Samba PDC on Ubuntu Lucid (3.4.7) and am unable to join
Windows 7 machines to the domain. I have applied the registry changes
described at http://wiki.samba.org/index.php/Windows7
Windows XP machines can join with no problems.
Samba log:
stty: standard input:
Are you sure this is a Windows 7 fault?
By the looks of the Samba log smbldap-tools is causing the grief.
Have you confirmed smbldap-useradd is working from the terminal?
You could also try adding the machine account to your LDAP server prior to
joining it to the domain from the desktop.
David
No, I'm not sure, but given that Windows XP machines can join with no
problems (and thus smdldap-useradd is working, in this case), at the
very least Windows 7 is doing something differently.
The Windows 7 machine actually does end up on the LDAP server, as
subsequent attempts to join
You could try turning up the log level in smb.conf so that you can see what
Windows 7 is passing to Samba, and in turn what it is sending to
smbldap-tools (sorry I don't know what level this will require).
For reference, at one site with quite a few Windows 7 clients I am running
Ubuntu Server
My initial assumption about Windows XP was wrong, I can't join with that
either, it just seemed that way. I failed to notice that removing the
machine from the domain from within XP didn't actually remove it from
the LDAP server and thus when I rejoined it apparently used the existing
account
Here is my smbldap-tools configuration in smb.conf:
add user script = /usr/sbin/smbldap-useradd -m %u
ldap delete dn = Yes
add machine script = /usr/sbin/smbldap-useradd -w %u
add group script = /usr/sbin/smbldap-groupadd -p %g
add user to group script = /usr/sbin/smbldap-groupmod
@lists.samba.org
Sent: Sun, March 21, 2010 1:37:10 PM
Subject: Re: [Samba] Samba 3.4 Windows 95/98 logon problem
try to reset the password for the users using w95/98. it usually works.
Le 21/03/2010 13:42, selcuko a écrit :
Hi,
we have just upgraded one of our very old Linux/Samba servers to version
:
http://old.nabble.com/Samba-3.4-Windows-95-98-logon-problem-tp27945229p27945229.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/options/samba
or not smbclient(8) and other samba
client tools will attempt to authenticate itself to servers using the
weaker LANMAN password hash. If disabled, only server which support NT
password hashes (e.g. Windows NT/2000, Samba, etc... but not Windows
95/98) will be able to be connected from the Samba
I am not at all familiar with the use of Windows 9x clients, but I
suppose that you also need to include the following:
lanman auth = Yes
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
...@yahoo.com
Cc: samba@lists.samba.org
Sent: Sun, March 21, 2010 9:08:10 AM
Subject: Re: [Samba] Samba 3.4 Windows 95/98 logon problem
we have just upgraded one of our very old Linux/Samba servers to version
3.4.2. After the upgrade, the Windows 95/98 clients cannot login to the
server anymore
Please search the list archives. I am sure that your question has
already been addressed here.
It is possible to make it work.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
On 2010/03/21 05:42 (GMT-0700) selcuko composed:
we have just upgraded one of our very old Linux/Samba servers to version
3.4.2. After the upgrade, the Windows 95/98 clients cannot login to the
server anymore. In the log I see 'NT_STATUS_ACCESS_DENIED' messages for
these clients.
The samba
try to reset the password for the users using w95/98. it usually works.
Le 21/03/2010 13:42, selcuko a écrit :
Hi,
we have just upgraded one of our very old Linux/Samba servers to version
3.4.2. After the upgrade, the Windows 95/98 clients cannot login to the
server anymore. In the log I see
John Drescher wrote:
Yes. They work fine together. You need samba-3.3.X or greater. 3.4.X
does not allow printing under 64 bit clients but 3.3 or 3.5 are good.
I was about to upgrade from 3.3 to 3.4 until I read that. Is the 64-bit
printing issue going to be fixed in the 3.4 series?
Moray.
To
Yes. They work fine together. You need samba-3.3.X or greater. 3.4.X
does not allow printing under 64 bit clients but 3.3 or 3.5 are good.
I was about to upgrade from 3.3 to 3.4 until I read that. Is the 64-bit
printing issue going to be fixed in the 3.4 series?
Fixed in the 3.5 series
Are there any changes I need to implement on the Windows 7 Clients to get
them to see Samba Shares??
Seeing the shares even worked with the unsupported/deprecated 3.0.36
with no changes.
Joining the domain requires 3.3.X and above and the registry entries.
John
--
To unsubscribe from this
On 03/04/2010 03:22 AM, Moray Henderson wrote:
John Drescher wrote:
Yes. They work fine together. You need samba-3.3.X or greater. 3.4.X
does not allow printing under 64 bit clients but 3.3 or 3.5 are good.
I was about to upgrade from 3.3 to 3.4 until I read that. Is the 64-bit
printing
On Thu, Mar 04, 2010 at 09:22:56AM +, Moray Henderson wrote:
John Drescher wrote:
Yes. They work fine together. You need samba-3.3.X or greater. 3.4.X
does not allow printing under 64 bit clients but 3.3 or 3.5 are good.
I was about to upgrade from 3.3 to 3.4 until I read that. Is the
Jeremy Allison wrote:
Yes. They work fine together. You need samba-3.3.X or greater. 3.4.X
does not allow printing under 64 bit clients but 3.3 or 3.5 are
good.
I was about to upgrade from 3.3 to 3.4 until I read that. Is the
64-bit
printing issue going to be fixed in the 3.4 series?
Yes,
Hello everyone I am new to this mailing list,
I wish to setup a PDC at home using Samba and LDAP, my main concern is that I
have a few Windows 7 machines which will be joining the Domain. I researched a
few forums and have seen that people have been having trouble with getting 7
and Samba to
On Tue, Mar 2, 2010 at 1:20 PM, Ally Biggs bluechr...@hotmail.co.uk wrote:
Hello everyone I am new to this mailing list,
I wish to setup a PDC at home using Samba and LDAP, my main concern is that I
have a few Windows 7 machines which will be joining the Domain. I researched
a few forums
beautifully in an AD domain, just not
as controller.
-Original Message-
From: samba-boun...@lists.samba.org [mailto:samba-
boun...@lists.samba.org] On Behalf Of Mercier
Sent: Friday, February 12, 2010 6:41 AM
To: samba@lists.samba.org
Subject: [Samba] SAMBA and Windows 2008 TSE licence
On Fri, Feb 12, 2010 at 3:40 PM, Mercier
julien.merc...@pays-saint-marcellin.fr wrote:
I can't use the TSE licence server in Windows 2008 server. This Server is
member of my Samba Domain. My TSE licence server is actived and my licences
added, but when i want configure the TSE service and
1 - 100 of 323 matches
Mail list logo
