Re: [Samba] Re: Unusable performance over WAN (part 2)

[Stuart Highlander]

James Lamanna wrote:

On 10/8/07, Mike Eggleston <[EMAIL PROTECTED]> wrote:

On Mon, 08 Oct 2007, James Lamanna might have said:


So as it turns out, apparently it was a window scaling issue.
Turning on an excessively large window size on the routers (thereby
enabling dynamic TCP window scaling) seems to have fixed the issue. I
now get transfer rates around 130-160k/s.

Great. For hysterical porpoises please document what specific changes
you made on the windows boxes and what specific changes you made on
your router.

Mike



The only change I made on the routers was I added the global
configuration command (both Cisco routers btw)
ip tcp window-size 75

-- James


Is 75 a good value.

My router says the valid range is 0-65535.

Stu
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Add route

[Stuart Highlander]

add the following line to /etc/rc.local

/sbin/route add -net 10.19.1.0/24 10.19.1.254

where 10.19.1.254 is the gateway

to add a route to a host:

/sbin/route add -host 192.168.0.5 192.168.1.254

where 192.168.0.5 is the host and 192.168.1.254 is the gateway.

Jamie Beekhuis wrote:

I have added an add route command to my firewall and everthing is working
fine. But when I reboot I lose the route ,
What file can I edit to make the route permanent. (BSD Version 6.1 Release)

Jamie


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Access From another subnet

[Stuart Highlander]

shawn,

is the server on the 1.x network set as the wins server on the 2.x 
clients or is there another wins server set?


stu

Jim Hogan wrote:


Shawn,

Shawn Simmons wrote:

I have setup a Samba Server to be used as a documentation 
repository.  The

IP address of the server resides in 192.168.1.x
 


I have several Windows XP workstations that reside in the 192.168.1.x
network and have no problem accessing the shares on the Samba Server.
 


I have several Windows XP workstations that reside in the 192.168.2.x
network that will show the Samba Server in the network neighborhood;
however, I get "access denied" errors trying to access it.
  


These are two private networks.  What is the route between the 
networks?  Any network address translation/NAT at any point?


Jim

 


The following is my smb configuration:

 

# smb.conf is the main Samba configuration file. You find a full 
commented


# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the

# samba-doc package is installed.

# Date: 2006-06-16

[global]

  workgroup = PRECISIONARCH

  printing = cups

  printcap name = cups

  printcap cache time = 750

  cups options = raw

  map to guest = Bad User

  include = /etc/samba/dhcp.conf

  logon path = \\%L\profiles\.msprofile

  logon home = \\%L\%U\.9xprofile

  logon drive = P:

  idmap gid = 1-2

  idmap uid = 1-2

  realm = PRECISIONARCH.COM

  security = ADS

  template homedir = /home/%D/%U

  template shell = /bin/bash

  winbind refresh tickets = yes

  domain logons = No

  domain master = No

  passdb backend = smbpasswd

  wins support = No

  winbind offline logon = yes

  add machine script = /usr/sbin/useradd  -c Machine -d 
/var/lib/nobody

-s /bin/false %m$

  usershare max shares = 100

  hosts allow = 192.168.1. 192.168.2.

  server string= Document-Server

[homes]

  comment = Home Directories

  valid users = %S, %D%w%S

  browseable = No

  read only = No

  inherit acls = Yes

[profiles]

  comment = Network Profiles Service

  path = %H

  read only = No

  store dos attributes = Yes

  create mask = 0600

  directory mask = 0700

[users]

  comment = All users

  path = /home

  read only = No

  inherit acls = Yes

  veto files = /aquota.user/groups/shares/

[groups]

  comment = All groups

  path = /home/groups

  read only = No

  inherit acls = Yes

[printers]

  comment = All Printers

  path = /var/tmp

  printable = Yes

  create mask = 0600

  browseable = No

[print$]

  comment = Printer Drivers

  path = /var/lib/samba/drivers

  write list = @ntadmin root

  force group = ntadmin

  create mask = 0664

  directory mask = 0775

[netlogon]

  comment = Network Logon Service

  path = /var/lib/samba/netlogon

  write list = root

 

could someone please help me determine why the computers on the 
192.168.2.x

subnet cannot access the Samba server.  Thanks.

  




--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] replacing samba server

[Stuart Highlander]

No ldap.

John Drescher wrote:


On 1/3/07, Stuart Highlander <[EMAIL PROTECTED]> wrote:


good morning,

i am currently running samba version 3.0.23a on fedora core 4 linux as a
pdc.

i would like to convert the server to centos linux due to the death of
the fedora legacy project..

i think that the process to do this, as it pertains to samba, would
follow the process to replace a samba pdc.

can someone point me to the link of a howto that would aid me in
replacing a samba pdc, i.e., what files need to be backed up,
importing/exporting sid's, etc...?


Does your samba pdc use ldap? If so is the ldap server on the same
machine or a different box?

John


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] replacing samba server

[Stuart Highlander]

good morning,

i am currently running samba version 3.0.23a on fedora core 4 linux as a 
pdc.


i would like to convert the server to centos linux due to the death of 
the fedora legacy project..


i think that the process to do this, as it pertains to samba, would 
follow the process to replace a samba pdc.


can someone point me to the link of a howto that would aid me in 
replacing a samba pdc, i.e., what files need to be backed up, 
importing/exporting sid's, etc...?


thank you,

stuart
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] wins browsing issue

[Stuart Highlander]

- Original Message - 
From: "John H Terpstra" <[EMAIL PROTECTED]>
To: 
Sent: Wednesday, August 24, 2005 10:01 AM
Subject: Re: [Samba] wins browsing issue


