similar to: Domain group membership.

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 >

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

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.

>Date: Sat, 26 Nov 2005 21:39:28 -0600 >To: Craig White <craigwhite@azapple.com> >From: Eric Hines <eehines@comcast.net> >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

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

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:

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

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),

Hi, ntsysv doesn't list the samba daemons (smbd, nmbd), and while I could use chkconfig, it appears, to add the daemons, I'd rather do this via the rcx.d links so I can understand what's going on. Eric Hines -------- Forwarded Message -------- From: Sp0oKeR Labs <spooker@gmail.com> <snip>Date: Sun, 27 Feb 2005 21:35:32 -0300 Did u try ntsysv ou chkconfig? Are you using

The only way I could get rid of the err for gsm on launch was to copy libgsm to my DDO folder, even those I use DYLD_FALLBACK_LIBRARY_PATH, and libgsm is in all of those locations. Here's my launching script&#058; Code: on run --edit this to be the correct location and file to run (typically only edit after the "drive_c") set toRun to

UBUNTU 10.10 AMD64 Latest updates with recompile wine 3.1.7 after an ia32.lib upgrade. Returning to looking at GMAX. As things stand now, when you try to open the materials navigator the program posts an error, allows you to do a save, and quits.

Actually, my problem turns out to be even more basic and foolish than that. I assumed that since the relevant Kill files were present in the ls listing, then the Start files would be, too. Nope. I had to make those soft links; when I did, everything worked properly. Eric Hines -------- Forwarded Message -------- From: Paul Gienger <pgienger@ae-solutions.com> <snip> Date: Sun, 27

And my last post on the matter. This is why I won't do business with USR again anytime soon. They couldn't even be bothered to tell me this on my first query to them. Eric Hines >X-Originating-IP: [63.169.70.144] >Date: Tue, 20 Dec 2005 18:44:48 -0500 >From: usr_amr_eng@aqinc.com >Subject: In response to your USRobotics technical support questions, >your case

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

Hi all: =20 I joined my samba server to a win2000 domain controller. I found = something interesting, if I shutdown the domain controller, I can=A1=A6t = connect to my samba server through windows CIFS (\\IP <file:///\\IP> ). = However, using smbclient can still browsing shares without a problem. Is = it a normal situation?? =20 Thanks in advance, Latrell.

Hi all: =20 I=A1=A6m trying to join a win2000 ad domain but failed. I can see my = samba server in computer list of domain controller, but the icon of the = samba server is disabled. I also got error message from my samba server: =20 Failed to set password for machine account (NT_STATUS_WRONG_PASSWORD) = Failed to join domain: Wrong Password =20 The password should be correct because I can

Hi all: =20 After I upgraded to samba 3.0.23d, I can=A1=A6t use net ads info to = retrieve DC information. =20 In my previous version (3.0.21c), I can use net ads info and get the = information: LDAP server: 172.23.26.204 LDAP server name: nas-2003 Realm: NAS.LOCAL Bind Path: dc=3DNAS,dc=3DLOCAL LDAP port: 389 Server time: Mon, 22 Jan 2007 09:51:02 GMT KDC server: 172.23.26.204 Server

Hi, I learning samba on SUSE 9.3 linux box. I followed the Samba "Small Office Networking" example to configure the server, but I have problem to access the share "accounts" / finsvcs until I changed the valid users from %G to @acctsdep. Here are the output from the console when I accessing the share "accounts" server01:~ # smbclient //server01/accounts -U

Sorry for the direct post.... Eric Hines -------- Original Message -------- Subject: Re: [Samba] can't connect to swat Date: Sun, 16 Apr 2006 08:51:45 -0500 From: EHines <eehines@comcast.net> To: Larry Weldon <lweldon@weldoncomputers.com> References: <02a201c66148$c8925290$0c46a8c0@jshinotebook> <1145194206.20034.72.camel@tiger.home.welcoin.com> Larry Weldon

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