RE: [Samba] Not able to join domain
It might help, also, to set the samba machine explicitly to be the PDC: net rpc set-to-PDC. I've forgotten the exact switch, but you can do a man on net and look in the rpc section. Eric Hines At 04/06/06 07:56, you wrote: Hi, I think you should set security to USER instead of DOMAIN. Best regards, Bruno Guerreiro -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Boyd Sent: quinta-feira, 6 de Abril de 2006 12:25 To: samba@lists.samba.org Subject: [Samba] Not able to join domain I'm trying to set up Samba 3.0.20-4-SUSE on a opensuse 10 machine. I'm working with XP Pro on the client machine. I can't get the XP mahcine (RDS7) to join the domain (UCD). It asks for a user when trying to join and then says it cannot find it. The samba log is: auth/auth.c:check_ntlm_password(317) check_ntlm_password: Authentication for user [root] - [root] FAILED with error NT_STATUS_NO_SUCH_USER The root account is showing up in smbpasswd (that's assuming it needs to be there). Now the XP machine can see the domain (UCD) as well as WORKGROUP (which it currently is master of). Domain=[UCD] OS=[Unix] Server=[Samba 3.0.20-4-SUSE] Server Comment ---- UCD01Samba 3.0.20-4-SUSE WorkgroupMaster ---- UCD UCD01 WORKGROUPRDS7 This is after having to manually create the machine account (as there seems to be some problem with suse doing it on-the-fly. I've also noticed that testparm returns the samba machine as a BDC instead of a PDC. Load smb config files from /etc/samba/smb.conf Processing section [protel] Processing section [homes] Processing section [profiles] Processing section [users] Processing section [groups] Processing section [printers] Processing section [print$] Processing section [netlogon] Server's Role (logon server) NOT ADVISED with domain-level security Loaded services file OK. Server role: ROLE_DOMAIN_BDC Press enter to see a dump of your service definitions Also here's the smb.conf: [global] printcap name = cups 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: security = domain restrict anonymous = no domain master = Yes preferred master = Yes # idmap uid = 15000-2 # idmap gid = 15000-2 log level = 2 netbios name = UCD01 max protocol = NT ldap ssl = No server signing = Auto workgroup = UCD add machine script = /usr/sbin/useradd -c Machine -d /var/nodirs -s /bin/false '%u' passdb backend = tdbsam domain logons =Yes local master = Yes os level = 65 [protel] comment = Protel Data Folder path = /protel read only = no [homes] comment = Home Directories valid users = %S browseable = No read only = No inherit acls = Yes [profiles] comment = Network Profiles Service path = %H # path = /var/lib/samba/profiles 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 admin users = root guest ok = Yes browseable = No Anyway...if it's not obvious am a samba newb Oh and TIA - This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyrighted. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. USIT has scanned this email for viruses and dangerous content and believes it to be clean. However, virus scanning is ultimately the responsibility of the recipient
Fwd: RE: [Samba] Not able to join domain
Sorry about the direct post Date: Thu, 06 Apr 2006 08:38:39 -0500 To: Chris Boyd [EMAIL PROTECTED] From: Eric Hines [EMAIL PROTECTED] Subject: RE: [Samba] Not able to join domain At 04/06/06 08:13, you wrote: I've tried that and now I get Access denied instead cannot find user. Also I'm trying to run as a PDC and I thought that you have to have security = domain to do so. I've just found that under pdbedit root does not exist. I've tried to create it however and it gives the following. Should I import it from smbpasswd? pdbedit -a -u root Server's Role (logon server) NOT ADVISED with domain-level security new password: retype new password: tdb_update_sam: Failing to store a SAM_ACCOUNT for [root] without a primary group RID Unable to add user! (does it already exist?) The start of this error message implies that you have not yet changed your security level to user. Did you restart your Samba server after making that change? You must after every change to the smb.conf file, because Samba reads that file only on startup. Thanks Bruno Guerreiro [EMAIL PROTECTED] 04/06/06 1:56 PM Hi, I think you should set security to USER instead of DOMAIN. Best regards, Bruno Guerreiro -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Boyd Sent: quinta-feira, 6 de Abril de 2006 12:25 To: samba@lists.samba.org Subject: [Samba] Not able to join domain I'm trying to set up Samba 3.0.20-4-SUSE on a opensuse 10 machine. I'm working with XP Pro on the client machine. I can't get the XP mahcine (RDS7) to join the domain (UCD). It asks for a user when trying to join and then says it cannot find it. The samba log is: auth/auth.c:check_ntlm_password(317) check_ntlm_password: Authentication for user [root] - [root] FAILED with error NT_STATUS_NO_SUCH_USER The root account is showing up in smbpasswd (that's assuming it needs to be there). Now the XP machine can see the domain (UCD) as well as WORKGROUP (which it currently is master of). Domain=[UCD] OS=[Unix] Server=[Samba 3.0.20-4-SUSE] Server Comment ---- UCD01Samba 3.0.20-4-SUSE WorkgroupMaster ---- UCD UCD01 WORKGROUPRDS7 This is after having to manually create the machine account (as there seems to be some problem with suse doing it on-the-fly. I've also noticed that testparm returns the samba machine as a BDC instead of a PDC. Load smb config files from /etc/samba/smb.conf Processing section [protel] Processing section [homes] Processing section [profiles] Processing section [users] Processing section [groups] Processing section [printers] Processing section [print$] Processing section [netlogon] Server's Role (logon server) NOT ADVISED with domain-level security Loaded services file OK. Server role: ROLE_DOMAIN_BDC Press enter to see a dump of your service definitions Also here's the smb.conf: [global] printcap name = cups 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: security = domain restrict anonymous = no domain master = Yes preferred master = Yes # idmap uid = 15000-2 # idmap gid = 15000-2 log level = 2 netbios name = UCD01 max protocol = NT ldap ssl = No server signing = Auto workgroup = UCD add machine script = /usr/sbin/useradd -c Machine -d /var/nodirs -s /bin/false '%u' passdb backend = tdbsam domain logons =Yes local master = Yes os level = 65 [protel] comment = Protel Data Folder path = /protel read only = no [homes] comment = Home Directories valid users = %S browseable = No read only = No inherit acls = Yes [profiles] comment = Network Profiles Service path = %H # path = /var/lib/samba/profiles 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
RE: [Samba] Not able to join domain
At 04/06/06 09:09, Bruno Guerreiro wrote: Hi. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Hines Sent: quinta-feira, 6 de Abril de 2006 14:34 To: samba@lists.samba.org Subject: RE: [Samba] Not able to join domain It might help, also, to set the samba machine explicitly to be the PDC: net rpc set-to-PDC. I've forgotten the exact switch, but you can do a man on net and look in the rpc section. Never heard of this one. Always thought that this was defined only via smb.conf. I also was unable to find any entry im smb.conf From my SuSE 10.0 man page on net, in the rpc section: [RPC|ADS] JOIN [TYPE] [-U username[%password]] [options] An instruction to join a domain as PDC, then, would be net rpc join PDC. The username can be supplied on the same command line (I don't recommend adding the password, also, at this point--maybe I'm just excessively paranoid), and you'll be prompted for the password, or you can omit the username, also, and you'll be prompted for both the user and the password. You can set Domain master via smb.conf, but that's not the same thing as setting PDC. Eric Hines Best Regards, Bruno Guerreiro Eric Hines The mode in which the inevitable comes to pass is through effort. --Justice Oliver Wendell Holmes, Jr -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Not able to join domain
At 04/06/06 09:18, Chris Boyd wrote: I ran the groupmap script #!/bin/bash net groupmap modify ntgroup=Domain Admins unixgroup=ntadmin net groupmap modify ntgroup=Domain Users unixgroup=users net groupmap modify ntgroup=Domain Guests unixgroup=nobody and was able to create the root account in pdbedit. I've gotten the XP machine to join the UCD domain now. Although I'm still not clear what the groupmapping did. It created a confluence of Windows admin and *NIX root. This allows either to be used in place of the other, but now things get hazy for me, and a Samba guru is going to have to supply clarity. I'm nearly as new at this as you. snip Ok I've got it back to PDC by doing the net rpc join PDC.It gave me a failed to join domain error but it shows as a domain PDC now. That syntax would be right if you were trying to join a domain called PDC Showing as PDC is only dependent of the smb.conf file. According to my man page, this is the correct syntax for joining as PDC, not joining a domain called PDC. Setting domain logons = yes should make Samba be the PDC, also, but I've had trouble with this absent explicitly joining the domain as PDC, also, using the above command. This is either a bug in Samba (I've been using 3.0.14 and 3.0.21a), or it's a function of my newness and error rate at setting up samba servers. I lean toward the latter. snip The mode in which the inevitable comes to pass is through effort. --Justice Oliver Wendell Holmes, Jr -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] My Network Places not finding Samba server
You might try adding it to your XP's hosts file, also. This is located in the same place as your lmhosts file; it has slightly different uses. Also, you might ensure that this other NetBIOS name and IP address are listed in your Linux box's hosts file. A lot of things in your network get gutsed up when your Linux box comes up, and it gets its initial data from, among other places, its hosts file. Eric Hines At 02/21/06 22:11, Frederick C. Damen wrote: I changed the smb.conf to have a different NetBios Name then the workgroup 'DAMEN'. There does not appear to any change from the XP 'My Network Places' Although the nmbd.log indicates that the name DAMEN00 is not found. [2006/02/21 21:24:14, 1] nmbd/nmbd_incomingrequests.c:process_node_status_request(328) process_node_status_request: status request for name DAMEN00 from IP 192.168.0.1 on subnet UNICAST_SUBNET - name not found. [2006/02/21 21:24:16, 1] nmbd/nmbd_incomingrequests.c:process_node_status_request(328) process_node_status_request: status request for name DAMEN00 from IP 192.168.0.1 on subnet UNICAST_SUBNET - name not found. Although 'nmblookup DAMEN' finds the name when executed on the linux box upon which smbd/nmbd is running. querying DAMEN on 192.168.255.255 192.168.0.1 DAMEN00 This appear to (not)work the same with or without DAMEN listed in the lmhosts file. Do I need to list the workgroup name somewhere else also? Thanks, Fred Frederick C. Damen wrote: Thanks. I removed the entry for DAMEN from lmhosts and restart smb/nmb and no change that I can see. Thanks, Fred Kristaps RÄts wrote: Having the machine name equal to the workgroup name is a no-no, as far as I know. On O , 2006-02-21 at 08:15 -0600, Frederick C. Damen wrote: I assume I am doing(or not) something extremely simple that is causing my XP boxes to not see my linux(FC4) Samba server in the 'My Network Places'. I can access the shares by 'Map Network Drive' and using the IP address(192.168.0.1). I have set the workgroup name 'DAMEN' in the lmhosts file. 192.168.0.1 DAMEN I have set the workgroup in the smb.conf file. workgroup = damen netbios name = damen I have configured the Samba server to be the Domain Master Browser os level = 35 domain master = yes preferred master = yes wins support = yes I have configured the [global] to be browseable. browseable = yes public = yes I have set the XP box to be on a home network(not bussiness network) and workgroup to DAMEN. Any ideas? Thanks, Fred -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Join Domain Problem?
No, I haven't gotten a response, yet.
Eric Hines
At 02/06/06 18:13, James Taylor wrote:
Did you get a resolution to this issue? I am wondering because I am having
similar issues with my Samba setup.
JT
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Eric Hines
Sent: Sunday, February 05, 2006 10:06 AM
To: samba@lists.samba.org
Subject: [Samba] Join Domain Problem?
List,
I'm having trouble accessing shares, and I'm getting conflicting
indications on whether I've successfully joined the domain with my PC
and Samba server (which may bear on the share problem). I really
could use some help; I've not been able to recognize anything in the
docs or via Google that helps. I'm running SUSE 9.3 and Samba
3.0.21a, and I'm trying to access shares from a Win2k PC.
I ran net join PDC -D server -W domain -U root and got back the
answer ads_connect: Transport end is not connected. Joined domain
domain
net rpc testjoin returns Join to domain is OK.
However, wbinfo -u and wbinfo -g both return Error looking up domain
users/groups, and winbindd can only find BUILTIN for a trusted
domain, according to its log, and my log. wb_domain indicates that
no trusted domain ever is found.
But wbinfo -t succeeds, wbinfo -D=domain returns the domain data,
including its SID, and wbinfo --sequence returns BUILTIN and
domain, albeit with the same numbers.
Testparm says the Samba is the domain PDC. My PC successfully boots
into the domain with me (or root, as the case may be) as the logged in user.
So, how can I tell whether I've correctly joined the domain?
The second part of this is that with each of two shares (share1 and
share2), set up as below (I've only used bandwidth on one share;
their set up is identical), I get BAD_NETWORK_NAME from an smbclient
//server/share1 -U user call. With valid user set to @group in
share1 only, this changes to a bad login error (ACCESS_DENIED) for
that share. However, when logged in on the PC as root, I get into
share2 (which does not have @group set) just fine, but I get the
login error when root tries to get into share1. This argues that I
have an access problem with the two shares, and my domain problem
impacts this only obliquely.
The logs all indicate that the shares are being formed correctly, but
the messages log says that my PC couldn't find service: {[long
string of digits and characters, hyphenated into 5 groups]}, and that
the PC also couldn't find the to the directory containing share2
(without the @groups). It also appears that the last character of
each share gets truncated when its being sought out (found this in
the PC log on the Samba server). However, that last character always
is found eventually for share1 and never is for share2.
Setting createmask, et al., has had no effect, probably because I'm
not getting into the shares for these to have an effect.
So, what have I got going on here? How can I further troubleshoot
this share problem, also?
share1
path=/data/share1
valid [EMAIL PROTECTED] #Note: Share2 has only valid users = ''; it is
otherwise identical to this
read only=no
Thanks for your help; I've been pulling my hair out over these for
several weeks. I'm going bald
Eric Hines
There is no nonsense so errant that it cannot be made the creed of
the vast majority by adequate governmental action.
--Bertrand Russell
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Join Domain Problem?
List,
I'm having trouble accessing shares, and I'm getting conflicting
indications on whether I've successfully joined the domain with my PC
and Samba server (which may bear on the share problem). I really
could use some help; I've not been able to recognize anything in the
docs or via Google that helps. I'm running SUSE 9.3 and Samba
3.0.21a, and I'm trying to access shares from a Win2k PC.
I ran net join PDC -D server -W domain -U root and got back the
answer ads_connect: Transport end is not connected. Joined domain domain
net rpc testjoin returns Join to domain is OK.
However, wbinfo -u and wbinfo -g both return Error looking up domain
users/groups, and winbindd can only find BUILTIN for a trusted
domain, according to its log, and my log. wb_domain indicates that
no trusted domain ever is found.
But wbinfo -t succeeds, wbinfo -D=domain returns the domain data,
including its SID, and wbinfo --sequence returns BUILTIN and
domain, albeit with the same numbers.
Testparm says the Samba is the domain PDC. My PC successfully boots
into the domain with me (or root, as the case may be) as the logged in user.
So, how can I tell whether I've correctly joined the domain?
The second part of this is that with each of two shares (share1 and
share2), set up as below (I've only used bandwidth on one share;
their set up is identical), I get BAD_NETWORK_NAME from an smbclient
//server/share1 -U user call. With valid user set to @group in
share1 only, this changes to a bad login error (ACCESS_DENIED) for
that share. However, when logged in on the PC as root, I get into
share2 (which does not have @group set) just fine, but I get the
login error when root tries to get into share1. This argues that I
have an access problem with the two shares, and my domain problem
impacts this only obliquely.
The logs all indicate that the shares are being formed correctly, but
the messages log says that my PC couldn't find service: {[long
string of digits and characters, hyphenated into 5 groups]}, and that
the PC also couldn't find the to the directory containing share2
(without the @groups). It also appears that the last character of
each share gets truncated when its being sought out (found this in
the PC log on the Samba server). However, that last character always
is found eventually for share1 and never is for share2.
Setting createmask, et al., has had no effect, probably because I'm
not getting into the shares for these to have an effect.
So, what have I got going on here? How can I further troubleshoot
this share problem, also?
share1
path=/data/share1
valid [EMAIL PROTECTED] #Note: Share2 has only valid users = ''; it is
otherwise identical to this
read only=no
Thanks for your help; I've been pulling my hair out over these for
several weeks. I'm going bald
Eric Hines
There is no nonsense so errant that it cannot be made the creed of
the vast majority by adequate governmental action.
--Bertrand Russell
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Can't Get to Shares
Folks, I have two problems that may be related, and I'm hoping that with the mailing list back on the air, some of you can offer some help on resolving them/it. I'm running SUSE 9.3 and Samba 3.0.21a (which is managing a LAN with an XP laptop and a Win2k PC). Samba has joined the domain and is the PDC, winbindd is running, wins support = yes. The first problem is that, while I can get to some shares (e.g., home directory, printers, netlogon, profiles), others I cannot get to--I just get back NT_STATUS_BAD_NETWORK_NAME. These non-connecting shares are owned by a user and a group (of course), and the users trying to connect are members of the owning group. Googling, and checking the archives here turn up others with this problem, but no solutions. Tests I've run exploring this include: smbstatus--returns the connections from the PC (the laptop is off at the moment; it has the same symptoms) that are active and open getent passwd--succeeds getent group--succeeds wbinfo -t--succeeds Samba has successfully joined the domain However, these tests fail: smbclient //server/share -U user --returns the BAD_NETWORK_NAME error net use \\server\share from the PC returns network name cannot be found--the same as above net use \\server\misspelled share from the PC returns network name cannot be found. Clearly not getting to the point of authentication. wbinfo -u and wbinfo -g return error looking up domain users/groups The second problem (and I suspect the cause of the first) is that I cannot get my PC to join the domain. When I try, whether I use my Linux box root and password, as is the correct way, or I use the PC's Admin account to authenticate the joining in response to the prompts, I just get a credentials supplied conflict with an existing set of credentials error. How can I fix this? I suspect I need first to get the PC to join the domain, but I'm clueless as to how, given this error. Right click on My Computer|Properties|Network ID Tab|Network ID or Properties, either one, returns the conflicting credentials error message. Thanks for your help. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can't Connect to Shares
At 01/22/06 22:06, Adam Nielsen wrote: wbinfo -u == error looking up domain users wbinfo -g == error looking up domain groups You do have winbindd running, don't you? If so, it looks like you haven't joined the domain correctly which I suspect is the cause of all the problems. 'net testjoin' should return OK if you've successfully joined. Yes, winbindd is running. I assume this has to be done on the Samba machine; no such options (join, testjoin, etc) exist on the Win2k PC. I ran, on the Samba machine, both test join and test join PDC (as I have the Samba set for being a PDC), and the commands claimed success at completion, and net rpc testjoin returned Join to 'ASTRA_ENT' is ok. However, both joins also gave the message :ads_connect: Transport endpoint is not connected. I'm assuming (hoping) that's because I'm not running ADS. However, smbclient //server/share -U user still returns the NT_STATUS_NETWORK_NAME error, and wbinfo -u and wbinfo -g both return the same errors as above. And when I try to get my Win2k PC to join the domain (My Computer|Properties|Network ID tab|Properties) I get the credentials conflict, whether I use my root|passwd or a Windows' Admin|passwd authentication. And I still can't connect to any of the three shares--same NT_STATUS_NETWORK_NAME errors. There is some progress, though; nmblookup -B server __SAMBA__ now returns the correct answer. What else do I need to look for? I assume I still need to get the PC to join the domain, but how? Cheers, Adam. Thanks for your help. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] RESOLVED:Network and Reboot Problem
Simple, too, it turns out: I just added os level = 35 to the [globals] stanza, and now the Samba server wins all the elections when the PC/laptop reboot and claim to be the domain server. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Can't Connect to Shares
I'm running SUSE 9.3 with Samba 3.0.21a, but I can't connect to some shares, even though I can connect to others just fine. I get into my home share, netlogon share, printer shares, etc, but three shares all get me the same answer in response to smbclient -L //server/share: I get back an NT_STATUS_BAD_NETWORK_NAME error. All users are correctly in passdb, passwd, etc. I have winbind running, WINS Support=Yes, Samba is set as a PDC (I think--Preferred Master=Yes). Googling the error message and searching the HOWTO didn't turn up any solutions, only the statement that this error generally meant that the share was badly formed. Following are additional tests I've run that have failed, and their results: from the server side: smbclient //lserver0/share -U ehines == the BAD_NETWORK_NAME error message Note: When I run this against the working shares, I get the correct response. from the Windows device side: net use \\lserver0\share == System 67 error...network name cannot be found. Note: When I run this against the working shares, I get the correct response. nmblookup -B lserver0 __SAMBA__ == querying SAMBA on 192.168.2.2...name-query failed to find __SAMBA__ even though SAMBA clearly is running, and I can connect to it from the Windows devices. nmblookup -d 2 '*' works to the extent that it finds the PC on one subnet, but it does not find the laptop on another subnet (even though the laptop is identical to the PC in terms of successful--and failed--access to the shares, and SWAT's STATUS function shows the laptop as well as the PC to be active). wbinfo -u == error looking up domain users wbinfo -g == error looking up domain groups wbinfo -a ehines%passwd == NT_STATUS_CANT_ACCESS_DOMAIN_INFO wbinfo --get-auth-user == no authorized user configured However, wbinfo -D DomainName returns the SID and the correct domain name, and net rpc info returns the correct domain name and SID. It also returns 5 users, which is all I've set up for now, but it returns Num domain groups: 5 and Num local groups: 0. I only have 1 domain, so I guess I'm not understanding these responses completely. The offending share setup from smb.conf (I've only enclosed one; the three are essentially identical) is below, together with an excerpt from my [global] stanza. If I've over-snipped the [global], I'll send the whole thing, but it's a bit long. [accounts] comment = Accounting Files path = /data/accounts read only = No [global] workgroup = ASTRA_ENT netbios name = LSERVER0 interfaces = 192.168.2.2/24, 192.168.3.1/24, lo bind interfaces only = Yes passdb backend = tdbsam pam password change = Yes unix password sync = Yes smb ports = 139 name resolve order = wins bcast hosts shutdown script = /var/lib/samba/scripts/shutdown.sh abort shutdown script = /sbin/shutdown -c domain logons = Yes preferred master = Yes wins support = Yes Thanks a lot for your help. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Can't Add Users to Passdb
Folks, I've gone and screwed something up, and I cannot add users to passdb database. I've set passdb backend to tdbsam in my [global]. I've added users to passwd (useradd -m user). However, when I try to add smb users, I get errors and failures to add the users. smbpasswd -a root (and supply the password in response to the prompts) gets me the following error messages: tdb_update_sam: Failing to store a SAM_ACCOUNT for [root] without a primary group RID Failed to add entry for user root. Failed to modify password entry for user root This happens whether I'm trying to add root or ordinary users. What have I screwed up, and how do I fix it? Thanks for your help. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] RESOLVED: Can't Add Users to Passdb
Folks, I've gone and screwed something up, and I cannot add users to passdb database. I've set passdb backend to tdbsam in my [global]. I've added users to passwd (useradd -m user). However, when I try to add smb users, I get errors and failures to add the users. smbpasswd -a root (and supply the password in response to the prompts) gets me the following error messages: tdb_update_sam: Failing to store a SAM_ACCOUNT for [root] without a primary group RID Failed to add entry for user root. Failed to modify password entry for user root This happens whether I'm trying to add root or ordinary users. What have I screwed up, and how do I fix it? Thanks for your help. Eric Hines Somehow, my script for mapping Windows groups to UNIX groups had gotten screwed up, and it was creating two instances of each mapping (e.g., of Domain Admins to root, Domain Users to users, etc), with each mapping having different SIDs. Tdbsam was getting confused. I blew away the mappings, one by each, and recreated them, one by each, and now I can add my users (including root...) to the passdb database. net groupmap list let me see the mappings, net groupmap delete got rid of them all (possibly I could have just gotten rid of one of each of the two instances, but which one?), and net groupmap modify let me reset the pairings. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] One SAMBA Server, two networks.
At 01/16/06 08:12, Robert Adkins wrote: Hello, I am making some changes to our network to split the front office and back office onto two seperate subnets, but need to keep the same Samba server in place serving both subnets. What I am intending to do is install an additional network card into the server and address this new card for the new subnet. What I am looking to do is properly broadcast the server's samba status/availability across both networks and properly serve files/domain controller data across both subnets. To do this, I intend to duplicate all the entries in the lmhosts file in /etc/samba with the only difference being the network that the server is broadcasting on. Will this work, or is this more complicated then I am currently seeing? -- Regards, Robert AdkinsIT Manager/Buyer Impel Industries, inc. 586-254-5800 I've gotten most of this to work by using the example in Chapt 3 of the Samba-3 by Example book. However, I'm stuck on being able to get access to only some of my shares--for the ones to which I can't connect, I get a BAD_NETWORK_NAME error. If you get past this, please post your solution here. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Mal-Formed Share
Folks, I'm having a problem connecting to some shares, and not to others. I'm running SUSE 9.3 and Samba 3.0.22pre1 with a Win2k PC on one subnet and an XP laptop on a separate subnet. The problem is that with three shares out of eight, I get a tree connect failed: NT_STATUS_BAD_NETWORK_NAME error message; I get appropriate accesses to the remaining five. Googling the error message and searching the HOWTO didn't turn up any solutions, only the statement that this error generally meant that the share was badly formed. Following are the tests I've run that have failed, and their results: from the server side: smbclient //lserver0/share -U ehines == the BAD_NETWORK_NAME error message Note: When I run this against the working shares, I get the correct response. from the Windows device side: net use \\lserver0\share == System 67 error...network name cannot be found. Note: When I run this against the working shares, I get the correct response. nmblookup -B lserver0 __SAMBA__ == querying SAMBA on 192.168.2.2...name-query failed to find __SAMBA__ even though SAMBA clearly is running, and I can connect to it from the Windows devices. nmblookup -d 2 '*' works to the extent that it finds the PC on one subnet, but it does not find the laptop on another subnet (even though the laptop is identical to the PC in terms of successful--and failed--access to the shares, and SWAT's STATUS function shows the laptop as well as the PC to be active). I have winbind running, WINS Support=Yes, Samba is set as a PDC (I think--Preferred Master=Yes). The offending share setup from smb.conf (I've only enclosed one; the three are essentially identical) is below, together with the [global] stanza. If I've over-snipped the [global], I'll send the whole thing, but it's a bit long. [accounts] comment = Accounting Files path = /data/accounts read only = No [global] workgroup = ASTRA_ENT netbios name = LSERVER0 interfaces = 192.168.2.2/24, 192.168.3.1/24, lo bind interfaces only = Yes passdb backend = tdbsam pam password change = Yes unix password sync = Yes smb ports = 139 name resolve order = wins bcast hosts shutdown script = /var/lib/samba/scripts/shutdown.sh abort shutdown script = /sbin/shutdown -c domain logons = Yes preferred master = Yes wins support = Yes Thanks for your help. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Network and Reboot Problem
Folks, I'm running a Samba server (SUSE 9.3 and Samba 3.0.22pre1) on a 2-subnet LAN, with a Win2k PC on one subnet and an XP laptop on the other. When I boot up the server and then the two windows devices at the start of a day, everything comes up just fine, the server appears in Network Neighborhood and in Explorer, and I have access to my shares normally. However, my problem is this: if I have occasion to reboot either (or both) Windows devices after having successfully formed the LAN, I can't get back to my shares except through some convoluted machinations, and the server no longer appears in NN or in Explorer. When I run START|RUN|\\lserver0\ehines, I get access to the ehines home share. When I run, from a DOS command line, net view \\lserver0, I get a listing of all the shares to which I'm supposed to have access. Net use \\lserver0\share returns a successful completion message. I get this behavior on both devices, and whether I cold reboot or log off one user and log on another. This acts like a Windows thing, rather than a general network problem (although I really have no hard data or knowledge with which to substantiate that). Do any of you have any ideas about how to pursue and correct this? Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbclient not displaying shares
At 01/04/06 04:59, you wrote: Eric Hines [EMAIL PROTECTED] At 01/03/06 05:48, Gerard Seibert wrote: I have just recently installed Samba. I have two WinXP Pro machines networked to a FreeBSD 5.4 computer. The Printer is connected to one of the WinXP machines currently. This is the output of the 'smbclient' command. smbclient -U user-name -L winxp Password: Domain=[winxp] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment - --- Error returning browse list: NT_STATUS_OK Domain=[winxp] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Server Comment ---- WorkgroupMaster ---- As you can see, nothing is listed. Does testparm give you any hints? Eric Hines Nothing at all. I created the file with SWAT; therefore, I would assume the syntax was correct. I have no idea what is wrong. I have Googled and found others with this problem, but no concrete solution to it. SWAT won't check syntax; that's why you run testparm. However, testparm only checks syntax and otherwise just regurgitates what you put into the config file. If there are no clues from testparm, then I have no further ideas. What do you have for your passdb backend = input? I had a problem with using tdbsam and forgetting to put anyone into the passdb table; when I did that, this problem went away. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbclient not displaying shares
At 01/03/06 05:48, Gerard Seibert wrote: I have just recently installed Samba. I have two WinXP Pro machines networked to a FreeBSD 5.4 computer. The Printer is connected to one of the WinXP machines currently. This is the output of the 'smbclient' command. smbclient -U user-name -L winxp Password: Domain=[winxp] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment - --- Error returning browse list: NT_STATUS_OK Domain=[winxp] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Server Comment ---- WorkgroupMaster ---- As you can see, nothing is listed. Does testparm give you any hints? Eric Hines snip There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Trouble Connecting to Server
At 01/02/06 22:36, Craig White wrote: On Mon, 2006-01-02 at 22:24 -0600, Eric Hines wrote: At 01/02/06 21:37, Adam Nielsen wrote: I'm having trouble connecting to my Samba server. The immediate symptom is that I cannot see my Samba server in my Windows Network Neighborhood, and so I cannot connect to it to check my share connections. try 'wins support = yes' in smb.conf It's there, and winbindd is running. snip If running \\samba.ip on a Windows box works, then this is definitely the problem. Additional data, from an error log I have named.conf generating, keeping in mind that I have dynamic dns turned on. I'm getting messages to the effect that my test1 dot biz dot hosts dot jnl file (test1 dot biz dot hosts is the forward lookup file that, among other things, defines the points of contact for my two subnets) cannot be created due to a permission denied error. My test1 dot biz dot hosts forward lookup table lives in /var/lib/named/master directory, with permissions rw-r--r--, and it's owned by root:root. Further, even though I have ddns running, this test1 dot biz dot hosts file remains unchanged from the day I created it--not a thing has been added to it. Should there have been by now, or am I exposing my ignorance here? Further, my named and dhcpd are running in separate chroot jails. Is this causing problems with updating this file--or any other of my forward lookup files? on most systems, named runs as user named and thus cannot make changes to files owned by root:root and cannot create journal files in folders unless owned by named:named and chmod 775 That's pretty much what I thought. DO I need to worry about the lack of journal files? I have the impression that these aren't particularly relevant to my problem. Finally, what do the error messages mean, and what do I need to do to correct that? probably follow some of the best documentation available and resist the temptation to shortcut it. Who--me!? Take shortcuts!? http://samba.org/samba/docs/man/Samba3-ByExample/ this might be just the chapter you are looking for... http://samba.org/samba/docs/man/Samba3-ByExample/Big500users.html Yeah, it's the Chapt 3 example I'm having trouble with. I'll look at that Chapt 4, too. Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] tdbsam Question
Dumb question time; I can't find the answer in the Samba-3 or HOWTO docs: how do you add users to the passdb.tdb (tdbsam's db)? Is pdbedit the only way? I ask because the Chapt 3 Samba-3 example has passdb = tdbsam in the samba config file, but the instructions for adding users are to use useradd and smbpasswd, which leave passdb.tdb empty (except for root--I have no idea how that got in there). Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Trouble Connecting to Server
Folks, I'm having trouble connecting to my Samba server. The immediate symptom is that I cannot see my Samba server in my Windows Network Neighborhood, and so I cannot connect to it to check my share connections. I'm running SUSE 9.3 on the server, which is running Samba (3.0.22) , a dhcp server (which seems to be running correctly--everyone gets an address when they ask for one), and a dns server with ddns operating (via the dhcpd). NIC 192.168.1.2 faces the Internet and gets there through a Linksys router/switch on 192.168.1.1. A Win2k PC sits on a 192.168.2.0 subnet; this subnet's NIC is set to 192.168.2.2 (the PC itself gets IP 192.168.2.9). A laptop dual bootable between SUSE 9.3 and WinXP sits on a 192.168.3.0 subnet; its NIC is set to 192.168.3.1 (the laptop gets 192.168.3.9). Both of these subnets must go through the 192.168.1.2 NIC to get to the Internet; all devices have easy access to the Internet. A poor man's ASCII art diagram lies below. Both the XP laptop and the Win2k PC have the same symptoms, so I'll just talk about the PC. .3.0 .3.1--samba/dns/dhcp--.2.2---.2.9 | .1.2 | | Linksys .1.1 | Internet I have the following entries in its smb.conf: netbios name = lserver0 workgroup = astra_ent [of which both the laptop and PC are members] interfaces = 192.168.2.0/24 192.168.3.0/24 lo [I can't use eth1 and eth2 as SUSE 9.3 assigns the ethx to different NICs on different boot ups] name resolve order = wins bcast hosts My /etc/hosts file on the SUSE has the following entries: 192.168.2.2lserver01.test1.biz lserver01 lserver0 192.168.1.2sserver.test.biz sserver 192.168.3.1lserver02.test1.biz lserver02 Being cheap (perhaps pound foolish), I've not registered the test.biz domain; although if it comes to that, I will. I have registered it by putting the sserver line from the /etc/hosts file into the PC's (for now; the laptop solution should look much the same) hosts file (which the PC reads just like an lmhosts file). IP Forwarding is turned on on the SUSE box, and ddns is enabled via the dhcp server (and is evidenced by the resolver cache on the PC). The Win2k's resolver cache has both forward lookup and reverse lookup files for sserver, sserver.test.biz, and all the lserver0x and .test1.biz names. The PC's WINS is pointed at the 192.168.1.2, 192.168.2.2, and 192.168.3.1 NICs. I can ping all by hostname, as well as by FQDN; although it appeared that I could not ping sserver by hostname only until I added sserver and its FQDN to the PC's host file (which it reads as though it were an lmhosts file). I say it appeared because it looked like the forward and reverse look up files for sserver appeared in the PC's resolver cache before I made this addition, but I got too fast with a ping test and contaminated that datum. Any advice would be greatly appreciated. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Trouble Connecting to Server
At 01/02/06 21:37, Adam Nielsen wrote: I'm having trouble connecting to my Samba server. The immediate symptom is that I cannot see my Samba server in my Windows Network Neighborhood, and so I cannot connect to it to check my share connections. You can still go Start | Run \\ip.address to connect to a 'hidden' Samba server. I get a network path not found error. However, when I do the same thing for each of the two subnets, I get invited to log in (my Samba error, I think--I may have not yet put anything into my tdbsam. I'm still trying to get the network itself to work.) I can ping all by hostname, as well as by FQDN; although it appeared that I could not ping sserver by hostname only until I added sserver and its FQDN to the PC's host file (which it reads as though it were an lmhosts file). I say it appeared because it looked like the forward and reverse look up files for sserver appeared in the PC's resolver cache before I made this addition, but I got too fast with a ping test and contaminated that datum. It sounds like nmbd isn't running, or more likely, it's only running on one subnet. There are all sorts of issues using NetBIOS names across different subnets, but Google will tell you all about that. I do have only one instance of nmbd running, and two of smbd. How do I get another nmbd instance to run? If running \\samba.ip on a Windows box works, then this is definitely the problem. Additional data, from an error log I have named.conf generating, keeping in mind that I have dynamic dns turned on. I'm getting messages to the effect that my test1 dot biz dot hosts dot jnl file (test1 dot biz dot hosts is the forward lookup file that, among other things, defines the points of contact for my two subnets) cannot be created due to a permission denied error. My test1 dot biz dot hosts forward lookup table lives in /var/lib/named/master directory, with permissions rw-r--r--, and it's owned by root:root. Further, even though I have ddns running, this test1 dot biz dot hosts file remains unchanged from the day I created it--not a thing has been added to it. Should there have been by now, or am I exposing my ignorance here? Further, my named and dhcpd are running in separate chroot jails. Is this causing problems with updating this file--or any other of my forward lookup files? Finally, what do the error messages mean, and what do I need to do to correct that? Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba cd-rom share Problem
If you have more than one CDROM on your machine, the correct share path might be something like path = /media/cdrom1 Eric Hines At 12/27/05 09:38, Andreas Bauer wrote: Hello NG, my network consists of AD/2003 as LDAP Server, SuSE 10.0 and xp clients and SuSE 9.3 Samba/NFS-Fileserver for the homes of SuSE clients and Samba shares for the Xp clients. My problem is the cd-rom samba share. All other samba shares except the cd-rom share are working for me. If I open the network environment in the windows explorer of a succeded logon xp client, I can access all shares except the cd-rom share. At accessing the cd-rom share in the windows explorer, I am getting no errormessage, but the directories and files of the shared cd do not appeare in the right side side of the win explorer. The right part of the windows exlorer is empty. The cd-rom section in the smb.conf is: [cdrom] path = /media/cdrom read only = yes browseable = yes locking = no Best regards and many thanks Andreas There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] OT: SUSE 9.3 and NICs
At 12/25/05 15:29, John H Terpstra wrote: On Saturday 24 December 2005 17:38, Eric Hines wrote: Folks, I realize this is off topic, and if anyone can suggest a better source for the question, I'd be glad to go there. Novell SUSE's support is unresponsive, however. My problem is this: I'm running 9.3 Pro on an Intel server board that has two NIC chips built in (a 10/100 and a GigE). I've since added a Netgear GigE NIC. However, every time I reboot, the NICs assigned to eth0, 1, and 2 all change at random, as do the IP addresses assigned. This happens whether I do anything at all or try to set things up through YaST. I'm trying to set up two subnets off this (samba-run) server, with one NIC (or one IP address) facing the Net and the other two NICs (or IP addresses) having to go through this NIC to get to the Net. It would seem impossible to cable up the LAN if the NIC supporting a given subnet--and its address--keep changing. How can I stabilize the NIC/IP address/ethx assignments? I see the exact same thing happening on my SusE9.3 boxen. Upgrade to SuSE 10 - seems to fox this. What other information does anyone need to help me with this? Let me know if you discover the secret - I'd like to know also. - John T. Thanks very much. What I got from the suse-linux-e@suse.com mailing list (summarized here and the key parts of the thread added below) is that you don't care if eth0 comes up on one NIC this time and another NIC the next. The only thing you have to get right is the NIC/IP address pairing. This must remain stable--and it does. The man page on ifstatus says ethx wander around since the advent of removable (e.g., USB) cards, and the boot up process initializes the first NIC it comes to and calls that one eth0, and so on. The kernel's IP stack then keeps track of the eth/NIC pairing so the NIC/IP address go where they need to go. X-Originating-IP: [195.135.221.131] Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm list-help: mailto:[EMAIL PROTECTED] list-unsubscribe: mailto:[EMAIL PROTECTED] list-post: mailto:suse-linux-e@suse.com Delivered-To: mailing list suse-linux-e@suse.com From: Michael W Cocke [EMAIL PROTECTED] To: suse-linux-e@suse.com Subject: Re: [SLE] SUSE 9.3 Pro and 3 NICs On Sun, 25 Dec 2005 15:59:12 -0500, you wrote: Eric Hines wrote: At 12/25/05 07:51, James Knott wrote: Eric Hines wrote: At 12/24/05 18:53, James Knott wrote: Eric Hines wrote: snip Alternatively, how do I use YaST to do this? I've been in YaST|Network Devices|Network Card|NIC|Edit and edited the IP address for each. I can't find any place to pin a NIC to a particular ethx, though. And both the addresses and the ethx change on each boot--e.g., eth0 will have on NIC (by MAC address) and one IP address after one bootup, and after another bootup it'll have a different NIC and a different IP address (and both will be completely different--it won't simply be a NIC/IP address pairing from another ethx on the earlier bootup). I'm not sure what you're getting at here. If you use the ifcfg files, you'll always configure the correct NIC. If you need to refer to the NICs in a script, you use the full name. snip One of the problems I have--and I'll try editing the files directly, to guarantee that I'm configuring the correct NIC with the correct information--is that it doesn't seem to make any difference how I configure each NIC--or whether I configure them at all--on one boot up, eth0, say, will have NIC1, with IP address 2, attached to it, and on a subsequent bootup, eth0 will have NIC2, with IP address 3, attached to it, even though I have done nothing at--just boot up, run ifconfig -a to see what's where, then shut down. Similarly, there's no pairing between NIC and IP address--these change on their own, also: NIC3 with IP address 1 on one bootup will have, on the next bootup, IP address 3 attached. Also, even editing the files directly, I could see no way to pin a NIC to a specific eth. How do I do that? Either I'm missing something or you're missing something. Those files are tied directly to a NIC, with the corresponding MAC address. They don't work with any other. Now eth0, eth1 etc., may wander around, but why is that an issue? Servers talk to IP addresses, not NICs. It's up to the IP stack to figure out which NIC to talk to. You shouldn't have any need to worry about whether a NIC is eth0 or not. James, I think you're assuming that the OP understands as much about this as you do. I went thru the same learning/aggravation cycle when I installed SuSE 9.3 on my firewall system. Eric, What you're encountering is a raceway condition that's set up during boot. What happens is that a whole bunch of initialization tasks are started in a batch, and whatever NIC is initialized first is named eth0, second is eth1, etc. There are actually several ways to work around what may be the dumbest design decision
[Samba] OT: SUSE 9.3 and NICs
Folks, I realize this is off topic, and if anyone can suggest a better source for the question, I'd be glad to go there. Novell SUSE's support is unresponsive, however. My problem is this: I'm running 9.3 Pro on an Intel server board that has two NIC chips built in (a 10/100 and a GigE). I've since added a Netgear GigE NIC. However, every time I reboot, the NICs assigned to eth0, 1, and 2 all change at random, as do the IP addresses assigned. This happens whether I do anything at all or try to set things up through YaST. I'm trying to set up two subnets off this (samba-run) server, with one NIC (or one IP address) facing the Net and the other two NICs (or IP addresses) having to go through this NIC to get to the Net. It would seem impossible to cable up the LAN if the NIC supporting a given subnet--and its address--keep changing. How can I stabilize the NIC/IP address/ethx assignments? What other information does anyone need to help me with this? Thanks very much. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Is it possible to write an smbclient automated script
At 12/23/05 01:04, Beast wrote: Pablo Graziano wrote: I'd like to write an automated smbclient script. Something simple, like: login cd to a certain directory copy that entire directory to client logout Is this possible, and how? Why not use smbmount instead? smbmount //svr/share /mnt/samba -o username=myuser,password=mypasswd cp -r /mnt/samba/source /tmp/destination --beast Wouldn't this transmit the password in the clear? Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba printing fails for Windows clients, was working, now fails...
At 12/21/05 06:48, Dennis B. Hopp wrote: activity superstore wrote: Hi all The printing via Samba+Cups has stopped working. I'm using Mandrake 10.0 Official as a Samba server for file sharing and printing on a Windows network. Printing from a WindowsXP client to the Samba server now fails and I don't know why it has suddenly stopped, it used to work. File sharing still works okay. There are on no errors logged on the Linux Samba box, the Windows application you try to print from just says not responding. I have used Knoppix as a client and the printing works from Samba, so it is just a Windows client to Linux Samba issue, but I can't figure it out. Any ideas? Samba version samba-server-3.0.2a-3mdk That's an old version of Samba. I got to imagine Mandrake (or Mandriva or whatever they are called now) has released a newer package. Can you try to upgrade? --Dennis Yes, but it was working. OP doesn't report changing anything, in particular, the OS or Samba. Why would it quit out of the blue? Could there be a print log file (or some such) that's gotten too big and hangs the print process? Could the print server itself (I use a Netgear doofer that plugs into the back of my Samsung) have failed? A Lynksys that I used prior to the Netgear did quit on me; replacing that got me my printing back. On the other hand, it probably would be worth the effort to upgrade Samba on GPs; 3.0.21 is sufficiently advanced over 3.0.2a that that's worth the effort in its own right. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] OT: NIC
Thanks. I'll switch. US Robotics' Tech Support is acting like usual--being unresponsive. Eric Hines At 12/20/05 02:12, Louis van Belle wrote: Hi, i use 100 mbit, 3com, intel pro100 Giga bit, intel pro1000 because both are good supported in kernel Louis -Original Message- From: Eric Hines[EMAIL PROTECTED] Sent: 19-12-05 17:47:04 To: samba@lists.samba.orgsamba@lists.samba.org Subject: [Samba] OT: NIC Folks, I'm trying to add a network interface card to my SUSE 9.3 box, and I'm not having much luck with a US Robotics version. What manufacturer do any of you use in your machines--either 10/100MB or GigE NIC? Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- 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 There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] OT: NIC
At 12/20/05 07:11, Nathan Vidican wrote: Eric Hines wrote: Folks, I'm trying to add a network interface card to my SUSE 9.3 box, and I'm not having much luck with a US Robotics version. What manufacturer do any of you use in your machines--either 10/100MB or GigE NIC? Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell HANDS-DOWN: Intel... never had nor used a better supported, more stable nor higher performing card than intel. Stick to the EtherExpress Pro lines, ie EtherExpress Pro 100/B PCI card for 10/100 - supported by almost any O/S right out of the box - even Win95 doesn't need a driver for it, I have suse/amd64 here using 4 of them in a box - works great :) -- Nathan Vidican [EMAIL PROTECTED] Windsor Match Plate Tool Ltd. http://www.wmptl.com/ Many thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Startup and/or Access Problem
I came into the middle of this conversation, but my 2 cents worth on your last question is that FC4 broke a lot of stuff that worked in FC3--so I moved to SUSE. The FCs, as I understand it, are beta versions of the proprietary RHELs--very good betas, to be sure, but still betas. Eric Hines At 12/20/05 10:51, Gene Poole wrote: First and foremost, thanks! I checked out the smb.log and there WERE 2 problems: 1. Undefined user (OK, I forgot to add the guest account) 2. The 'interfaces' parameter in the global section was incorrect. Once the two issues were corrected, everything started working just fine. One last question, why was it working under whatever Samba version running on FC3? Thanks, Gene Poole [EMAIL PROTECTED] snip There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RESOLVED RE: [Samba] OT: NIC
Thanks to all who responded. I wound up installing a Netgear GA311 10/100MB NIC. It went in smoothly and functions well. Eric Hines At 12/20/05 10:09, Joe Cipale wrote: To add my $0.02: Anything from Netgear or Intel will be your best choice. I have found US Robotics support to be spotty at best in nearly every linux flavor (SuSE, Mandrake, RH9/FC2) I have tried. Plus I( have a vested interest: I was a QA Engineer on many of the Intel NICs from the mid-90s to 200, so I have a pretty good idea of how well they operate. Joe Louis van Belle wrote: Hi, i use 100 mbit, 3com, intel pro100 Giga bit, intel pro1000 because both are good supported in kernel Louis -Original Message- From: Eric Hines[EMAIL PROTECTED] Sent: 19-12-05 17:47:04 To: samba@lists.samba.orgsamba@lists.samba.org Subject: [Samba] OT: NIC Folks, I'm trying to add a network interface card to my SUSE 9.3 box, and I'm not having much luck with a US Robotics version. What manufacturer do any of you use in your machines--either 10/100MB or GigE NIC? Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] OT: NIC Problem (Fwd: In response to your USRobotics technical support questions, your case #:300882125)
OK, this really is my last post on the matter; Adam brings up a valid point. SUSE Pro 9.3 (kernel 2.6.11.4-21.10) found the US Robotics NIC right off, but said it could not find a driver for it. My Netgear went right in, with SUSE finding that driver just fine. Both were, indeed, based on the RTL8169 chip (I assume USR's was, based on the delivered software directory structure and naming). I ran a standard installation of SUSE, right off Novell's DVDs. Netgear, among others, was mentioned in the list of drivers provided for YaST's manual configuration; no USR driver was in that list. Netgear's driver was present enough for YaST's automatic installation; USR's was not. The fact remains, though, that even were this a SUSE problem and not a USR one, USR's tech support could have answered my question the first time, and not the second. Eric Hines At 12/20/05 20:28, Adam Nielsen wrote: Hi Eric, which is supposed to contain the Linux kernel driver RTL8169 If that card is based on the RTL8169 chip, there's already a driver for it supplied with the Linux kernel. If compilied as a module, it's called r8169. I've been using it myself for about a year now without any problems. You could perhaps try that instead? Cheers, Adam. There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] OT: NIC
Folks, I'm trying to add a network interface card to my SUSE 9.3 box, and I'm not having much luck with a US Robotics version. What manufacturer do any of you use in your machines--either 10/100MB or GigE NIC? Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Basic samba/swat setup prob
At 12/18/05 09:49, Mathew D. Watson wrote: dave wrote: I am running kubuntu, samba 3.0.14a, my smb.conf file is ... [global] workgroup = METRAN encrypt passwords = yes [test] comment = For testing only, please path = /etc/samba/tmp read only = no guest ok = yes I have a /etc/samba/tmp directory, I am user dave on the system so I ... smbpasswd -a dave I gave it a password of 'testing', it complained that a file did not exist then created it for me ... all looked AOK I pointed my browser to http://localhost:901, an authentication dialogue popped up, I entered 'dave', 'testing' hopeing for the swat screen but all I get is authentication failed, retry. This is a guess, but try adding security = user to the [global] section. You might also try, as I did, using the /etc/samba/smb.conf file that came with the samba package. Then run swat, and use it to make your changes. Mat There are a couple of other things you might want to try: since you've gotten to the authentication dialog, it appears you have a proper swat config file (you might, though, compare yours to the one that's on pg 53 of Ts, et al.'s _Using Samba_ (O'Reilly pub), just to be sure. The biggie, though, is that, unless you explicitly set up swat to do otherwise, you need to log in as root to get it to run (don't forget to assign the same password for smbpasswd as you have for your root access for your kubuntu machine...). Anyone using swat can mess with your samba con fig file, and you don't want that--you should limit access to root, and that's the default access level for swat. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Basic samba/swat setup prob
At 12/18/05 10:58, dave s wrote: On Sunday 18 December 2005 16:47, Eric Hines wrote: At 12/18/05 09:49, Mathew D. Watson wrote: dave wrote: I am running kubuntu, samba 3.0.14a, my smb.conf file is ... [global] workgroup = METRAN encrypt passwords = yes [test] comment = For testing only, please path = /etc/samba/tmp read only = no guest ok = yes I have a /etc/samba/tmp directory, I am user dave on the system so I ... smbpasswd -a dave I gave it a password of 'testing', it complained that a file did not exist then created it for me ... all looked AOK I pointed my browser to http://localhost:901, an authentication dialogue popped up, I entered 'dave', 'testing' hopeing for the swat screen but all I get is authentication failed, retry. This is a guess, but try adding security = user to the [global] section. You might also try, as I did, using the /etc/samba/smb.conf file that came with the samba package. Then run swat, and use it to make your changes. Mat There are a couple of other things you might want to try: since you've gotten to the authentication dialog, it appears you have a proper swat config file (you might, though, compare yours to the one that's on pg 53 of Ts, et al.'s _Using Samba_ (O'Reilly pub), just to be sure. The biggie, though, is that, unless you explicitly set up swat to do otherwise, you need to log in as root to get it to run (don't forget to assign the same password for smbpasswd as you have for your root access for your kubuntu machine...). Thank you SO MUCH :) I have been wrestling with this problem for 2-3 weeks. It was complicated because kubuntu does not have a root password by default. Having setup a root password then smbpasswd -a and all is well :) !? I'm minded of Hamlet's injunction, Get thee to a nunnery, go. (Although nunnery was a rude slang term when Shakespeare was writing.) Generate a root user, promptly. Which you have done. I strongly urge you to go through the hassle of logging in as root (or su to root) whenever you want to make a system change of any sort. It's too easy to make system changes as an ordinary user that screw up the system, sometimes catastrophically. If you force yourself to do these as root only, you won't be proofed against those catastrophic errors, but you will be encouraged to make your changes only after prior thought, so the likelihood of those errors is minimized. One question, why does the smbpasswd have to be the same as the root password, apart from it therefore being easy to remember ? A more expert *NIX user can chime in here, but I suspect it has to do with you only getting one user called root, with those privileges. One password for both passwd and smbpasswd prevents password conflicts. Cheers Dave Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NT_STATUS_LOGON_FAILURE
I think the command should be: smbclient -L machinename -U Eric HInes At 12/16/05 13:39, Donald Musser wrote: Hi everyone, I'm using the online HOWTO manual in the Quick Start reference to try and get a basic domain controller going. So I set up smb.conf, and testparm checked out okay, I've started nmbd and smbd, but when I try to to run [EMAIL PROTECTED] samba]#smbclient -L username -Uusername%password session setup failed: NT_STATUS_LOGON_FAILURE -- I get this error Any ideas about what's causing this? I can post any relevant info as needed. -Myles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RESOLVED Re: [Samba] Upgrade Trouble w/ Samba 3.0.20b
At 12/10/05 22:56, Craig White wrote: On Sat, 2005-12-10 at 22:29 -0600, Eric Hines wrote: At 12/10/05 22:10, Craig White wrote: On Sat, 2005-12-10 at 20:04 -0600, Eric Hines wrote: I'm currently running SUSE Pro 9.3 with samba-3.0.13-1.1-SUSE, and I'm trying to upgrade to 3.0.20b. When I try to rpm -Uvh samba-3.0.20b and samba-client-3.0.20b, I get the failed dependency samba = 3.0.13 is needed by (installed) samba-vscan-0.3.5-37.2. How do I resolve this dependency? I'd prefer not to force it in, as that often generates more problems than it solves. Thanks for your help. worse comes to worse, you can remove samba-vscan and then re-install it - get the source-rpm and edit the SPEC file either commenting out the dependency or changing the dependency to the updated samba rpms that you have installed (but of course it sets you up for having to deal with it again). My thinking is that the samba-vscan could ***probably*** be installed with --nodeps (never done it myself) NEVER use --force unless you are prepared to live with the consequences. Craig OK, here's where I expose my ignorance. I did a find on samba-vscan (and on samba-vscan-0.3.5-37.2 in particular), and nothing turned up. The source file is an rpm, also, so how do I remove the vscan module? rpm -e samba-vscan Do you use the samba-vscan module? Craig Now that is brain dead to draw a blank like that Thanks for the pointer. Ultimately, I will use the virus scanner, but for now I sit behind very good hardware and software firewalls. And my email is first read (for now) on my Win2k PC, which has a virus scanner. At that point I'll try the --nodeps part and we'll both know. And I assume that virus in this context is used broadly to include trojans, worms, and all the other little virtual critters we've invented, the better to plague ourselves. Thanks for your help. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] password for swat
There are a couple of things you may need to do. One is to write a swat configuration file. There's a good example on page 53 of Ts, Eckstein, and Collier-Brown's _Using Samba_ (O'Reilly pub) that works well for Fedora Core and SUSE. You may need to tailor it some for your OS, but I think most of the tailoring will be in where you have to put the file. Also, the example includes the line only-from = localhost. You may need to change that to only-from = 127.0.0.1. Localhost almost always works, but sometimes it's necessary to use the IP address instead. Also, after having installed the file, don't forget to restart (or start in the first place) your inetd or xinetd--whichever daemon your OS uses. You also may need to add root's password to smbpasswd. Hope this helps. Eric Hines At 12/10/05 03:36, Roman Budzianowski wrote: I got SWAT running on OS X 10.4 and when I go to localhost:901 I am asked for password. However neither root nor admin work (I enabled root). I get: The name or password entered for area SWAT on localhost:901 was incorrect. Please try again. Thanks for help, Roman Budzianowski [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RESOLVED Re: [Samba] Share Connection Failure
Michael, Worked like a champ. Thanks for your help. Eric At 12/10/05 11:23, Michael Barnes wrote: Eric, Try changing your smb.conf file to: [accounts] valid users = @accounts force group = accounts (along with the other usual stuff) [finsvcs] valid users = @finsvcs force group = finsvcs (along with the other usual stuff) This will limit access to members of the appropriate group. It will also force all files created in those shares to be owned by the group, so other group members should have no problem using them. HTH, Michael Eric Hines told me on 12/7/2005 21:36: I'm at my wit's end on this, and I hope someone can help. I'm running SUSE Pro 9.3 with Samba 3.0.13, and I can't get connected to my shares properly. Valid users (e.g., for [accounts]) is set to %G, and I've confirmed that the users are members of the owning groups for the shares and that they are in the passwd and smbpasswd files with the same passwords as on the Win2k PC from which they're trying to gain access. Network Neighborhood browsing shows up the shares, but access is denied. The directory structure is: /data (owned by root:root) /data/accounts (owned by owner:group) When I try to gain access to [accounts] as ehines (one of the users), all I get is a dialog box saying incorrect password or unknown user name, and I'm invited to log in--which is then rejected, also. There is a [homes] share to which I gain access easily and correctly. I can gain access to [accounts] by logging in from the Win2k PC as root (yes, the UNIX root) and using the UNIX root password. However, once I've done that, no one else can ever gain access again--including to the [homes] share--until I reboot the PC. I know I'm dong something basic and brain dead wrong, but I can't find it. I've been through the TOSHARG2 and the Samba-3 documentation, but I'm not finding my error. I set system log to level 2, and following are the relevant parts of the smbd and winbindd logs: from log.smbd: [2005/12/07 20:53:47, 2] auth/auth.c:check_ntlm_password(305) check_ntlm_password: authentication for user [EHines] - [EHines] - [ehines] succeeded [2005/12/07 20:53:49, 2] smbd/service.c:make_connection_snum(321) user 'ehines' (from session setup) not permitted to access this share (accounts) [2005/12/07 20:53:49, 2] smbd/service.c:make_connection_snum(321) user 'ehines' (from session setup) not permitted to access this share (accounts) [2005/12/07 20:53:49, 2] smbd/service.c:make_connection_snum(321) user 'ehines' (from session setup) not permitted to access this share (accounts) [2005/12/07 20:53:49, 2] smbd/service.c:make_connection_snum(321) user 'ehines' (from session setup) not permitted to access this share (accounts) [2005/12/07 20:53:49, 2] smbd/service.c:make_connection_snum(321) user 'ehines' (from session setup) not permitted to access this share (accounts) [2005/12/07 20:53:49, 2] smbd/service.c:make_connection_snum(321) user 'ehines' (from session setup) not permitted to access this share (accounts) from log.winbindd: [2005/12/07 20:48:07, 0] nsswitch/winbindd_util.c:winbindd_param_init(555) winbindd: idmap uid range missing or invalid [2005/12/07 20:48:07, 0] nsswitch/winbindd_util.c:winbindd_param_init(556) winbindd: cannot continue, exiting. [2005/12/07 20:48:07, 1] nsswitch/winbindd.c:main(897) Could not init idmap -- netlogon proxy only Thanks for your help. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Upgrade Trouble w/ Samba 3.0.20b
I'm currently running SUSE Pro 9.3 with samba-3.0.13-1.1-SUSE, and I'm trying to upgrade to 3.0.20b. When I try to rpm -Uvh samba-3.0.20b and samba-client-3.0.20b, I get the failed dependency samba = 3.0.13 is needed by (installed) samba-vscan-0.3.5-37.2. How do I resolve this dependency? I'd prefer not to force it in, as that often generates more problems than it solves. Thanks for your help. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Upgrade Trouble w/ Samba 3.0.20b
At 12/10/05 22:10, Craig White wrote: On Sat, 2005-12-10 at 20:04 -0600, Eric Hines wrote: I'm currently running SUSE Pro 9.3 with samba-3.0.13-1.1-SUSE, and I'm trying to upgrade to 3.0.20b. When I try to rpm -Uvh samba-3.0.20b and samba-client-3.0.20b, I get the failed dependency samba = 3.0.13 is needed by (installed) samba-vscan-0.3.5-37.2. How do I resolve this dependency? I'd prefer not to force it in, as that often generates more problems than it solves. Thanks for your help. worse comes to worse, you can remove samba-vscan and then re-install it - get the source-rpm and edit the SPEC file either commenting out the dependency or changing the dependency to the updated samba rpms that you have installed (but of course it sets you up for having to deal with it again). My thinking is that the samba-vscan could ***probably*** be installed with --nodeps (never done it myself) NEVER use --force unless you are prepared to live with the consequences. Craig OK, here's where I expose my ignorance. I did a find on samba-vscan (and on samba-vscan-0.3.5-37.2 in particular), and nothing turned up. The source file is an rpm, also, so how do I remove the vscan module? Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] netlogon problems
Michael, This does help, but only when I get to that point. As I gain further understanding of my problem, it's that I can't get my users logged on in the first place, so as to get to the point of needing to be able to run the script. A better description of my problem is in the thread [Samba] Share Connection Failure. Can you offer any help there? Thanks Eric Hines At 12/09/05 08:47, Michael Barnes wrote: I just went through all this with my set up. First, insure the users have the desired group as their PRIMARY group in both NT groups and Unix groups. You can verify this by checking the /etc/passwd list and running 'pdbedit -Lv'. Change your [NETLOGON] entry to read 'path = /data/%g'. In your /data/ folder, create a login for each group, i.e. /data/finsvcs/scripts/login.bat; /data/accounts/scripts/login.bat; /data/others/scripts/login.bat; etc. Each login would reflect what you want for that group. For example: /data/finsvcs/scripts/login.bat: REM Login.bat for Financial Services Members net time \\lserver0 /set /yes net use m: \\lserver0\finsvcs net use x: /home HTH, Michael Eric Hines told me on 12/8/2005 19:43: You have not misunderstood my post; I have mis-described my problem. The logon script will not run until the user gets connected to his/her share on the samba server, and I cannot get the user connected in the first place. I have a better description of my problem (finally) under the thread [Samba] Share Connection Failure. Your points are valid, though, and I will take them to heart when I get the point of getting connected so that the logon script has a chance to run. Do you have any advice on the basic connection problem? Thanks Eric Hines At 12/08/05 01:25, Matthew Easton wrote: Pardon me if I misunderstand your post... I think you want to present a logon script to the user based on her/ his group membership. In other words, ( I surmise ) currently Fred gets an invitation to logon to finsvcs, but it will necessarily fail unless he is a member of the finance group. So you want him to have a logon script that DOES NOT mount finsvcs share if he is not a member of finance. I note that the logon script directive in you [global] settings has no value. In a small environment, you can make that logon script = /some/path/%u.bat and give each user a unique logon script. In a larger environment you want to control scripts by group membership--- check out http://lists.samba.org/archive/samba/2002-March/040656.html as an example of ways to control logon by group. On Dec 4, 2005, at 12:19 PM, Eric Hines wrote: Folks, I'm trying to achieve control over who logs into a share according to the group to which that person belongs, but with no luck. I'm running SUSE Pro 9.3 and Samba 3.0.13, with a Win2k machine on one subnet and an XP laptop on another subnet. In all cases, the user, instead of getting into his share transparently, gets invited to log in, and then the login is rejected. I've run the login.bat from the Windows machines, and that also only gets access denied. Share valid users is set to %G (%U lets the user in just fine, but that's inadequate security). Users get into their home directories just fine. My login.bat is net time \\lserver0 /set /yes net use \\lserver0\accounts net use \\lserver0\finsvcs net use x: /home My [netlogon] share is [netlogon] comment = Network logon service path = /data/%U valid users = %S read only = No My [global] is [global] workgroup = ASTRA_ENT username map = /etc/samba/smbusers syslog = 0 name resolve order = wins bcast hosts printcap name = CUPS show add printer wizard = No add user script = /usr/sbin/useradd -m '%u' delete user script = /usr/sbin/userdel -r '%u' add group script = /usr/sbin/groupadd '%g' delete group script = /usr/sbin/groupdel '%g' add user to group script = /usr/sbin/groupmod -G '%g' '%u' add machine script = /usr/sbin/useradd -s /bin/false -d / var/lib/nobody '%u' logon script = scripts\login.bat logon path = logon drive = X: domain logons = Yes preferred master = Yes wins support = Yes ldap ssl = no I've placed the login.bat file in the share accounts (\data \accounts and /data/financials in this case), and I've placed the login.bat file in each user's home directory. Nothing has worked. I've been through the TOSHARG2 with no luck, and Googleing hasn't brought me anything I recognized, either. Any help would be greatly appreciated. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] netlogon problems
You have not misunderstood my post; I have mis-described my problem. The logon script will not run until the user gets connected to his/her share on the samba server, and I cannot get the user connected in the first place. I have a better description of my problem (finally) under the thread [Samba] Share Connection Failure. Your points are valid, though, and I will take them to heart when I get the point of getting connected so that the logon script has a chance to run. Do you have any advice on the basic connection problem? Thanks Eric Hines At 12/08/05 01:25, Matthew Easton wrote: Pardon me if I misunderstand your post... I think you want to present a logon script to the user based on her/ his group membership. In other words, ( I surmise ) currently Fred gets an invitation to logon to finsvcs, but it will necessarily fail unless he is a member of the finance group. So you want him to have a logon script that DOES NOT mount finsvcs share if he is not a member of finance. I note that the logon script directive in you [global] settings has no value. In a small environment, you can make that logon script = /some/path/%u.bat and give each user a unique logon script. In a larger environment you want to control scripts by group membership--- check out http://lists.samba.org/archive/samba/2002-March/040656.html as an example of ways to control logon by group. On Dec 4, 2005, at 12:19 PM, Eric Hines wrote: Folks, I'm trying to achieve control over who logs into a share according to the group to which that person belongs, but with no luck. I'm running SUSE Pro 9.3 and Samba 3.0.13, with a Win2k machine on one subnet and an XP laptop on another subnet. In all cases, the user, instead of getting into his share transparently, gets invited to log in, and then the login is rejected. I've run the login.bat from the Windows machines, and that also only gets access denied. Share valid users is set to %G (%U lets the user in just fine, but that's inadequate security). Users get into their home directories just fine. My login.bat is net time \\lserver0 /set /yes net use \\lserver0\accounts net use \\lserver0\finsvcs net use x: /home My [netlogon] share is [netlogon] comment = Network logon service path = /data/%U valid users = %S read only = No My [global] is [global] workgroup = ASTRA_ENT username map = /etc/samba/smbusers syslog = 0 name resolve order = wins bcast hosts printcap name = CUPS show add printer wizard = No add user script = /usr/sbin/useradd -m '%u' delete user script = /usr/sbin/userdel -r '%u' add group script = /usr/sbin/groupadd '%g' delete group script = /usr/sbin/groupdel '%g' add user to group script = /usr/sbin/groupmod -G '%g' '%u' add machine script = /usr/sbin/useradd -s /bin/false -d / var/lib/nobody '%u' logon script = scripts\login.bat logon path = logon drive = X: domain logons = Yes preferred master = Yes wins support = Yes ldap ssl = no I've placed the login.bat file in the share accounts (\data \accounts and /data/financials in this case), and I've placed the login.bat file in each user's home directory. Nothing has worked. I've been through the TOSHARG2 with no luck, and Googleing hasn't brought me anything I recognized, either. Any help would be greatly appreciated. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Share Connection Failure
I'm at my wit's end on this, and I hope someone can help. I'm running SUSE Pro 9.3 with Samba 3.0.13, and I can't get connected to my shares properly. Valid users (e.g., for [accounts]) is set to %G, and I've confirmed that the users are members of the owning groups for the shares and that they are in the passwd and smbpasswd files with the same passwords as on the Win2k PC from which they're trying to gain access. Network Neighborhood browsing shows up the shares, but access is denied. The directory structure is: /data (owned by root:root) /data/accounts (owned by owner:group) When I try to gain access to [accounts] as ehines (one of the users), all I get is a dialog box saying incorrect password or unknown user name, and I'm invited to log in--which is then rejected, also. There is a [homes] share to which I gain access easily and correctly. I can gain access to [accounts] by logging in from the Win2k PC as root (yes, the UNIX root) and using the UNIX root password. However, once I've done that, no one else can ever gain access again--including to the [homes] share--until I reboot the PC. I know I'm dong something basic and brain dead wrong, but I can't find it. I've been through the TOSHARG2 and the Samba-3 documentation, but I'm not finding my error. I set system log to level 2, and following are the relevant parts of the smbd and winbindd logs: from log.smbd: [2005/12/07 20:53:47, 2] auth/auth.c:check_ntlm_password(305) check_ntlm_password: authentication for user [EHines] - [EHines] - [ehines] succeeded [2005/12/07 20:53:49, 2] smbd/service.c:make_connection_snum(321) user 'ehines' (from session setup) not permitted to access this share (accounts) [2005/12/07 20:53:49, 2] smbd/service.c:make_connection_snum(321) user 'ehines' (from session setup) not permitted to access this share (accounts) [2005/12/07 20:53:49, 2] smbd/service.c:make_connection_snum(321) user 'ehines' (from session setup) not permitted to access this share (accounts) [2005/12/07 20:53:49, 2] smbd/service.c:make_connection_snum(321) user 'ehines' (from session setup) not permitted to access this share (accounts) [2005/12/07 20:53:49, 2] smbd/service.c:make_connection_snum(321) user 'ehines' (from session setup) not permitted to access this share (accounts) [2005/12/07 20:53:49, 2] smbd/service.c:make_connection_snum(321) user 'ehines' (from session setup) not permitted to access this share (accounts) from log.winbindd: [2005/12/07 20:48:07, 0] nsswitch/winbindd_util.c:winbindd_param_init(555) winbindd: idmap uid range missing or invalid [2005/12/07 20:48:07, 0] nsswitch/winbindd_util.c:winbindd_param_init(556) winbindd: cannot continue, exiting. [2005/12/07 20:48:07, 1] nsswitch/winbindd.c:main(897) Could not init idmap -- netlogon proxy only Thanks for your help. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] User Primary group problem
According to my SUSE man pages, adduser -g makes the group named after the g switch the primary group of the user named at the end of the command. Eric Hines At 12/06/05 19:29, Michael Barnes wrote: This only makes the user a member of a group. It does not change the PRIMARY GROUP of the user. Ideally, I want to set the primary group of the user at the time of user creation. Lacking that, I'd like to be able to change the user's primary NTgroup and Unixgroup at the same time. Michael Craig White told me on 12/6/2005 18:30: On Tue, 2005-12-06 at 14:08 -0600, Michael Barnes wrote: How do I establish both a user's primary NTgroup and Unixgroup when creating a new user? Depending on the tool, I can set his NTgroup or his Unix group, but I don't seem to be able to establish both with one tool. man smb.conf Example: add user to group script = /usr/sbin/adduser %u %g Craig -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] User Primary group problem
Interesting. I had occasion to use usermod -g (per my man pages, again, the g switch with usermod changes the primary group to the new one) to change my primary group. It left my (previously existing) home directory owned by me:users (as it was originally created), but new stuff that I did within my home directory (and elsewhere) became owned by me:new primary group. I've never used usrmgr, and I've never had trouble (except my own brain dead errors) with useradd or usermod. Eric Hines At 12/06/05 20:19, Michael Barnes wrote: That's what my man page says, also. However, when applied to the adduser script portion of smb.conf, it breaks usrmgr, which is the recommended tool for adding users. Further, after the user is created, if I change the primary group in usrmgr, it only changes the NTgroup, not the Unixgroup :-( So, I have to go back to the command line and do a usermod to set the Unix group correctly. And, if that isn't bad enough, it creates the users home folder owned by root:root, so I have to do a chown to change it to user:user. Sigh. Michael Eric Hines told me on 12/6/2005 20:21: According to my SUSE man pages, adduser -g makes the group named after the g switch the primary group of the user named at the end of the command. Eric Hines At 12/06/05 19:29, Michael Barnes wrote: This only makes the user a member of a group. It does not change the PRIMARY GROUP of the user. Ideally, I want to set the primary group of the user at the time of user creation. Lacking that, I'd like to be able to change the user's primary NTgroup and Unixgroup at the same time. Michael Craig White told me on 12/6/2005 18:30: On Tue, 2005-12-06 at 14:08 -0600, Michael Barnes wrote: How do I establish both a user's primary NTgroup and Unixgroup when creating a new user? Depending on the tool, I can set his NTgroup or his Unix group, but I don't seem to be able to establish both with one tool. man smb.conf Example: add user to group script = /usr/sbin/adduser %u %g Craig -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] netlogon problems
Folks, I'm trying to achieve control over who logs into a share according to the group to which that person belongs, but with no luck. I'm running SUSE Pro 9.3 and Samba 3.0.13, with a Win2k machine on one subnet and an XP laptop on another subnet. In all cases, the user, instead of getting into his share transparently, gets invited to log in, and then the login is rejected. I've run the login.bat from the Windows machines, and that also only gets access denied. Share valid users is set to %G (%U lets the user in just fine, but that's inadequate security). Users get into their home directories just fine. My login.bat is net time \\lserver0 /set /yes net use \\lserver0\accounts net use \\lserver0\finsvcs net use x: /home My [netlogon] share is [netlogon] comment = Network logon service path = /data/%U valid users = %S read only = No My [global] is [global] workgroup = ASTRA_ENT username map = /etc/samba/smbusers syslog = 0 name resolve order = wins bcast hosts printcap name = CUPS show add printer wizard = No add user script = /usr/sbin/useradd -m '%u' delete user script = /usr/sbin/userdel -r '%u' add group script = /usr/sbin/groupadd '%g' delete group script = /usr/sbin/groupdel '%g' add user to group script = /usr/sbin/groupmod -G '%g' '%u' add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u' logon script = scripts\login.bat logon path = logon drive = X: domain logons = Yes preferred master = Yes wins support = Yes ldap ssl = no I've placed the login.bat file in the share accounts (\data\accounts and /data/financials in this case), and I've placed the login.bat file in each user's home directory. Nothing has worked. I've been through the TOSHARG2 with no luck, and Googleing hasn't brought me anything I recognized, either. Any help would be greatly appreciated. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RESOLVED? [Samba] Shares Problem
Folks, snip Folks, I'm running SUSE Pro 9.3 with Samba 3.0.13, and I have LAN with 2 subnets. The problem (or the symptom; I may actually have two problems) is that I can't get into some of the shares from my Win2k box (one subnet) or from my XP laptop (other subnet). The directory structure is /data /data/accounts /data/finsvcs and the shares are accounts and finsvcs. /data is owned by root:root, while the share directories are owned by mfwic:accounts and mfwic:finsvcs. Each user can get into his own /home/directory just fine, and I've confirmed that the users are correctly entered in the passwd and smbpasswd files (as also implied by being able to get into the /home directories). User access to the shares is granted via valid user=%G. From the windows devices, it's possible to browse over to (or to go via Network Neighborhood), and see, the shares, but entering is denied--the Windows devices invite me to log in and then reject the login. Winbindd is running, and the windows devices are pointed to the samba box for the WINS service. I've run the checklist from TOSHARG2, and the only items that _don't_ work are smbclient //lserver0/accounts -Uuser (including mfwic). That gets me a tree connect failed: NT_STATUS_ACCESS_DENIED error. However, if I run smbclient //lserver0/accounts -Uroot with the root password, I get into the shares. I cannot ping by name the machines (PC and laptop) from lserver0, the samba box, or lserver0 from the windows machine. I can ping in both directions by IP address. nmblookup -B xxx '*' works when xxx=IP address, fails when xxx=machine name. net use x: \\lserver0\accounts fails with a bad password error from my Win2k PC, and with a multiple connections not allowed error from my XP laptop. Any advice would be greatly appreciated. Eric Hines I got this to work, but I don't understand why, or what the implications are on the change I made. Any advice would be greatly appreciated. The change I made was to change valid users for the shares accounts and finsvcs to %U from %G. The documentation says that %G is the _primary_ group of the user in question; the primary group of these users, from the way they were first entered into the system is 'users;' they were only after that _added_ to the groups owning the shares' directories. Could this be part of problem, or is that a non-distinction? Also, what am I doing to security by allowing the session user in and not mandating that that person be a member of the share-owning group? Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Shares Problem
Folks, I'm running SUSE Pro 9.3 with Samba 3.0.13, and I have LAN with 2 subnets. The problem (or the symptom; I may actually have two problems) is that I can't get into some of the shares from my Win2k box (one subnet) or from my XP laptop (other subnet). The directory structure is /data /data/accounts /data/finsvcs and the shares are accounts and finsvcs. /data is owned by root:root, while the share directories are owned by mfwic:accounts and mfwic:finsvcs. Each user can get into his own /home/directory just fine, and I've confirmed that the users are correctly entered in the passwd and smbpasswd files (as also implied by being able to get into the /home directories). User access to the shares is granted via valid user=%G. From the windows devices, it's possible to browse over to (or to go via Network Neighborhood), and see, the shares, but entering is denied--the Windows devices invite me to log in and then reject the login. Winbindd is running, and the windows devices are pointed to the samba box for the WINS service. I've run the checklist from TOSHARG2, and the only items that _don't_ work are smbclient //lserver0/accounts -Uuser (including mfwic). That gets me a tree connect failed: NT_STATUS_ACCESS_DENIED error. However, if I run smbclient //lserver0/accounts -Uroot with the root password, I get into the shares. I cannot ping by name the machines (PC and laptop) from lserver0, the samba box, or lserver0 from the windows machine. I can ping in both directions by IP address. nmblookup -B xxx '*' works when xxx=IP address, fails when xxx=machine name. net use x: \\lserver0\accounts fails with a bad password error from my Win2k PC, and with a multiple connections not allowed error from my XP laptop. Any advice would be greatly appreciated. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Basic Setup Problem
Gentlemen: This is an embarrassingly basic problem; I'm obviously doing something fundamentally wrong. I'm running SUSE Professional 9.3 and Samba 3.0.13 (I'm trying to upgrade to 3.0.20b, but I get a dependency error--that's another story). My problem is this: I'm trying to set up John Terpstra's Example 1.2.1 from his Samba by Example (I told you this was basic), but when I run smbclient -L lerver0 -Uroot%password (the real one), all I get is NT_STATUS_LOGON_FAILURE. smbclient -L localhost U% works correctly. Testparm indicates the smb.conf is at least syntactically correct. ps indicates that smbd and nmbd are both running. Finally, I've confirmed that root is in smbpasswd and has the same password and the overall Linux box (I've even reset it in smbpasswd to be sure). Any help would be appreciated. Eric Hines One of the natural consequences of socialism is that a few stand in judgment of many, and make their choices for them. --Amit Varma -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RESOLVED: Fwd: Re: [Samba] Basic Setup Problem
Date: Sat, 26 Nov 2005 21:39:28 -0600 To: Craig White [EMAIL PROTECTED] From: Eric Hines [EMAIL PROTECTED] Subject: Re: [Samba] Basic Setup Problem snip 1) your point is valid about the password; I was following the example as exactly as I could. 2) there is no difference between smbclient -L localhost -U root and lserver0 -U root--both fail with the LOGON_FAILURE message. It acts like I've got the user Root set up wrong, somehow; the anonymous look (smbclient ... -U%) works correctly. I'm also having trouble getting in from a Win2k PC and an XP laptop, but I suspect the present problem underlies that problem. 3) wins support isn't relevant to this example, but I turned that on, anyway, and got no change. 4) my very basic smb.conf, as set up by the example, follows. # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2005/11/26 18:36:19 # Global parameters [global] workgroup = ASTRA_ENT security = SERVER - s/b security = user Craig I'll bite: why? I mean, I understand from a security standpoint you're right--server level security is suboptimal; however, in the example scenario, the company was uninterested in security, and security = server ought to have been OK--and it was what the example called for. I changed to security = user, and smbclient -L localhost/lserver0 both worked correctly. Now, however, the other problem to which I alluded remains. I can only get into the share from my Win2k or my XP machines as root. I should be able to go right in: guest ok = yes. Thanks Eric Hines First, my apologies for the direct replies; I was banging the REPLY button without paying attention to the fact that the replies were not going to the list. Second, the second problem--not being able to get in from a Windows box except as root--is also fixed--another of my stupid errors: security s/b SHARE, not SERVER. Thanks for your patience. Eric Hines -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] remove wins entries - samba 3
Geoff, Sorry about the hour; I didn't realize you were still up--I went to bed A number of questions, and some updates. I can find no evidence of active named logging, although I did find one log with named entries. In particular, what is the relevant log(s)? There is no syslog or system log. Running a FIND on *log didn't turn up anything even remotely close. I've obviously not got logging turned on properly I also notice that, where John's example has several instantiations of named running, I have only one, and it's very difficult to terminate that one--I have to kill pid to do it. Service daemon restart works fine for all the others, and service named start works fine, too. Just service stop/restart do not work--the latter hangs on the stop part. In the files below, why all the changes to mail from lserver1? I thought from John's examples these were supposed to be the server name? Geoff Scott wrote: Eric Hines wrote: Geoff Scott wrote: What do your logs say for bind starting up? Can you restart bind and watch your logs? Do you have any errors for it? f you mean winbind, a tail -f on log.winbindd just showed it No Berkely Internet Name Daemon - BIND The daemon is actually named named Grep for the entries for that daemon (named)in the relevant log, /var/log/... Syslog? In log /var/log/messages, named starts successfully, loads all the zone files OK, and it outputs the log entry lame server resolving 'lserver1.test.biz' (in 'test.biz'?): 206.16.250.17#53, also ... .18#53 several times. These are owned by a company in Barcelona, Spain. There also are cases (fewer) of resolving localhost.lserver1.test.biz to the same IP addresses/ports. tail -f messages and pinging lserver1 produced no immediate result. I could find no other log that had named entires in it. According to log.nmbd, Samba server LSERVER1 and samba name server LSERVER1 repeatedly became domain master browser and local master browser, respectively, on 192.168.1.103. tail -f log.nmbd also did not respond to an unsuccessful ping of lserver1. You asked whether I could tell my router/firewall not to send dhcp stuff to lserver1 only. That would take a specific MAC address exclusion capability, and this router/firewall does not have that. Can I, instead, tell lserver1 not to look to the router/firewall, but only to look to itself (/e.g./, via the dhcpd.conf or via lserver1's System Settings|Network GUI, using the DNS and/or hosts tab)? Or would that lock lserver1 into itself, never to get access to the Internet? I've done some other poking around in response to the DNS doc for which you sent me the URL last night, and noticed these things: /etc/sysconfig/networking/devices/ifcfg-eth0 is set as follows (emphasis added) DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes TYPE=Ethernet DHCP_HOSTNAME=*lserver1* I have the same thing for eth1 (there are two NIC chips on the motherboard), except it's turned off. dhcpd.leases has pserver1 (my print server) at 192.168.1.96, even though it's hardwired via its own setup functionality to a static address of 198.162.1.10, and it responds to pings at the .10 address. Finally, I made the zone file changes, and I still cannot ping lserver1 or lserver1.test.biz--unknown host in both cases. snip Regards Geoff Scott -- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] *Funding available ID:Yptrffhh2622165837
In the US snail mail doesn't work like that. Mail gets returned to the sender for insufficient postage. Eric Hines Louis van Belle wrote: So to all companies, please spam them. in The Netherlands Spam to companies is allowed ;-) ( for now, law is comming ) And Just send them Mail not email mail, but dont put a stamp on it. and i can send 9 Kilogram without stamp :D make them pay the . ( you know ) ;-) snip -- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] *Funding available ID:Yptrffhh2622165837
The call trick also works in reverse. Shortly after the PRC started minting their Panda gold coins, I got a long distance call (MI to NM, and in those days, Ma Bell was still a regulated monopoly--that call's per minute rate was not low) from a broker offering to let me in on the ground floor of buying a supply of these wonderful, valuable collector's items for only a little above the face value of those coins. He called just as I was sitting down to supper after painting my house, so I was in a bad mood (I hate painting houses). Rather than blowing him off and hanging up, though, I engaged him in conversation about the relative merits of gold bullion vs gold coins, the gold coins of other nations (including the US) as collector's items, the investing value of collector's item gold coins vs the value of simply buying bullion, where we thought the price of gold was going, and in which nation as its economy evolved, the value of gold vs silver, platinum, mines, other commodities in general (I even got him onto coal for a little bit). I kept him on the phone on his nickel (lots of them) for an hour. And at the end, when he asked if I were going to buy any Pandas, and I said no, hadn't he been listening, I could hear the phone slam down on his end. I not only never heard from that company again, but for the next several months the number of cold calls coming in offering me any good deals was a good approximation of zero. Eric Hines Jeff Frantz wrote: Just give them a call at their toll-free number: 866-322-3376 It costs them money and you can annoy the crap out of them. I just called and someone actually answered. I told her to expect lots of calls! -Jeff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Louis van Belle Sent: Wednesday, July 06, 2005 10:42 AM To: samba@lists.samba.org Subject: RE: [Samba] *Funding available ID:Yptrffhh2622165837 So to all companies, please spam them. in The Netherlands Spam to companies is allowed ;-) ( for now, law is comming ) And Just send them Mail not email mail, but dont put a stamp on it. and i can send 9 Kilogram without stamp :D make them pay the . ( you know ) ;-) Registrant: Canadian Publications ATTN: 3223376.NET c/o Network Solutions P.O. Box 447 Herndon, VA. 20172-0447 Domain Name: 3223376.NET Administrative Contact: Canadian Publications [EMAIL PROTECTED] tration.com ATTN: 3223376.NET c/o Network Solutions P.O. Box 447 Herndon, VA 20172-0447 570-708-8780 Technical Contact: Network Solutions, LLC. [EMAIL PROTECTED] 13200 Woodland Park Drive Herndon, VA 20171-3025 US 1-888-642-9675 fax: 571-434-4620 Record expires on 03-Sep-2005. Record created on 03-Sep-2004. Database last updated on 6-Jul-2005 10:38:27 EDT. Domain servers in listed order: NS1.ANZWERSNET.BIZ 211.140.139.108 NS2.ANZWERSNET.BIZ 218.5.74.47 -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens [EMAIL PROTECTED] Verzonden: dinsdag 5 juli 2005 16:26 Aan: [EMAIL PROTECTED] Onderwerp: [Samba] *Funding available ID:Yptrffhh2622165837 *Government financing available Business publications 4865 hwy 138 r.r. 1 St-Andrews w. On K0C 2A0 The most complete and affordable reference for anyone looking for financing. It is the perfect tool for new and existing businesses, individuals, foundations and associations Complete guide containing more than 3000 programs New 2005 edition Legal Deposit-National Library of Canada Business.$ 69.95 CD-Rom Academic printed$ 149.95 (430 pages) Toll free: 8 6 63 2 23 3 7 6 0844126086724032056340070710664410403075403008Pupncrjknq -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [Fwd: Samba-3 By Ex Chapt 3]
Yes, I am--or at least I think so; the daemon is running, and it's configured according the the Chapt 3 example. The /etc/resolv.conf file says it's written by /etc/dhclient-script, so I disabled that file, adjusted the resolv and tried again. No effect. Also, during reboot, when dhcpd started up, I got the error message Not configured to listen on any interface. Wrote 5 new leases. When the reboot completed, I had no Internet connection whatsoever. I had to re-enable dhclient-script and reboot. So I remain with the problems that I have no DNS resolution capability, and I cannot edit, with permanence, /etc/resolv.conf. I'd probably be satisfied with the latter if I could get DNS to work. Thanks Eric Hines Chris Nicholls wrote: Are you using dhcp to get an IP address on that server? Every time dhcpcd gets an IP address it overwrites the resolv.conf. So I think that's why it's changing every time you reboot. dhcpcd can be run with the -R option to prevent it from overwriting resolv.conf (check out the dhcpcd man page). I'm not sure where you'd specify that as i don't use FC. But it's probably easier to just give that machine a static IP. Chris Eric Hines wrote: One more thing I forgot to mention. The chapter calls for editing /etc/resolv.conf, but in my case it won't stay edited--it keeps getting set back to an original form (for searching my ISP) on every reboot. Thanks again. snip I'm running Samba v 3.0.14a on an FC3 machine. I've got two basic problems: one centers on my DNS set up and the other is an authenticated logon problem. With /etc/nsswitch.conf set to hosts: dns, I cannot ping my samba server--Host not found. Nor does host lserver1.test.biz (which appears in my /etc/hosts file) resolve the name (incidentally, host -f ... just tells me the f is an illegal option). WINS seems to resolve OK (at least the test for that in the chapter passes). I've checked my files several times, and I can find no error in them. snip Any help on these two would be greatly appreciated. Eric Hines -- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Question regarding SWAT
I had a similar problem, and the only way I could get SWAT to come up
(I'm still not sure I should have to--what's name resolution for?) was
to use, in the swat file:
only_from = 127.0.0.1
instead of
only_from = localhost
Eric Hines
[EMAIL PROTECTED] wrote:
Hi everyone,
In the last few days I've spended hours and hours on the web surching for a
solution to my problems. Eventhough it looked like there where several other
people having the same problem I couldn't find a way to solve it.
Therefore I'm hoping that one of you could help me with the following problem.
I've installed Samba 3.0.14a on RedHat 9.0. Samba is working perfectly.
But the problem lies with SWAT. When I type in my browser
http://localhost:901; I get the following error:
Connection was refused when attempting to contact localhost:901
My config files look like this:
--/etc/xinetd.conf--
#
# Simple configuration file for xinetd
#
# Some defaults, and include /etc/xinetd.d/
defaults
{
instances = 60
log_type= SYSLOG authpriv
log_on_success = HOST PID
log_on_failure = HOST
cps = 25 30
}
includedir /etc/xinetd.d
swat stream tcp nowait.400 root /usr/sbin/swat swat
--/etc/xinetd.d/swat
# default: off
# description: SWAT is the Samba Web Admin Tool. Use swat \
# to configure your Samba server. To use SWAT, \
# connect to port 901 with your favorite web browser.
service swat
{
disable = no
port= 901
socket_type = stream
wait= no
only_from = localhost
user= root
server = /usr/sbin/swat
log_on_failure += USERID
}
--
and in my services I've added the line: swat 901/tcp
I'm not using a firewall.
So, the service samba is working fine, but when I start xinetd he failes.
service xinetd status then gives : xinetd dead but pid file exists.
When I look into my /var/log/messages I come across the following statements:
---
Jul 6 15:12:33 localhost xinetd: xinetd shutdown failed
Jul 6 15:12:33 localhost xinetd[2456]: missing service keyword [line=20]
Jul 6 15:12:33 localhost xinetd[2456]: missing } in last service entry
[line=20]
Jul 6 15:12:33 localhost xinetd[2456]: 2456 {general_handler} (2456)
Unexpected signal: 11 (Segmentation fault)
Jul 6 15:12:33 localhost last message repeated 9 times
Jul 6 15:12:33 localhost xinetd[2456]: 2456 {bad_signal} Received 10 signals
in 1 seconds. Exiting...
Jul 6 15:12:33 localhost xinetd: xinetd startup succeeded
But I can't find the file where the } is missing in line 20.
I trully hope someone could help me with this because I really really want to
get this working.
I would be very thankfull, if you got some usefull info.
Thanks,
P.J. Wolters
--
He can compress the most words into the smallest ideas of any man
I ever met.
- Abraham Lincoln
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [Fwd: Samba-3 By Ex Chapt 3]
I tried both versions of /etc/dhclient-enter-hooks below, and in each
case, following a reboot my /etc/resolv.conf was overwritten to its
original form by dhclient-script.
Unless this is related to my DNS functionality, which I've written IAW
BYEXAMPLE Chapt 3 (although, apparently not, as it doesn't work), not
working, I'd just as soon focus on that, for the time being. Thanks for
all the help on /etc/resolv.conf, though, that most assuredly was not
time wasted. It'll be useful when I come back to this problem.
Eric Hines
Dwight Tovey wrote:
Eric Hines said:
snip
So I remain with the problems that I have no DNS resolution capability,
and I cannot edit, with permanence, /etc/resolv.conf. I'd probably be
satisfied with the latter if I could get DNS to work.
You can tell dhclient to get the IP address and gateway info, but to
ignore what the server tells it to do for the DNS server. Look at the man
pages for dhclient-script. If you create an executable script called
/etc/dhclient-enter-hooks and in there define the function
'make_resolv_conf()', you can override how your /etc/resolv.conf gets
handled. I have one on a FC3 machine at home. I can't get to it at the
moment, but from memory I believe that you can do something like this in
dhclient-enter-hooks:
===8-
#!/bin/bash
make_resolv_conf() {
cat /etc/resolv.conf EOF
search mydomain.net
nameserver 192.168.52.1
EOF
}
===8-
Of course, you could also just define make_resolv_conf() as an empty
function and it will just leave the current /etc/resolv.conf alone.
/dwight
--
He can compress the most words into the smallest ideas of any man
I ever met.
- Abraham Lincoln
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] remove wins entries - samba 3
Hi, Farshad, I'm too new at this to be of much help. My WINS seems to be working, but I'm clueless as to why, just as I'm clueless as to why my DNS is not working. Eric Hines Farshad Abasi wrote: Hi, I am having the same problem. Did you figure out how to do this? Any help in how to remove stale WINS entries from Samba would be greatly appreciated. Cheers, -farshad -- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [Fwd: Samba-3 By Ex Chapt 3]
Geoff Scott wrote: Eric Hines wrote: Geoff, What do your logs say about NT_STATUS_LOGON_FAILURE for the stuff below? What type of sam are you running? Ldapsam / tdbsam ? It's set for tdbsam. I've not got that set up right, though, according to the smbd log. I've frankly walked away from this problem, though, until I get DNS resolution running. My WINS does seem to be, tested with nsswitch set solely to wins. Now it's set back to hosts: files dns wins. I've been in log.nmbd, log.smbd, log.winbindd, and smbd. Smbd yells about Unable to open TDB rid database! There's a pretty clear hint; I just haven't had time to pursue it. There was a thread titled logon.bat that started a bit before this one. Have a look at that for example logon script settings. I'm studying that, too. That may help with my logon problem, but it doesn't address my DNS problem. When I run the logon.bat file from my Win2k box, I get the following in a DOS window: net time \\lserver1 /set /yes System error 5 has occurred. I'd guess that would work if you had wins set in your nsswitch It is, though: hosts: files dns wins Access is denied. net use h: /home The user's home directory has not been specified. Well that's just clearly wrong. As John said in that post I mentioned: net use o: %LOGONSERVER%\sharename Or net use o: \\lserver1\sharename But none of those is going to work unles name resolution is working. Particularly wins for this example. Agree on both. I still need to study John's post, but I'm concentrating on getting DNS to work for now. WINS does seem to be working. Regards Geoff Scott Thanks Eric Hines -- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] remove wins entries - samba 3
I have the following setup. It's not fancy as I'm just trying to learn Linux and Samba. My test LAN consists of a Win2k, SP4 box (mustelidae) and an FC3 (kernel 2.6.11-1.35_FC3) server (lserver1) running Samba 3.0.14a. A Samsung printer also is present via a print server plugged into its back. I can print to it from lserver1, although the URI for the printer uses its IP address, so this probably doesn't mean much. As mustelidae also can be on a larger home LAN with access to the Internet, and lserver1 also has access to the Internet, the whole arrangement sits behind an 8-port Linksys router/firewall. As I have only a 2 box set up, I'm only struggling with one subnet out of the two that John has in his BYEXAMPLE book (adding a second subnet ought to be a piece of cake after I get this part running and understood). My DNS server sits on lserver1. I'm trying to ping lserver1 from lserver1. With nsswitch set only to files or only to wins (/e.g./, hosts: files), this is successful. With nsswitch set only to dns, I cannot get name resolution, although I can successfully ping by IP address. I can ping lserver1 by name or by IP successfully from mustelidae. Where is lserver1 pointing in terms of DNS? How do I tell? At this point, all I can say is that I've set up named.conf (and dhcpd.conf) as John has them in his Chapt 3 example, with the sole differences being that I'm using one subnet and not two (a DHCP issue), I'm calling my server lserver1.test.biz, vice diamond.abmas.biz, and lserver1's IP address is 192.168.1.103, vice the one John's using in his example. Aside from these edits, named.conf (and dhcpd.conf) are cut and pastes from John's latest on line. Is /etc/resolv.conf part of this answer? That's the file I can't keep from being overwritten by dhclient-script, even with the two dhclient-enter-hooks examples posted earlier today. Same, probably not very responsive, answer for whether this DNS server has the records to do with lserver1. The router/firewall has its own DHCP server, and it gets its config from our ISP and from a list of DNS servers that were loaded into the router/firewall when it was provisioned. lserver1 gets it address from this router. There's been some discussion earlier of the wisdom of this, but it's a stable address, if not static, as it's a long-term lease. I do intend to put lserver1 onto a static address, but only after I've worked out all the files that have lserver1 stored by its current address, so I can keep them current. Lserver1's address hasn't changed in months, and as I'm on it daily, its address won't change anytime soon under the present arrangement. My named.conf and dhcpd.conf are built from John's example, as mentioned above. /Etc/hosts has the IP address/name pairs he calls for. I think that means I'm running a local name server. As you can see, I have very little understanding of what's going on here; I've rather slavishly followed John's example, and I'm clearly making mistakes I'm not recognizing. Thanks Eric Hines Geoff Scott wrote: Eric Hines wrote: Hi, Farshad, I'm too new at this to be of much help. My WINS seems to be working, but I'm clueless as to why, just as I'm clueless as to why my DNS is not working. Eric Hines The questions you need to ask yourself are simple. Where is my DNS server? Where is my machine that I am pinging from pointing to in terms of DNS? Does that DNS server have the records to do with my lserver1 samba server? Are you running a local name server as per JHT's docs? Are you pointing your DNS on your lserver1 samba server to an external name server? Answer each of these questions for us and we'll see where we can help. Regards Geoff Scott -- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Can't get Local DNS to Run [Was[[Samba] remove wins entries - samba 3]]
Further on this. I just ran an ethereal trace on an attempt to ping lserver1 from lserver1, and it appears that my DNS isn't staying local at all, but I have no idea what's gone wrong (other than my /etc/resolv.conf file). The trace (I'd include the relevant parts, but I can't get it to save anything in textual form) had lserver1.test.biz going out through the router/firewall for resolution. As the firewall strips the local domain stuff and appends instead the ISP's domain stuff, the request, going to the ISP, was for lserver1.hsd1.etc.etc. And of course, the answer came back, Who? Hence no resolution. I'm not sure of the role of /etc/resolv.conf in all this, though. When I do edit that file per John's example and don't reboot, but merely restart everything (named, dhcpd (I don't know about the client side of this), smbd, and winbindd), the resolv.conf remains as I edited it, but I still can't get local name resolution. Whether I have the IP address in John's example, or lserver1's address, I get no name resolution. Also, with only the domain parts (e.g., test.biz test.us) of the machine names present in the search line I can't restart smb--it just hangs. If I put an FQN in the search line (lserver1.test.biz), which is what dhclient-script does when it rewrites the file, then smb restarts OK. Also, John's example has several instantiations of named running; I have only one. Eric Hines Original Message Subject:Re: [Samba] remove wins entries - samba 3 Date: Wed, 06 Jul 2005 21:20:55 -0500 From: Eric Hines [EMAIL PROTECTED] To: samba@lists.samba.org References: [EMAIL PROTECTED] I have the following setup. It's not fancy as I'm just trying to learn Linux and Samba. My test LAN consists of a Win2k, SP4 box (mustelidae) and an FC3 (kernel 2.6.11-1.35_FC3) server (lserver1) running Samba 3.0.14a. A Samsung printer also is present via a print server plugged into its back. I can print to it from lserver1, although the URI for the printer uses its IP address, so this probably doesn't mean much. As mustelidae also can be on a larger home LAN with access to the Internet, and lserver1 also has access to the Internet, the whole arrangement sits behind an 8-port Linksys router/firewall. As I have only a 2 box set up, I'm only struggling with one subnet out of the two that John has in his BYEXAMPLE book (adding a second subnet ought to be a piece of cake after I get this part running and understood). My DNS server sits on lserver1. I'm trying to ping lserver1 from lserver1. With nsswitch set only to files or only to wins (/e.g./, hosts: files), this is successful. With nsswitch set only to dns, I cannot get name resolution, although I can successfully ping by IP address. I can ping lserver1 by name or by IP successfully from mustelidae. Where is lserver1 pointing in terms of DNS? How do I tell? At this point, all I can say is that I've set up named.conf (and dhcpd.conf) as John has them in his Chapt 3 example, with the sole differences being that I'm using one subnet and not two (a DHCP issue), I'm calling my server lserver1.test.biz, vice diamond.abmas.biz, and lserver1's IP address is 192.168.1.103, vice the one John's using in his example. Aside from these edits, named.conf (and dhcpd.conf) are cut and pastes from John's latest on line. Is /etc/resolv.conf part of this answer? That's the file I can't keep from being overwritten by dhclient-script, even with the two dhclient-enter-hooks examples posted earlier today. Same, probably not very responsive, answer for whether this DNS server has the records to do with lserver1. The router/firewall has its own DHCP server, and it gets its config from our ISP and from a list of DNS servers that were loaded into the router/firewall when it was provisioned. lserver1 gets it address from this router. There's been some discussion earlier of the wisdom of this, but it's a stable address, if not static, as it's a long-term lease. I do intend to put lserver1 onto a static address, but only after I've worked out all the files that have lserver1 stored by its current address, so I can keep them current. Lserver1's address hasn't changed in months, and as I'm on it daily, its address won't change anytime soon under the present arrangement. My named.conf and dhcpd.conf are built from John's example, as mentioned above. /Etc/hosts has the IP address/name pairs he calls for. I think that means I'm running a local name server. As you can see, I have very little understanding of what's going on here; I've rather slavishly followed John's example, and I'm clearly making mistakes I'm not recognizing. Thanks Eric Hines Geoff Scott wrote: Eric Hines wrote: Hi, Farshad, I'm too new at this to be of much help. My WINS seems to be working, but I'm clueless as to why, just as I'm clueless as to why my DNS is not working. Eric Hines
Re: [Samba] remove wins entries - samba 3
Geoff Scott wrote:
Eric Hines wrote:
My DNS server sits on lserver1. I'm trying to ping lserver1 from
Do:
ping lserver1.test.biz
Response is?
With /etc/resolv.conf edited per John's example (subject to the changes
I discussed in a posting just made), there's a long pause and then
unknown host. With /etc/resolv.conf in its original form
(dhclient-script generated), there's a short pause and then unknown host.
lserver1. With nsswitch set only to files or only to wins (/e.g./,
hosts: files), this is successful. With nsswitch set only to dns, I
cannot get name resolution, although I can successfully ping by IP
address. I can ping lserver1 by name or by IP successfully from
mustelidae.
Where is lserver1 pointing in terms of DNS? How do I tell? At this
John also mentions setting in resolv.conf
nameserver 127.0.0.1(this is your loopback address)
nameserver 192.168.0.2 (this should be the ip of your router/firewall)
(you can have a maximum of 3 nameserver listed
I made that correction (it wasn't clear from John's example what that IP
address was for), but I still got unknown host) when I tried to ping
lserver1 and lserver1.test.biz.
. Is /etc/resolv.conf part of this
answer?
YES!
My resolv.conf, nsswitch.conf, and smb.conf are attached. The nsswitch
is set to dns only, now for test. Normally it's set to files dns wins.
My named.conf and dhcpd.conf are built from John's example, as
mentioned above. /Etc/hosts has the IP address/name pairs he calls
for. I think that means I'm running a local name server.
No. The hosts file bypasses dns eg. Nsswitch is usually set to files dns
wins
Check files 1st then dns, then wins to find names on your lan
Files is your hosts files the rest should be self explanitory
That much I'd figured out: I meant the aggregate4 of all of those, since
that was the goal of John's set up, which included all of those.
As you can see, I have very little understanding of what's going on
here; I've rather slavishly followed John's example, and I'm clearly
making mistakes I'm not recognizing.
You need to learn about DNS elsewhere.
Go here, and read this:
http://www.novell.com/documentation/suse91/suselinux-adminguide/html/ch14.ht
ml
Particularly this:
http://www.novell.com/documentation/suse91/suselinux-adminguide/html/ch14s06
.html
Then apply it to your situation.
Going there tonight.
Thanks
Eric Hines
The over view is this:
The way out of this mess from my point of veiw is to switch off dhcp from
the router/firewall.
How? I can't switch off the router/firewall.
Regards Geoff Scott
--
He can compress the most words into the smallest ideas of any man
I ever met.
- Abraham Lincoln
# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2005/07/05 15:28:39
# Global parameters
[global]
workgroup = DOM_TEST
interfaces = eth0, lo
bind interfaces only = Yes
passdb backend = tdbsam
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*Password* %n\n *Re-enter*new*password* %n\n
*Password*changed*
username map = /etc/samba/smbusers
unix password sync = Yes
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 50
smb ports = 139 445
name resolve order = wins bcast hosts
time server = Yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = CUPS
show add printer wizard = No
add user script = /usr/sbin/useradd -m '%u'
delete user script = /usr/sbin/userdel -r '%u'
add group script = /usr/sbin/groupadd '%g'
delete group script = /usr/sbin/groupdel '%g'
add user to group script = /usr/sbin/usermod -G '%g' '%u'
add machine script = /usr/sbin/useradd -s /bin/false -d /tmp '%u'
shutdown script = /var/lib/samba/scripts/shutdown.sh
abort shutdown script = /sbin/shutdown -c
logon script = \scripts\login.bat
logon path = \\%L\profiles\%U
logon drive = X:
domain logons = Yes
preferred master = Yes
wins support = Yes
ldap ssl = no
utmp = Yes
idmap uid = 1-2
idmap gid = 1-2
map acl inherit = Yes
veto files = /*.eml/*.nws/*.{*}/
veto oplock files = /*.doc/*.xls/*.mdb/
## Shares omitted to same space.; generated by /sbin/dhclient-script
; search hsd1.tx.comcast.net.
; nameserver 63.240.76.198
; nameserver 204.127.199.8
search lserver1.test.biz
nameserver 127.0.0.1
nameserver 192.168.1.1#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note
Re: [Samba] remove wins entries - samba 3
Geoff Scott wrote: Eric Hines wrote: Geoff Scott wrote: Eric Hines wrote: The over view is this: The way out of this mess from my point of veiw is to switch off dhcp from the router/firewall. ow? I can't switch off the router/firewall. No of course not. You mean to say that you can't get access to a web interface or commandline on the router to configure it? You might need to look at getting better hardware / strongarming your ISP for info on the router if it is ISP provided. It's our own Cisco/Linksys router/firewall. I'll have to figure out how to do this on a per-machine basis. There are others also that are protected by the router/firewall. Can you show us your zone files for test.biz 192.168.1.0? Attached. What do your logs say for bind starting up? Can you restart bind and watch your logs? Do you have any errors for it? If you mean winbind, a tail -f on log.winbindd just showed it starting up again n response to a service winbind restart. log.smbd just showed smbd restarting after a restart. log.nmbd showed nmbd getting the shutdown signal, then starting back up and becoming the domain master browser. Regards Geoff Scott Thanks Eric Hines -- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln $ORIGIN . $TTL 38400 ; 10 hours 40 minutes 1.168.192.in-addr.arpa IN SOA lserver1.test.biz. root.test.biz. ( 2003021825 ; serial 10800 ; refresh (3 hours) 3600 ; retry (1 hour) 604800 ; expire (1 week) 38400 ; minimum (10 hours 40 minutes) ) NS lserver1.test.biz. $ORIGIN 1.168.192.in-addr.arpa. 103 PTR lserver1.test.biz. ; 1 PTR lserver1.test.biz. 10 PTR pserver1.test.biz. ; 20PTR qmsa.abmas.biz. ; 30PTR hplj6a.abmas.biz. $ORIGIN . $TTL 38400 ; 10 hours 40 minutes test.biz IN SOA lserver1.test.biz. root.test.biz. ( 2003021833 ; serial 10800 ; refresh (3 hours) 3600 ; retry (1 hour) 604800 ; expire (1 week) 38400 ; minimum (10 hours 40 minutes) ) NS dns.test.biz. MX 10 mail.test.biz. $ORIGIN test.biz. lserver1A 192.168.1.103 ; sleeth2 A 192.168.2.1 pserver1A 192.168.1.10 ; hplj6a A 192.168.1.30 ; qmsfA 192.168.2.20 ; hplj6f A 192.168.2.30 dns CNAME lserver1 lserver1CNAME lserver1 mailCNAME lserver1 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] [Fwd: Samba-3 By Ex Chapt 3]
One more thing I forgot to mention. The chapter calls for editing /etc/resolv.conf, but in my case it won't stay edited--it keeps getting set back to an original form (for searching my ISP) on every reboot. Thanks again. Eric Hines Original Message Subject:Samba-3 By Ex Chapt 3 Date: Tue, 05 Jul 2005 17:47:09 -0500 From: Eric Hines [EMAIL PROTECTED] To: Samba samba@lists.samba.org I guess I'm ate up with dumb because I'm having a great deal of difficulty with this chapter. I'm running Samba v 3.0.14a on an FC3 machine. I've got two basic problems: one centers on my DNS set up and the other is an authenticated logon problem. With /etc/nsswitch.conf set to hosts: dns, I cannot ping my samba server--Host not found. Nor does host lserver1.test.biz (which appears in my /etc/hosts file) resolve the name (incidentally, host -f ... just tells me the f is an illegal option). WINS seems to resolve OK (at least the test for that in the chapter passes). I've checked my files several times, and I can find no error in them. The other problem is running smbclient //lserver1/accounts -U ehines. I'm invited to give the password, so that part is OK, but when I do, I just get an NT_STATUS_LOGON_FAILURE message. ehines is the owner of accounts and a member of the group that owns accounts. I think this goes back to my logon file in /scripts (per the smb.conf set up), but I'm clueless as to what should be in that file. That file currently has the following contents: net time \\lserver1 /set /yes net use h: /home net use p: \\lserver1\accounts Any help on these two would be greatly appreciated. Eric Hines -- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln -- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Can't Start SMB Services and Question
Benjamin,
I made the suggested correction (and another one that I should already
have done: create the /scripts directory and put the login.bat into
it--doh), and there's improvement. Now I get an
NT_STATUS_BAD_NETWORK_NAME error. That's a separate problem that I need
to work, and I think I know what's causing it.
However, I still need to run under a different smb.conf (and hence the
network name problem) because with the smb config file I attached
earlier, I still can't run smb services.
Attached is the testparm output, still reflecting no (syntactical) errors.
Thanks for your help.
Eric Hines
Benjamin Biel wrote:
Hi Mr. E Hines,
check following typs in your conf.
- logon script = scripts\login.bat
+ logon script = \scripts\login.bat
Besfor make testparm and send me your srenn, then i can help you better.
--
He can compress the most words into the smallest ideas of any man
I ever met.
- Abraham Lincoln
Load smb config files from smb.conf.example3_4
Processing section [printers]
Processing section [IPC$]
Processing section [homes]
Processing section [netlogon]
Processing section [profiles]
Processing section [accounts]
Processing section [backups]
Processing section [apps]
Loaded services file OK.
# Global parameters
[global]
workgroup = DOM_TEST
interfaces = eth1, lo
bind interfaces only = Yes
passdb backend = tdbsam
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*Password* %n\n *Re-enter*new*password* %n\n
*Password*changed*
username map = /etc/samba/smbusers
unix password sync = Yes
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 50
smb ports = 139 445
name resolve order = wins bcast hosts
time server = Yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = CUPS
show add printer wizard = No
add user script = /usr/sbin/useradd -m '%u'
delete user script = /usr/sbin/userdel -r '%u'
add group script = /usr/sbin/groupadd '%g'
delete group script = /usr/sbin/groupdel '%g'
add user to group script = /usr/sbin/usermod -G '%g' '%u'
add machine script = /usr/sbin/useradd -s /bin/false -d /tmp '%u'
shutdown script = /var/lib/samba/scripts/shutdown.sh
abort shutdown script = /sbin/shutdown -c
logon script = \scripts\login.bat
logon path = \\%L\profiles\%U
logon drive = X:
domain logons = Yes
preferred master = Yes
wins support = Yes
ldap ssl = no
utmp = Yes
idmap uid = 1-2
idmap gid = 1-2
map acl inherit = Yes
veto files = /*.eml/*.nws/*.{*}/
veto oplock files = /*.doc/*.xls/*.mdb/
[printers]
comment = SMB Print Spool
path = /var/spool/samba
guest ok = Yes
printable = Yes
use client driver = Yes
default devmode = Yes
browseable = No
[IPC$]
path = /tmp
hosts allow = 192.168.1.0/24, 127.0.0.1
hosts deny = 0.0.0.0/0
[homes]
comment = Home Directories
valid users = %S
read only = No
map acl inherit = No
veto files =
veto oplock files =
browseable = No
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
guest ok = Yes
locking = No
[profiles]
comment = Profile Share
path = /var/lib/samba/profiles
read only = No
profile acls = Yes
[accounts]
comment = Quicken Files
path = /data/accounts
read only = No
[backups]
comment = Miscellaneous Backups
path = /data/backups
read only = No
[apps]
comment = Application Files
path = /apps
admin users = mfwic
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] FOLLOWUP: Samba, OS X Tiger 10.4 plain text password, username null-padded?
So, Apple is following the Microsoft school of Tech (non)Support Eric Hines Elizabeth Schwartz wrote: So, an Apple engineer came and hung out for about three hours last week and agreed that Tiger was doing something pretty funky with the plain text passwords. Today's word is: there is a fix in 10.4.2 that will go in combination with the /etc/nsmb.conf and hopefully solve your problem.That is as much detail as I have right now. Do you have access to the seed build of 10.4.2 via ADC ? We aren't going to play with beta releases of OS X ourselves right now but I'd be real interested if anyone here does. cheers Betsy [who received a bunch of off-list Me Too messages...] -- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Slow eth0 Config
Folks, This is a strange problem, and I'm not sure this is the right place for it, so feel free point me to a better location. I'm running FC3 and Samba 3.0.14a. The problem is this: when I boot up my Linux box, and it gets to the point of turning on my NIC (eth0), where the PC used to turn it right on and continue, now there's an inordinately long delay in getting eth0 to come up--so long that the PC drops back to its earlier, coarse-text bootup screen where it's gutsing up the local file systems for several 10s of seconds. When the PC returns to its later screen that shows the various daemons and other functionalities being turned on, eth0 is up and running, and 5-6 other functionalities have already been turned on, as well, and the bootup completes in otherwise normal fashion. I'm working through JHT's online BYEXAMPLE book's Chapt 3 exercise, and I've reached the point where I've written the DNS config files and turned on named. The problem began at this point in time. Also, ethereal indicates that the Linux PC is sending out exactly 0 broadcast packets asking for dynamic address confirmation/reassignment, even though the PC has been set to get its address automatically via DHCP. Further, the machine's /etc/hosts file has the following line in it (which it has always had, so this ought not be a problem, unless there's something fundamentally different between Chapt 3 and the earlier chapters): 192.168.1.103 lserver1. I'm running this with Chapt 2's smb.conf file as my version of Chapt 3's smb.conf file has its own problems which I haven't had a chance to trouble shoot--it causes the PC's bootup to hang--completely, this time--on trying to bring up snmb. I don't think this earlier .conf file is related, though, or is it? At the same time, I've switched from a Linksys 4-port router/firewall for my LAN to a Linksys 8-port router/firewall. I don't think this is relevant, but I'm too ignorant at this point blithely to discount it. I've turned off named, so the DNS stuff ought no longer be running, but this has had no effect. I've also turned off the sshd with no effect. Any thoughts on what's going on? Thanks Eric Hines -- He can compress the most words into the smallest ideas of any man I ever met. - Abraham Lincoln -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Obtaining log level 10 for just specified user(s) (MS Word Excel File Locking issue - still)
I can't address the Word problem, but have you looked at Excel itself as the culprit for the Excel problem? For instance, is the user able to get anything done on his/her Excel spreadsheet before this problem occurs? There is a .xlb file (I don't remember its exact name; I'll have to look it up when I go in to work tomorrow) that occasionally gets corrupted. Deleting this file makes Excel work OK, again, and the file is regenerated the next time the user opens Excel (and is changed/updated/whatever MS feels like doing with this sort of file) every time the user opens Excel. Eric Hines At 05/30/05 08:40, you wrote: Is it possible to make samba produce a log at level 10 for only a specified user(s), I am trying (still) to figure out why Samba processes climb to 100% CPU and the user loses connection with MS Word Excel files being locked. Have been dealing with this issue for quite some time now, but had to put it on the back burner for a while because we had little time to deal with it. Apprently only an issue with a few users still, yet unable to isolate anything different from them to the user next to them, aside from filenames, which are apparently random or not the cause anyhow. Gave up on trying to fix it a while back, but having more and more problems daily, with 2-3 processes every hour or so climbing to 100% cpu utilization and the user being locked out; a simple kill -9 to the process id in question, and a new one spawns and the end users good to go... Annoying, but at least a work-around we've been able to get by with. I'd like to get some debugging logs, but as these servers are being used in production, I need to force log level 10 only for specified users (aka ones having the problem). Is it possible to do this? Log files hit like 5 megs in a matter of a minute or two; can't accept that for every user on the system - and it's a huge hit on I/O we don't need to take either :( Any suggestions? -- Nathan Vidican [EMAIL PROTECTED] Windsor Match Plate Tool Ltd. http://www.wmptl.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Government programs provide enough to keep you alive, but they don't offer any hope of living your dreams. --Grim -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RESOLVED--Re: [Samba] Print Share Problem
The printer stanza has to be _called_ [printers]? [pserver1]--the name [pserver1]--the name of the specific share--isn't sufficient? If the only stanza is [printers], then how does the specific printer get found? I changed [pserver1] to [printers], and now the correct specific printer shows up, but still--my question stands. Thanks Eric Hines At 05/20/05 14:11, you wrote: On Friday 20 May 2005 13:03, E Hines wrote: I'm running FC3 and Samba 3.0.14a. I'm trying to work through Exercise 2.3 of the on-line Samba-3 by Example, and mostly things ore OK, but I can't get my print share to show up when I run smbclient -L localhost -U %. Everything else shows up correctly (although I do get two workgroups to appear, as there is another workgroup to which I used to belong before I separated from it (I thought) to set up a test LAN for these exercises), and I both can ping my printer by name and get back its correct MAC address from a subsequent arp -a. Where is your [printers] meta-service stanza? That is in the example smb.conf file and is necessary. - John T. snip -- John H Terpstra Samba-Team Member Phone: +1 (650) 580-8668 Author: The Official Samba-3 HOWTO Reference Guide, ISBN: 0131453556 Samba-3 by Example, ISBN: 0131472216 Hardening Linux, ISBN: 0072254971 Other books in production. Government programs provide enough to keep you alive, but they don't offer any hope of living your dreams. --Grim -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba-3 by Example Exercise 2.3
The FAQ (question/answer 2) says that the DHCP server config /etc/dhcpd.conf) automatically provides each client with the IP address of the WINS server. I've been over the provided dhcpd.conf, and I cannot find which line(s) are referring to the WINS server. Also, as written, when I tried to start my dhcpd, I got an error saying I had to specify a ddns-update-style. I wound up adding at the top the following: ddns-update-style interim; ignore client-updates; This has worked well, so far. Eric Hines Government programs provide enough to keep you alive, but they don't offer any hope of living your dreams. --Grim -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: nazi spam in German over list address
Locking out the Windows folks is counterproductive--those are exactly the ones we're trying to attract away from MS, for that's the only way we'll beat MS--by converting its customers. And now I'm done with this thread; I'm more interested in learning Samba. Eric Hines At 05/16/05 21:12, you wrote: snip I'd go further and cut down on membership to people emailing from non-Windows systems (including Webmail systems, until someone invents a worm that spreads through those...) Err, rather, limit membership to only people who are emailing from non-Windows systems. J. L. Blank, Systems Administrator, twu.net -- J. L. Blank, Systems Administrator, twu.net -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Dawn is nature's way of telling you to go to bed. And to just stay there until the evil yellow disk is gone again. --Anonymous -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: roaming profiles problem for new users
John, This isn't entirely fair. There are three kinds of newbies, and I'll say for the purposes of this thread that newbies also may be new to Linux/UNIX, not just to Samba: the first kind is lazy and goes running for help at the drop of a bug and doesn't bother to read the docs first. This kind deserves your rant. The second kind doesn't know documentation exists--they don't deserve your rant; they need only a pointer to the docs--as you provided below, in addition. The third kind has read the docs and still has a problem, else they wouldn't be on the mailing list looking for help. We don't deserve your rant, either. And we've read the docs despite what seem to be a high error rate in them that confuses the diagnostic outcomes. (For instance, in Chapt 1 of the HOWTO, on connecting to a Remote SMB Client, we're told to run net use d: \\servername\service. When I do that, I simply get the error back that the local device is already in use. Of course--d: is a logical partition on my PC. I have to figure out that you meant d: to be generic, in the same spirit as servername. Maybe I should have recognized that a priori, but I didn't. Newbies make mistakes like that. In the Samba Checklist, Step 4, we're told to run nmblookup - B BIGSERVER_SAMBA_. This seems to have two typos in it, yet as a newbie, I'm unsure. Using - B (with the space) just has nmblookup look for the IP address of the machine B, also, which, of course it cannot find. Or were we supposed to use -B -- without the space? But then to what broadcast address, as that's what that switch calls for? Or is nmblookup - servername what was truly meant? And the _SAMBA_ suffix appended to our server's name means that that machine cannot be found by nmblookup, either--unless someone actually has appended that suffix to their machine name. the - B, -B, - confusion is repeated throughout the checklist. Further, in step 6, we're told to try nmblookup - d 2 '*' . This leads to further error, as nmblookup cannot find either machine d or 2. It turns out we're supposed to use -d (no space).) For all that, we in this third kind of newbie, get lumped in with the first kind, and our problems get utterly ignored. It's true enough that you're all volunteers, helping out in addition to your day jobs, and really your efforts are appreciated a great deal. But most of us newbies are trying to learn this stuff, also in addition to our own day jobs. Or are we on the wrong mailing lists? If there are other Samba mailing lists intended for newbies, please point us there. /rant Eric Hines At 05/06/05 10:08, you wrote: Jon, Please, please use the resources we provide before posting questions like this. Did you read the book Samba-3 by Example before you asked your questions here? I think you will find a fully working solution in chapter 3. The latest version (still being edited) can be downloaded from: http://www.samba.org/samba/docs/Samba-Guide.pdf Note: The book uses SUSE Linux as its reference base so you will beed to adjust pathes and Samba binary names according to the way Mandrake have named the binary files . - John T. snip -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Out of the argument with ourselves comes poetry, out of the argument with others comes politics. --Yeats -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Option 'valid users' disappear in SWAT
It's not a bug, it's a feature. SWAT assumes that once you've made your list of valid users (or invalid users, or etc) that you'll not want to change it, so Swat stops presenting those lists under the BASIC set of options. Select ADVANCED (the radio buttons are near (just above or below, I don't remember which) the choice of shares on the SHARES main menu button (and similarly placed on each of the other main menu buttons), and the much longer list of things you can manipulate that appears will include, e.g., your valid users option. Eric Hines At 05/03/05 03:28, you wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, maybe it's a bug, maybe not. I added some groups in the field valid users in SWAT and committed my changes. After that, this option disappears. When I manually delete all groups in the smb.conf, in SWAT this option is available again. I'm running Samba 3.0.14a (SerNet). Greetings, Holger -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCdzYxO0QDuZMdP0sRAmSkAKCOBILU9iyH2CXejvzjFaISG4cTsgCdE6+K MxfWoHVW6dhh8qO3cewlVr8= =y0+2 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Out of the argument with ourselves comes poetry, out of the argument with others comes politics. --Yeats -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can't Install Samba 3.0.14a
All, Thanks to all who offered your solutions. Fortunately, they converged on one (rpm -Uvh ...), and it ran just fine. I followed Paul's advice and put the four rpms on one line for this. A couple of fillips to the end game: rpm has a fail safe: I had forgotten to backup my swat control file; rpm, rather than blithely overwriting it, simply created swat.rpmnew instead. I had only to copy that into the original swat control file. Then, however, to get SWAT to run (I was getting a connection refused to localhost:901 error), I had to change disable = yes to disable = no. Eric Hines At 04/19/05 08:41, you wrote: The Samba packages on Fedora 3 should be installed like this: rpm -Uhv --nodeps /usr/src/redhat/RPMS/i386/samba-common-3.0.14a-1.i386.rpm rpm -Uhv /usr/src/redhat/RPMS/i386/samba-3.0.14a-1.i386.rpm rpm -Uhv /usr/src/redhat/RPMS/i386/samba-client-3.0.14a-1.i386.rpm nodeps is bad. Put all the packages on one rpm line and you'll be fine. That allows rpm to figure out for itself that you've got your ducks in a row and trust that if it does just what you said everything will be all right. snipthere is one place where a --nodeps or even a --force is useful. When you do a yum upgrade you need to push a couple packages (like rpm itself) in really hard to get it to kick off right, but that's a pretty specific situation where you're upgrading pretty much everything on the system anyway. On a regular package and a functioning system, --nodeps is a no-no, especially if you don't know why you want to use it in the first place. Don't forget to backup /var/lib/samba/* and /etc/samba/* before the update and after the shutdown of all samba deamons. Alex. -- Paul GiengerOffice: 701-281-1884 Applied Engineering Inc. Systems Architect Fax:701-281-1322 URL: www.ae-solutions.com mailto: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba If you are unwilling to defend your right to your own life, then you are like a mouse trying to argue with owls. You think their ways are wrong. They think you are dinner. --Anonymous -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Install/SWAT Access
I'm running FC3, kernel 2.6.9-1.667, with the KDE desktop. This came with Samba v 3.0.11-fc3 bundled. I've since installed v 3.0.14a. I'm also extremely new to Linux, so please bear with me. My questions are very basic. The FC3-bundled samba is in /etc/samba, and the upgrade went into /usr/local/samba. To get SWAT to work, I had to copy the smb.conf that's in /etc/samba into /usr/local/samba/lib. However, this latter version is not read by the networking functionality, or by CUPS--only when I used KDE's samba editor to edit /etc/samba/smb.conf was I able to see my Linux box from my Windows machines (running Win2k) or get printing to work. I have 2 samba versions installed, but my system is still using only the older version. So: How do I point SWAT at the etc/samba version? How do I get my system to use the newer version in its different location? More optimally, how do I control the installation destination directory, so that I can install future versions (including reinstalling 3.0.14a) into /etc/samba? Thanks for your help. Eric Hines If you are unwilling to defend your right to your own life, then you are like a mouse trying to argue with owls. You think their ways are wrong. They think you are dinner. --Anonymous -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Install/SWAT Access
Many thanks. As it happens, I'd just bought the 2004 edition of your book yesterday. I'll be getting the later edition when it comes out, too Eric Hines At 04/17/05 11:17, you wrote: snip So: How do I point SWAT at the etc/samba version? How do I get my system to use the newer version in its different location? More optimally, how do I control the installation destination directory, so that I can install future versions (including reinstalling 3.0.14a) into /etc/samba? Thanks for your help. I believe you will find what you need in Chapter 8 of the currently-being-revised edition of my book Samba-3 by Example (a.k.a. Samba-Guide) from: http://www.samba.org/samba/docs/Samba-Guide.pdf Cheers, John T. -- John H Terpstra Samba-Team Member Phone: +1 (650) 580-8668 Author: The Official Samba-3 HOWTO Reference Guide, ISBN: 0131453556 Samba-3 by Example, ISBN: 0131472216 Hardening Linux, ISBN: 0072254971 Other books in production. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Install/SWAT Access
Paul, Thanks for your response. I got the version from samba.org as a tar.gz file, which turned out to be source code. I did install from source. Where can I get an rpm package for this version? Alternatively (for my longer term benefit), how do I a) get FC3 to look at/use the upgrade version in the samba team's directory structure, or b) install the upgrade version into FC3's directory structure? Thanks Eric Hines At 04/17/05 15:19, you wrote: I'm running FC3, kernel 2.6.9-1.667, with the KDE desktop. This came with Samba v 3.0.11-fc3 bundled. I've since installed v 3.0.14a. I'm also extremely new to Linux, so please bear with me. Where did you get your upgrade version?? It sounds like you installed from source, which in an RPM distro is not the best way to do things. I won't get into a long discussion on it, but if you're on a rpm box, use an rpm till you know what you're doing. If you installed from source, (if you remember running make install) there should be a make option to back it out, like make uninstall. You can build a rpm, which will put the files in all the right places in your machine with the script at sourcedir/packaging/Fedora/makerpms.sh I believe. snip -- Paul GiengerOffice: 701-281-1884 Applied Engineering Inc. Systems Architect Fax:701-281-1322 URL: www.ae-solutions.com mailto: [EMAIL PROTECTED] If you are unwilling to defend your right to your own life, then you are like a mouse trying to argue with owls. You think their ways are wrong. They think you are dinner. --Anonymous -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Fwd: Re: [Samba] Samba Install/SWAT Access
Paul, Deryck, et al., Thanks for all of your help (OP isn't savvy--what was your first clue? g). After sufficient prodding, I went and looked and found the following URL, at our very own samba.org, for rpms for Samba v 3.0.14a: http://us1.samba.org/samba/ftp/Binary_Packages/Fedora/RPMS/i386/core/3/http://us1.samba.org/samba/ftp/Binary_Packages/Fedora/RPMS/i386/core/3/ Looks like I'll be uninstalling the source build and installing these rpms I'm also going to go to school on Paul's Option 2 below. Eric Hines From: Paul Gienger [EMAIL PROTECTED] User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) Subject: Re: [Samba] Samba Install/SWAT Access Deryck Hodge wrote: Eric Hines wrote: Paul, Thanks for your response. I got the version from samba.org as a tar.gz file, which turned out to be source code. I did install from source. Where can I get an rpm package for this version? Alternatively (for my longer term benefit), how do I a) get FC3 to look at/use the upgrade version in the samba team's directory structure, or b) install the upgrade version into FC3's directory structure? Thanks Eric Hines Eric, You can specify a different directory structure when using configure. Run ./configure --help to see the options. Running ./configure --help | grep dir produced the following: While this is all fine and good, it still doesn't fix the problem I was addressing, that being source code installs on a RPM based system can cause havoc if you aren't adept at keeping things straight. Not to be demeaning to Eric, but the OP here isn't savvy (yet ;) ) on where things should be to fix the system when things break, hence the post here. Eric, to answer your questsons a) simple really, build an RPM that has been built to RH/Fedora's organization. b) see answer a. To build a rpm to these specs, you have 3 real choices. One of them I outlined in my response, which is to run the makerpms.sh script, which I think you need to add u+x permissions to before it will run. Option 2 is to grab a src.rpm and build that way. This is a long description, but it's pretty easy. If you download http://us4.samba.org/samba/ftp/Binary_Packages/RedHat/SRPMS/samba-3.0.14a-1.src.rpm and install that, you will get the sources installed in a way that you can build from them in RHs directory structure. To build the rpm files, you go to /usr/src/redhat/SPECS and execute 'rpmbuild -bb samba.spec' which will then go nuts building, provided you have any dependancies installed, it will complain if you don't. If it does complain, install any packages it is asking for. Once it exits (hopefully with a 0 result) you will have packages built in /usr/src/redhat/RPMS/i386 (assuming that you're running an x86-32 arch). Install all the samba packages without the -debug in the name. I'm sure there's an option to disable debug builds, but I don't know it off hand. - note that you have to have a few deve packages installed to just get started here, like rpmbuild (I think, it used to be named that) and maybe some other stuff. Try to run rpmbuild bare and see if it runs, if not start to install that and put in whatever it asks for. If you aren't sure how to do that, go to your install disk's rpm directory and run rpm -ivh package_file_name.rpm.I realize now that you may not be that fluent at installing rpm files, that command right there is one you could end up using a lot in this step. You can install several packages at once by just adding more filenames at the end. Option 3 is to find a binary packaged RPM file someplace. You're on your own there, I usually do step 2 if things aren't available in my yum paths. Hope that helps. -- Paul GiengerOffice: 701-281-1884 Applied Engineering Inc. Systems Architect Fax:701-281-1322 URL: www.ae-solutions.com mailto: [EMAIL PROTECTED] If you are unwilling to defend your right to your own life, then you are like a mouse trying to argue with owls. You think their ways are wrong. They think you are dinner. --Anonymous -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