> On Wednesday 24 August 2005 08:19, Stuart Highlander wrote:
> > good morning all,
> >
> > i have an interesting issue with browsing.
> >
> > details:
> > i have three subnets.  (subnet1, subnet2, and subnet3)
> > i have a samba server on each subnet. (samba1, samba2, and samba3)
> > i have a windows 2000 server on subnet1.  (m$1)
>
> I have not read in detail through this email, but as a first step, rename
the
> M$1 machine to a name that does not contain the '$' character. The '$'
> character has special significance in Windows networking. Do not use this
is
> on machine name.
>
> - John T.
>
> > samba1 is the domain master and wins server with ip 192.168.0.1
> > win2k clients authenticate to their local server and wins is set to
> > 192.168.0.1.
> >
> > when i run a net view \\m$1 from a win2k client on subnet2 or subnet3, i
> > get "system error 53 has occurred.  the network path was not found."
> > message.
> >
> > when i run a net view \\samba1 or \\samba2 from the same win2k client,
> > everything is fine. (shared resources at )
> >
> > when i run a net view \\m$1 from a win2k client on subnet1, everything
is
> > fine. (shared resources at )
> >
> > pertinent information from smb.conf of samba1
> > os level = 65
> > name resolve order = wins host lmhosts bcast
> > domain logons = yes
> > preferred master = yes
> > domain master = yes
> > wins support = yes
> >
> > pertinent information from smb.conf of samba2 and samba3
> > os level = 65
> > name resolve order = wins host lmhosts bcast
> > domain logons = yes
> > preferred master = yes
> > domain master = no
> > wins server = 192.168.0.1
> > local master = yes
> >
> > m$1 appears in browse.dat on both samba2 and samba3.
> >
> > any ideas?
> >

i am sorry john.  the name of the win2k box is ms1 and not m$1.  i was
trying to be cute.

i apologize to all.

stu

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] wins browsing issue

[Stuart Highlander]

good morning all,

i have an interesting issue with browsing.

details:
i have three subnets.  (subnet1, subnet2, and subnet3)
i have a samba server on each subnet. (samba1, samba2, and samba3)
i have a windows 2000 server on subnet1.  (m$1)
samba1 is the domain master and wins server with ip 192.168.0.1
win2k clients authenticate to their local server and wins is set to
192.168.0.1.

when i run a net view \\m$1 from a win2k client on subnet2 or subnet3, i get
"system error 53 has occurred.  the network path was not found." message.

when i run a net view \\samba1 or \\samba2 from the same win2k client,
everything is fine. (shared resources at )

when i run a net view \\m$1 from a win2k client on subnet1, everything is
fine. (shared resources at )

pertinent information from smb.conf of samba1
os level = 65
name resolve order = wins host lmhosts bcast
domain logons = yes
preferred master = yes
domain master = yes
wins support = yes

pertinent information from smb.conf of samba2 and samba3
os level = 65
name resolve order = wins host lmhosts bcast
domain logons = yes
preferred master = yes
domain master = no
wins server = 192.168.0.1
local master = yes

m$1 appears in browse.dat on both samba2 and samba3.

any ideas?

stu

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] smbd/service.c:make_connection_snum(xxx) connect to service initially as user root (uid=0, gid=100) messages

[Stuart Highlander]

- Original Message - 
From: "Gerald (Jerry) Carter" <[EMAIL PROTECTED]>
To: "Stuart Highlander" <[EMAIL PROTECTED]>
Cc: 
Sent: Friday, June 24, 2005 12:07 PM
Subject: Re: [Samba] smbd/service.c:make_connection_snum(xxx) connect to
service initially as user root (uid=0, gid=100) messages


> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Stuart Highlander wrote:
>
> > smbd/service.c:make_connection_snum(642) WKSTN-02 (192.168.3.11) connect
to
> > service Images initially as user root (uid=0, gid=100) (pid 26901) : 1
> > Time(s)
>
> Do you have an 'admin users' line configured in smb.conf somewhere?
> If so , then I would expect this as normal.
>
>
>
>
>
> cheers, jerry

thanks for your reply,

i figured out what i did to cause the messages.

on the samba share, i set force user= root.

thank you for the help,

stuart

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] smbd/service.c:make_connection_snum(xxx) connect to service initially as user root (uid=0, gid=100) messages

[Stuart Highlander]

good afternoon all,

specifics:
samba server version 3.0.10-1, role_domain_pdc on fc3 named main, ip
192.168.3.1.  main is also designated as wins server.

samba server version 3.0.14a, role_domain_member server on fc3 named
support, ip 192.168.3.2. security=domain, password server= main.

support successfully joined to domain.

win2k clients.

all users are able to save files to the share on support and everything
works fine.

the following appears in Logwatch of support:

smbd/service.c:make_connection_snum(642) WKSTN-02 (192.168.3.11) connect to
service Images initially as user root (uid=0, gid=100) (pid 26901) : 1
Time(s)

is this just noise or an example of a mis-configuration?

thank you,

stuart

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Problem with smbmount and windows xp

[Stuart Highlander]

- Original Message - 
From: "Christian Punke" <[EMAIL PROTECTED]>
To: 
Sent: Wednesday, June 22, 2005 9:42 AM
Subject: [Samba] Problem with smbmount and windows xp


> For long time I used to smbmount my windows-xp share from my SuSE-Linux
> machine with smbmount from samba 2.2.12.
>
> Now I changed to debian-linux with samba 3.0.13.
>
> The smbmount-cmd: ' smbmount //winxp/share /unix-dir -o
> username=user,password=xxx,ro' returns no error.
> with 'mount' I see the mounted win-share.
> But when I try a 'ls /unixdir' I get a 'Permission denied' error, same
> while using 'df'.
>
> The permission on the windows-share are: everyone:full control.
> The permission on the unixdir are: drwxrwxrwx and I'm the owner of the
> directory.
> All commands given under 'root'-account.
> smbclient -L -N -U username works fine.
>
> I tried to smbmount and access a Win-NT4-share with smbmount V3.0.13
> from my debian successfully.
>
> Anybody any ideas 
>
>
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba

i had to change the permissions on the mount point to get mine to work.
originally they were 755.  i changed them to 777, mounted the share, ls'd,
and everything was fine.  umounted the share, reset the permissions to 755
on the mount point, remounted the share, ls'd, and everything was fine.

i am using fc3.

a friend of mine had the same problem with fc3 mounting win2003 sp1.  he
followed above process and everything is fine now.

stu

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] updating samba via rpm

[Stuart Highlander]

- Original Message - 
From: "Paul Gienger" <[EMAIL PROTECTED]>
To: "'Ian Clancy'" <[EMAIL PROTECTED]>; "'Stuart Highlander'"
<[EMAIL PROTECTED]>
Cc: 
Sent: Thursday, June 09, 2005 9:50 AM
Subject: RE: [Samba] updating samba via rpm


> > I can't remember exactly, but i think gnome-vfs2-smb depends on
> > samba-common. Other gnome rpm's depend on gnome-vfs2-smb etc 
> > The rpm from the site provides one rpm package :
> > samba-3.0.14a-1
>
> Really? Last time recompiled the samba spec file, I was given 4 rpm files,
> just like the RH/Fedora implementation.  The spec file states that it came
> from:
>
> URL: http://www.samba.org/
>
> Source: ftp://www.samba.org/pub/samba/%{name}-%{version}.tar.bz2
>
>
> > If your not bothered about using gnome you can uninstall the Fedora
> > Samba rpm's (stop samba first of course):
> > rpm --nodeps -e samba samba-common samba-client
>
> Why oh why people insist on jeopardizing their rpm db integrity when
> perfectly sane options exist...  yes you're putting in the same files, but
> now anything that was depending on samba-common, or any other package that
> used to be there, is going to be confused when it goes looking for its
> dependencies.  Hrm, yum wants to update gnome-vfs (or whatever else) and
> samba isn't installed...  it may either install old versions or break
> entirely and update nothing.
>
> Compile the spec and then in one line:
>
> Rpm -Uvh samba-3.0.14a-1.i386.rpm samba-client-3.0.14a-1.i386.rpm
> samba-common-3.0.14a-1.i386.rpm samba-swat-3.0.14a-1.i386.rpm
>
> Leave out the swat if you so desire and/or the h option if you don't like
> the progress bar.
>
>
> > then install the rpm from samba.org
> > rpm -Uvh samba-3.0.14a-1.i386.rpm
> >
> > One thing to look out for. What was previously located in
> > /var/cache/samba is now located in /var/lib/samba.
> > regards

thanks to all who have responded to my original post.

i have read the document regarding the src rpm's and it confirms what paul
stated in his reply regarding the use of the rpm command..

in my previous post, i stated that i use  rpm -Fvh.  paul's reply and other
documentation stated to use rpm -Uvh.  the only difference i see is that
rpm -Fvh updates the package if it is installed and rpm -Uvh updates the
package.  i will use the rpm -Uvh on my test samba server and see how it
goes.

has anyone seen any serious issues, gotchas, better-do's, or suggestions,
when updating from version 3.0.10-1 to version 3.0.14a-1?

thank you for your help,

stuart

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] updating samba via rpm

[Stuart Highlander]

good afternoon,

current status:
samba pdc running samba 3.0.10-1.fc3 on fedora core 3 on a dell server.
clients are windows 2000 pro workstations.
authentication is via tdbsam.

pretty vanilla setup.  no active directory, ldap, winbind, etc.

i have downloaded the rpm's from samba.org for current stable release samba
3.0.14a-1.  usually  i perform upgrades to samba server using rpm -Fvh
samba-*, with this set of rpm's the update does not run using the rpm -Fvh
command.

i do recall list traffic that did not recommend upgrading this way, but have
not had any problems in the past doing it this way.

could someone steer me to documentation that would help me upgrade the samba
software via rpm?

i have downloaded and read the samba pdf manuls by john terpstra, jelmer
vernooij, and jerry carter (excellent reading), but did not find my specific
issue.

thank you,

stuart

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Sarbanes-Oxley headaches

[Stuart Highlander]

- Original Message - 
From: "John H Terpstra" <[EMAIL PROTECTED]>
To: 
Sent: Monday, May 16, 2005 9:17 AM
Subject: Re: [Samba] Sarbanes-Oxley headaches


> On Monday 16 May 2005 07:50, Stuart Highlander wrote:
> > > I gather that OP would be better served by using a tdb or ldap
backend.
> >
> > i am not the original poster, but did ask the question regarding account
> > lockout and reset using the smbpasswd backend.
> >
> > i agree that moving to ldap or tdb would better suit my needs but i do
not
> > have the test environment nor the time to move and adequately test my
> > production environment to one or the other right now.
> >
> > since i am using the smbpasswd for the foreseeable future, are the
account
> > lockout and reset features applicable to using the smbpasswd backend?
if
> > not, it is ok.  my guess is that they are not, but cannot find
> > documentation to verify this.
> >
> > as for sox, i found a free program that enables window$ boxes to log
event
> > logs to a remote syslog server, found here:
> >
> >  http://www.netadmintools.com/art284.html
>
> The advanced Windows account facilities are available only with the tdbsam
or
> ldapsam backends. It is very easy to migrate to tdbsam. Here are the
steps:
>
> 1. Edit smb.conf to include this line:
> passdb backend = tdbsam
> 2. Migrate your smbpasswd file to tdbsam:
> pdbedit -i smbpasswd -e tdbsam
>
> Done.
>

thank you for the information on converting to tdbsam.

where in the docs would it discuss changing passwords?

stu

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Sarbanes-Oxley headaches

[Stuart Highlander]

- Original Message - 
From: "Craig White" <[EMAIL PROTECTED]>
To: 
Sent: Saturday, May 14, 2005 9:12 AM
Subject: Re: [Samba] Sarbanes-Oxley headaches


> On Sat, 2005-05-14 at 10:44 +0200, Tony Earnshaw wrote:
>
> >
> > > i am currently using samba version 3.0.7 with smbpasswd.
> > >
> > > does the account lockout feature not work with smbpasswd?
> >
> > smbpasswd doesn't have anything to do with this, it's used for setting /
> > synchronizing passwords. Perhaps you meant smbclient; yes it works both
> > for Windows (XP Pro in my case) and smbclient.
> >
> 
> smbpasswd is not just a command but also a backend storage type for user
> accounts & passwords.
>
>  Collection/passdb.html#id2552851>
>
> I gather that OP would be better served by using a tdb or ldap backend.
>

i am not the original poster, but did ask the question regarding account
lockout and reset using the smbpasswd backend.

i agree that moving to ldap or tdb would better suit my needs but i do not
have the test environment nor the time to move and adequately test my
production environment to one or the other right now.

since i am using the smbpasswd for the foreseeable future, are the account
lockout and reset features applicable to using the smbpasswd backend?  if
not, it is ok.  my guess is that they are not, but cannot find documentation
to verify this.

as for sox, i found a free program that enables window$ boxes to log event
logs to a remote syslog server, found here:

 http://www.netadmintools.com/art284.html

stu

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: **** SPAM **** 6.5: Re: [Samba] Re: nazi spam in German overlist address

[Stuart Highlander]

- Original Message - 
From: "Gerald (Jerry) Carter" <[EMAIL PROTECTED]>
To: "Kevin M. Barrett" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, May 16, 2005 8:09 AM
Subject: Re:  SPAM  6.5: Re: [Samba] Re: nazi spam in German
overlist address


> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Kevin M. Barrett wrote:
> |
> | Has any consideration been made to converting the
> | list to a forum?
>
> There's already Samba forums around so another one
> would not be extremely helpful IMO.  Plus the preference
> for forum vs. mailing list is linked to personality, time
> constraints, etc
>
> Converting this list to a forum would significantly
> change the dynamic and then someone would just create
> another mailing list :-)
>

for what it is worth:

i say keep things like they are, tweek the filter if possible, and i will
just clean out the inbox of the junk.  it is a minor inconvenience, but only
just that.

the benefits of this list as it is far outweigh the nusiance of spam.

stu


stu

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] help

[Stuart Highlander]

here is how i do it.  there may be a better way.

1.  mount the windows box from the linux box:
/bin/mount -t smbfs -o
username=validusernameonwindowsbox,password=validusernameonwindowsbox'spassw
ord //windowsbox/sharename /unixmountpoint

the values validusernameonwindowsbox, validusernameonwindowsbox'spassword,
windowsbox, sharename, and unixmountpoint are self explanatory.

2.  sync up the files to the backup location on the linux box:
/usr/bin/rsync -av /unixmountpoint/ /backup/windosbox/share

hope this helps.

stu

- Original Message - 
From: "Amani Makala" <[EMAIL PROTECTED]>
To: 
Sent: Tuesday, April 19, 2005 3:16 AM
Subject: [Samba] help


> hi!
> i need to configure a linux backup server, let me give u some hints on the
> real environment, i have one linux machine and two windows machines, now i
> need to make backup of files found on windows machine,but the backup
should
> be done on the linux machine. please anybody who can help me!
> thanks.
>
> -- 
> 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

Fw: [Samba] directory permissions

[Stuart Highlander]

- Original Message - 
From: "Stuart Highlander" <[EMAIL PROTECTED]>
To: "Aubrey King" <[EMAIL PROTECTED]>
Sent: Friday, May 13, 2005 4:46 PM
Subject: Re: [Samba] directory permissions


> aubrey,
>
> when i've run into this kind of problem, it was usually unix file
> permissions that was the hang-up.
>
> this is what i did to solve a problem with permissions on a share named
> "music" and a group that needed permission to write to files in "music"
> named "rockstars":
> create mask = 0770
> directory mask = 0770
> force create mode = 0770
> force directory mode = 0770
>
> i made sure that the group owner for music and recurring directories was
> "rockstars"
>
> this cleared up my issues on shares.
>
> if i am mistaken, please correct me.
>
> stu
>
> in smb.conf where i defined "music", i put the following:
>
> - Original Message - 
> From: "Aubrey King" <[EMAIL PROTECTED]>
> To: 
> Sent: Friday, May 13, 2005 4:38 PM
> Subject: [Samba] directory permissions
>
>
> >
> > I have just finished replacing a client's Windows / Exchange / IIS setup
> > here with Samba / [Postfix, UW Imap] / Apache and I've run into an
issue.
> > In this setup, Samba acts as PDC, so there are NO WINDOWS SERVERS - only
> > win clients.  One of the apps that they run seems to explicitly require
> > that the user own the folder that they are saving to.  In their prior
> > setup, this was easy, as you could set the directory owner to the users
> > group in the domain and everything was happy.  Even though I did this:
> >
> > net groupmap modify ntgroup="Domain Users" unixgroup=users
> >
> > I still cannot set users as the owner.  i even created a user called
users
> > and tried to fake it, but no dice.
> >
> > Ideas?
> >
> > -Aubrey King
> > -- 
> > 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] Sarbanes-Oxley headaches

[Stuart Highlander]

- Original Message - 
From: "Tony Earnshaw" <[EMAIL PROTECTED]>
To: 
Sent: Thursday, May 12, 2005 12:55 PM
Subject: Re: [Samba] Sarbanes-Oxley headaches


> tor, 12.05.2005 kl. 18.54 skrev Robert Kelly:
>
> > With the new scrutinization by auditors on account policies and
> > auditing, how can Samba be SOX compliant?
> > Using 3.0.14a-sernet on Suse 9.1 - ldapsam
> >
> > Specifically, a couple of things seem to be lacking:
> >
> > 1) Logon/Logoff times are not being recorded
> > The last logon time recorded in my ldap entries are pre-nt4 migration.
>
> Bad luck?
>
> > 2) Do the Audit Policy values in user manager have any effect?
> > Are they implemented?
> > Can they be syslogged?
>
> No to both, please read the official Samba HOWTOs. Experiment. Like we
> all have to.
>
> > 3) How can I get a hook into logons?
> > Without turning up the debug values, how can I tell if an account has
> > had repeated login failures?
>
> Try 'man pdbedit' and search for "-P".
>
> I have never understood why people complain about any item of software's
> supposed limitations until they have read and thoroughly understand all
> aspects of all the documentation. Perhaps they aspire toward posthumous
> beatification, attaining al martyrs' brigade status or whatever.
>
> > Thanks,
>
> *Wake up* and at least make *some effort* to read the docs and follow
> the threads and experiment for yourself as 1001 others on this list,
> including the undersigned choose to do. Hanging yourself out is not to
> your own advantage.
>
> --Tonni

i had an examiner yesterday ask similar questions about my system yesterday.
thank you for direction to the pdbedit manpage.

suppose i wanted to set up account lockout for 3 failed login attempts for
my w2k workstations with the ability to try again in 5 minutes.  would these
be the commands to use:

pdbedit -P "bad lockout attempt" -C 3
pdbedit -P "reset count minutes" -C 5

as for logging some of the requests of the original poster, i have found a
free program that will log the windows event log to a remote syslog server.
here is the link:

http://www.netadmintools.com/art284.html

stu

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Question on using smbmount

[Stuart Highlander]

i don't think that i would do it this way.

i use rsync via ssh to accomplish my backups from linux server to linux
serververy fast and easy to setup.

i mount an nt server share to one of my linux boxes using mount -t smbfs,
which uses smbmount, and use rsync "locally" to backup the nt share to one
of my linux boxes.

stu

- Original Message - 
From: "Jason Williams" <[EMAIL PROTECTED]>
To: 
Sent: Tuesday, April 12, 2005 4:24 PM
Subject: Re: [Samba] Question on using smbmount


> After thinking about this, is this even a viable option? I mean mounting
> a share on one linux server (running samba) to another linux server also
> running samba? The whole idea was so I could run a backup of the data on
> a tapedrive.
> Am I looking at this completely wrong?
>
>
> > I'm trying to mount a samba share located on one Linux server to
> > another samba server for backup purposes. The problem im running into
> > is that i get an error stating:
> >
> > couldn't find service 
> >
> > Here is what im attempting:
> >
> > One server #1 sambaserver, Where I want the share to be mounted for
> > backup purposes
> >
> > smbmount //valhalla/backupdir /backuparea/valhalla
> >
> > If im correct, im specifying valhalla (server #2) and backupdir (which
> > is the share i created and specified inside smb.conf.
> >
> > Once I do that, enter the password, I get the error:
> >
> > Apr 12 13:41:16 valhalla smbd[32354]:   sambaserver (192.168.1.51)
> > couldn't find service backupdir/
> >
> > Its right on the tip of my tongue, but its escaping me.
> >
> > Anyone have any suggestions?
> >
> > Thanks.
> >
> > Jason
>
>
> -- 
> 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] Drive Imaging and Domain Membership

[Stuart Highlander]

david,

i think this is a microsoft thing more than a samba issue.

i use a microsoft utility called sysprep on a workstation before i take an
image of it.  it basically takes the image back before the license key input
and machine name input.  i then take an image of the workstation using the
g4u program.  when the imaged machine is booted up, you re-enter the
information this information.  scripts can be written to automate the
process for large deployments.

here is more information on the subject:

http://support.microsoft.com/default.aspx?scid=kb;en-us;302577&sd=tech

i hope this helps.

stuart


- Original Message - 
From: "David Sonenberg" <[EMAIL PROTECTED]>
To: 
Sent: Friday, February 18, 2005 10:28 AM
Subject: [Samba] Drive Imaging and Domain Membership


> In my office we use dd to create harddirve images.  We are getting ready
> to put our Samba PDC/BDC into production.  The question is...  Is there
> a way to create drive images that are already domain members?  My
> understanding is that each domain member must have a unique netbios
> name.  Is there a way to get around this?
>
> -- 
> David Sonenberg
> Systems / Network Administrator
> Stroz Friedberg, LLC
> 15 Maiden Lane
> 15th Floor
> New York, NY 10038
> 212.981.6527 (o) | 917.495.4918 (c)
>
> -- 
> 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] smbd/service.c:make_connection_snum(648) in logs

[Stuart Highlander]

good morning all,

i have a fc2 server running samba 3.0.10-1.

from my daily logwatch i get these type of entries:

smbd/service.c:make_connection_snum(648)  workstation1 (10.19.1.2) connect
to service share1 initially as user user1 (uid=802, gid=512) (pid 28851) : 5
Time(s)

on all shares that user1 connects to, i get the same message identifying the
share (share2, share3, etc...) with same pid number.
the same thing happens with user2 with a different pid number.

the setup is pretty vanilla.
i use smbpasswd to authenticate.
the server is the domain/local master.

smb.conf
[global]
workgroup= office1
netbios name = server1
encrypt passwords = yes
name resolve order = wins hosts lmhosts bcast
login script = scripts\%U.bat
logon path = \\%L\%U\profile
domain logons = yes
os level =65
preferred master = yes
domain master = yes
wins support = yes
local master = true
admin users = admin
load printers = yes
printing = cups
use client driver = yes
printer admin = @admin
unix charset = iso8859-1
log level = 1
use sendfile = no


shares are basic homes, netlogon, printing, and data shares.  nothing
complex.

users are able to access shares, directories, files, read, write, delete,
print with no noticeable problems.

the log entries are my concern.

much ado about nothing?

thank you,

stuart

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Best practices for long-running Samba server

[Stuart Highlander]

misty,

i, too, have experienced some browsing issues since upgrading to samba
3.0.7-2 on an FC1 server.  the server stays up in terms of months than days
(thanks samba team).

restarting smb on the wins server every day seems to have eased this problem
for me. for a baling wire fix, i set up a cron job to restart smb on my
samba wins server when my users are not on my system every day.  this seems
to have "fixed" my browsing issues.

even when i have restarted smb on a server with users on the system, the
effects on my users have been almost nil.  my setup is not very
sophisticated, so i do not know how it would effect your situation.

if you have users on the system all hours of the day, then this may not
help.

stuart

- Original Message - 
From: "Misty Stanley-Jones" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 25, 2005 7:37 AM
Subject: [Samba] Best practices for long-running Samba server


> Hi all,
>
> I have been having the weirdest network browsing problems on my network
the
> past week.  Come to find out the wins.dat file got corrupted.  Removing
that
> file fixed everything.  Because our systems typically have uptimes
measured
> in months rather than days, and it is difficult for me to restart Samba
> except as a scheduled task (which I'm afraid to do because there are users
> who come in earlier than I do in the AM and users that work later than me
in
> the PM, and I don't want them having to call me at home :D ), I need to
know
> what the best practice is for the .dat and .tdb files.  Is it normal for
them
> to become corrupt over time?  Is there some best practice for how often to
> remove them and let them re-populate?  Anything else I should know for a
> Samba instance that typically runs for months on end without interruption?
>
> Thanks in advance,
> Misty
> -- 
> 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] allowing users to change system time

[Stuart Highlander]

ian,

your problem is probably with the local computer policy on the w2k boxes.

on the win2k box, go to start, run, gpedit.msc, Local Computer Policy,
Computer Configuration, Windows Settings, Securty Settings, Local Policies,
User Rights Assignments, Change the System Time.  Add users or authenticated
users to this key.

there may be an easier way, but works for me.

stu


- Original Message - 
From: "Ian Clancy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 01, 2004 4:07 PM
Subject: [Samba] allowing users to change system time


> Greetings Samba users,
> I'm the proud administrator of a samba 3 domain with openldap backend. All
> is well but for one niggling little problem which i hope somebody could
help
> me with ?.
> My pdc is set up as a time server "time server = yes" and I have created a
> logon script with the following entry :
>
> net time \\mypdc /set /yes
>
> Now, when i logon to a windows 2k domain client as Administrator the above
> command sync's the time on the client with the server, no problems.
However
> when ordinary users logon they get the following error :
>
> System error 1314 has occurred.
> A required privilege is not held by the client.
>
> I would like to give the users the privilege to change the time on their
> systems. Does anyone know how i could go about doing this ?. Using the
> usrmgr.exe program i can make a number of changes to the samba domain,
> usfortunately their is not an option to do this ?
> All help , ideas welcome.
> Thanks for your time.
> Ian Clancy
>
> Legal Disclaimer: Any views expressed by the sender of this message are
> not necessarily those of Connaught Electronics Ltd. Information in this
> e-mail may be confidential and is for the use of the intended recipient
> only, no mistake in transmission is intended to waive or compromise such
> privilege. Please advise the sender if you receive this e-mail by mistake.
>
>
>
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] upgrade from 3.0.7-2 to 3.0.9-1 problems

[Stuart Highlander]

good afternoon,

i am running samba 3.0.7-2 on a fedora core 2 servers.

has anyone had any serious problems upgrading from this version to the new
version?

thank you,

stuart

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Server not responding after Samba upgrade

[Stuart Highlander]

Good Morning Dusan,

This sounds similar to a problem I had earlier when upgrading a server and
it involved WINS registration.

Here is what I did to fix my problem:

http://lists.samba.org/archive/samba/2004-September/092466.html

Hope this helps,

Stuart

- Original Message - 
From: "Dusan Djordjevic" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 01, 2004 8:34 AM
Subject: [Samba] Server not responding after Samba upgrade


> Hi all,
>
> I used to run Samba 2.2.9 on Debian Woody. Yesterday I upgraded it (with
> all necessary packages) to 3.0.7. Since then, Samba on that server do
> not respond to netbios queries, only to direct access via IP. Also,
> when I try to resolv its name using nmblookup, I cannot find it.
>
> When I access to server via IP address everything works fine.
>
> Any idea ?
> TIA
> -- 
> Eng. Dusan Djordjevic (RHCE)
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Windows XP - Explorer crashes when I try to open a file ona Samba share

[Stuart Highlander]

- Original Message - 
From: "Lenroc" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 27, 2004 11:18 PM
Subject: [Samba] Windows XP - Explorer crashes when I try to open a file ona
Samba share


I am having problems with my samba clients. I am using Windows XP SP1 to
try to connect to a Samba server I have running on my Gentoo Linux server.

Browsing a share works decently well, but I ocassionally have network
problems (the same timeout issue I explain below).

The real problem comes, though, when I try to access a file (either trying
to open it or just right-clicking on it). As soon as I try, Explorer (the
Windows file browser) locks up hard. Eventually, the title bar of the
windows will update itself to say "Not Responding", but the only way out
is to force Explorer to quit and then wait for it to relaunch (or, if I'm
lucky, sometimes I can pull up the Task Manager and start Explorer that
way).

I have checked the logs on my server, and the entries I see are like this:

[2004/09/27 20:43:27, 1] smbd/service.c:make_connection_snum(648)
  192.168.1.101 (192.168.1.101) connect to service phpws initially as user
lenroc (uid=1000, gid=100) (pid 32369)
[2004/09/27 20:44:28, 0] lib/util_sock.c:read_socket_data(384)
  read_socket_data: recv failure for 4. Error = Connection reset by peer
[2004/09/27 20:44:28, 1] smbd/service.c:close_cnum(837)
  192.168.1.101 (192.168.1.101) closed connection to service phpws

The first entry corresponds with when I try to access a file. Then it
seems to wait for ~60 seconds before erroring out, then automagically
reconnecting. (I still don't get the file though. Windows just gives up, I
guess.)

The only portion of my smb.conf that I think is relevant is the following
line:
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

However, even without that line (so, using whatever the defaults are) I
experience the exact same problem.

Based on the error, it does not really seem like a Samba problem, but I do
successfully use this same server as an internal FTP (pure-ftpd), HTTP
(apache), IMAP (courier-imap), and DNS (dnsmasq) server, so if it is a
general networking problem, it's not widespread.

I have also tried mapping the share to a network drive, and using other
programs to open files directly, but I run into the exact same problems.

I have tried 2 different WinXP SP1 clients. I unfortunately do not have
any other breeds of Windows available to test.

Can anyone suggest any further troubleshooting steps I should take to help
narrow down the problem?

-- 
Lenroc

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

good morning lenroc,

are the clients and server on the same subnet or seperated by routers?

stuart


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] cannot copy from win2k client to samba share -SOLVED

[Stuart Highlander]

- Original Message - 
From: "Stuart Highlander" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 16, 2004 3:08 PM
Subject: [Samba] cannot copy from win2k client to samba share


> good afternoon all,
>
> i am running samba 3.0.7-2.FC1 on fedora core 1.
>
> i have a strange problem.  when the win2k clients at one of my sites try
to
> copy a file to a samba share on a different subnet, i get the following
> message:
>
> Cannot copy filename:  the specified network name is no longer available.
>
> i can copy the files to shares on a samba share on the same subnet, and i
> can copy the files from thte samba share on the different subnet to the
> win2k clients, but i cannot copy files from the clients to the samba share
> on the different subnet.
>
> no firewalls, and the permissions do not appear to be a factor.
>
> any ideas?
>
> stuart
>
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

good morning all,

this turned out to be a network problem and not a samba problem.

the input side of one of my routers happened to be throwing CRC and frame
errors when trying to copy the files in question from the one site to the
share on another site across the t1.

after wrestling with the provider for a week, they appear to have found and
corrected the problem.

stuart

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Automating Windows Update

[Stuart Highlander]

here are a couple of links that you might find interesting:

http://www.derkeiler.com/Mailing-Lists/NT-Bugtraq/2003-12/0079.html

http://sourceforge.net/projects/wpkg/

stuart


- Original Message - 
From: "jan ardosa" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 23, 2004 11:59 PM
Subject: [Samba] Automating Windows Update


Hi guys I was just wondering if there's already a way to automate the
process of updating Windows to be specific XP. My idea is to mimic how a
Windows server domain controller can rollout critical update on the entire
domain. Can Samba do this? Thanks for any info

Jan Ardosa



-
  Yahoo! Messenger - Communicate instantly..."Ping" your friends today!
Download Messenger Now
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Which distribution to rollout

[Stuart Highlander]

i had the same situation here.  i happened to be running  RH (7.2) servers
and addressing vulnerabilities started to become an issue.

i went the fedora route with few problems, most of my own making.  the
upgrades went relatively smoothly.  initial issues dealt with the upgrade
picking up an old config file for a nic on one server and causing my wins
server to not be able to find the server, causing domain login problems, and
minor differences between older versions of samba and samba 3.0.  fedora
stability has not been an issue here.  all they do is run, and run, and run
.

stuart


- Original Message - 
From: "Chris McKeever" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 23, 2004 9:44 AM
Subject: [Samba] Which distribution to rollout


> we are running an older version of RH (7.3) - and I am getting
> concerned that I may need to migrate off of it - but I dont know what
> I should move to.  Trying to formulate ideas before it becomes a 'got
> to do it now' scenario.
>
> I have some reservations about fedora - I just dont know how stable it
> is for a production server (our services are mainly
> samba/ldap/ntp/ssh/rsync/clamav) - we have about 15 samba servers in
> production currently.
>
> RHEL - well - the cost is a factor
>
> gentoo - takes to long to deploy
>
> Mandrake 10?
>
> What are some of the samba users recommendations?
>
> thanks
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] cannot copy from win2k client to samba share

[Stuart Highlander]

good afternoon all,

i am running samba 3.0.7-2.FC1 on fedora core 1.

i have a strange problem.  when the win2k clients at one of my sites try to
copy a file to a samba share on a different subnet, i get the following
message:

Cannot copy filename:  the specified network name is no longer available.

i can copy the files to shares on a samba share on the same subnet, and i
can copy the files from thte samba share on the different subnet to the
win2k clients, but i cannot copy files from the clients to the samba share
on the different subnet.

no firewalls, and the permissions do not appear to be a factor.

any ideas?

stuart

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] authentication problems after upgrade to samba 3.0.7-2.FC1 SOLVED!

[Stuart Highlander]

good morning all!

craig led me in the right direction on this one.

the problem was a bad ip address for dog2 in the dog1 wins.dat file.  dog1
is the network's win server.

here is what i did to solve this:
stopped smb on dog1.
deleted the wins.dat and browse.dat files in /var.cache/samba.
started smb on dog1.
restarted smb on dog2.
verified dog2 registered correctly by checking the wins.dat file on dog1
(cat /var/cache/samba/wins.dat).

many thanks to craig!

stuart
- Original Message - 
From: "Craig White" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, September 14, 2004 11:07 PM
Subject: Re: [Samba] authentication problems after upgrade to samba
3.0.7-2.FC1


> On Tue, 2004-09-14 at 18:39, fsb wrote:
> > good evening all,
> >
> > i upgraded my last samba 2.2.7a (dog2) this afternoon and
> > have run into
> > problems.
> >
> > first, the setup:
> > windows 2000 clients
> > three sites on three seperate subnets connected by t1
> > through routers.  each
> > site has a samba server that authenticates the users on its
> > subnet.  the
> > workgroup name for each server is dognet.  /etc/passwd,
> > /etc/group, and
> > smbpasswd are synced up manually.  users map drives to
> > shares on all servers
> > by logon script.  all servers are samba version 3.0.7-2.FC1
> > on Fedora Core
> > 1.
> >
> > dog1 authenticates users on 192.168.1.0.  he is also the
> > domain master.
> > dog1 is also the wins server for dognet.
> > from smb.conf of dog1:
> > workgroup=dognet
> >  netbios name=dog1
> > security=user
> > domain logons=yes
> > os level=65
> > preferred master=true
> > domain master=true
> > wins support=yes
> >
> > dog2 authenticates users on 192.168.2.0.  he is a local
> > master for
> > 192.168.2.0.
> > from smb.conf of dog2:
> > workgroup=dognet
> >  netbios name=dog2
> > security=user
> > domain logons=yes
> > os level=65
> > preferred master=true
> > local master=true
> > wins server=192.168.1.10
> >
> > dog3 authenticates users on 192.168.3.0.  he is a local
> > master for
> > 192.168.3.0.
> > from smb.conf of dog2:
> > workgroup=dognet
> >  netbios name=dog2
> > security=user
> > domain logons=yes
> > os level=65
> > preferred master=true
> > local master=true
> > wins server=192.168.1.10
> >
> > dog1 and dog3 work as expected.  after upgrading dog2, i
> > cannot authenticate
> > clients on 192.168.2.0 to dog2.  The message on the client
> > is:  The system
> > cannot log you on because the domain DOGNET is not
> > available.  dog2 is not
> > available via network neighborhood, but i can ssh, ping,
> > etc... into him.
> >
> > in /var/log/samba/nmbd.log of dog2, i get the following
> > messages when i
> > restart smb:
> >
> > add_domain_logon_names:  attempting to become logon server
> > for workgroup
> > DOGNET on subnet 192.168.2.10
> >
> > add_domain_logon_names:  attempting to become logon server
> > for workgroup
> > DOGNET on unicast_subnet
> >
> > become_logon_server_success:  samba is now a logon server
> > for workgroup
> > DOGNET on subnet unicast_subnet
> >
> > become_logon_server_success:  samba is now a logon server
> > for workgroup
> > DOGNET on subnet 192.168.2.10
> >
> > register_name_response:  WINS server at 192.168.1.10
> > rejected our name
> > registration of DOG2<20> IP 192.168.2.10 with error code 5.
> >
> > my_name_register_failed:  Failed to register my name
> > DOG2<20> on subnet
> > unicast_subnet.
> >
> > standard_fail_register:  Failed to register/refresh name
> > DOG2<20> on subnet
> > unicast_subnet
> >
> > register_name_response:  WINS server at 192.168.1.10
> > rejected our name
> > registration of DOG2<03> IP 192.168.2.10 with error code 5.
> >
> > my_name_register_failed:  Failed to register/refresh name
> > DOG2<03> on subnet
> > unicast_subnet
> >
> > standard_fail_register:  Failed to register/refresh name
> > DOG2<03> on subnet
> > unicast_subnet
> >
> > register_name_response:  WINS server at 192.168.1.10
> > rejected our name
> > registration of DOG2<00> IP 192.168.2.10 with error code 5.
> >
> > my_name_register_failed:  Failed to register my name
> > DOG2<00> on subnet
> > unicast_subnet.
> >
> > standard_fail_register:  Failed to register/refresh name
> > DOG2<00> on subnet
> > unicast_subnet
> >
> > Samba name server DOG2 is now a local master browser for
> > workgroup dognet on
> > subnet 192.168.2.10
> >
> > i do not get these messages when i restart smb on dog3.  the
> > two prior
> > upgrades (dog1 and dog3) went smoothly.
> >
> > does anybody have any ideas where i can get dog2 up by 8:00
> > tomorrow morning
> > (local time is 20:30)?
> 
> firewall?
>
> check wins.dat on dog1
>
> cat /var/cache/samba/wins.dat #or wherever it may be located...
>
> see if dog3 registers itself successfully. Is it possible that the
> router connections between the subnet 192.168.3 and 192.168.1 have
> different parameters than the subnet 192.168.2 and 192.168.1?
>
> I'm not sure that I would have 3 different machines listed

Re: [Samba] Samba Password Problems (Alt-Characters)-SOLVED

[Stuart Highlander]

Good Morning All,

I figured out a solution this problem.

I dumped the results of testparm to a file (testparm -v > smb_dump-file-01.
dos charset = CP850, unix charset = UTF-8.  local display = LOCALE.
I set the unix charset variable in smb.conf to unix charset = iso8859-1,
restarted smb, and verified unix charset set to iso8859 using testparm -v >
smb_dump-file-02.
I verified that my locale was ISO-8859-1 using locale charmap.

I tried syncing up UTF-8 as suggested, but could not get it to work
correctly with the alt-characters.

I want to thank Andrew for pointing me in the right direction.

Stuart

- Original Message - 
From: "Stuart Highlander" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 08, 2004 3:41 PM
Subject: [Samba] Samba Password Problems (Alt-Characters)


Good Afternoon All:

Here is the setup:
A RedHat 7.2 Samba 2.2.7 Server upgraded to Fedora Core 1 Samba 3.0.6-2.FC1.
The server is acting as the PDC.  No Windows servers are providing
authentication.
Windows 2000 clients.
testparm -v | grep "unix charset" results in UTF-8.
locale charmap results in ISO-8859-1.
using smbpasswd.


Before upgrading the server, I was able to authenticate users to the domain
on the Win2k boxes with alt-characters (alt-0162=¢) in their passwords.
Since upgrading the server, users who had these type of characters in their
passwords with passwords that have not changed, are able to authenticate,
but changing a user's password  to a new password that contains these
characters results in not being able to authenticate.

Any ideas?

Stuart

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Samba Password Problems (Alt-Characters)

[Stuart Highlander]

Andrew,

Thank you for replying to my post.

I am setting the passwords from the linux side.

Can you tell me how to change the locale to UTF8?

I would like to make the changes you recommend.

Thank you,

Stuart
- Original Message - 
From: "Andrew Bartlett" <[EMAIL PROTECTED]>
To: "Stuart Highlander" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, September 08, 2004 7:06 PM
Subject: Re: [Samba] Samba Password Problems (Alt-Characters)


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba Password Problems (Alt-Characters)

[Stuart Highlander]

Good Afternoon All:

Here is the setup:
A RedHat 7.2 Samba 2.2.7 Server upgraded to Fedora Core 1 Samba 3.0.6-2.FC1.
The server is acting as the PDC.  No Windows servers are providing
authentication.
Windows 2000 clients.
testparm -v | grep "unix charset" results in UTF-8.
locale charmap results in ISO-8859-1.
using smbpasswd.


Before upgrading the server, I was able to authenticate users to the domain
on the Win2k boxes with alt-characters (alt-0162=¢) in their passwords.
Since upgrading the server, users who had these type of characters in their
passwords with passwords that have not changed, are able to authenticate,
but changing a user's password  to a new password that contains these
characters results in not being able to authenticate.

Any ideas?

Stuart

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba