search for: strebelf

...Getting the groups via wbinfo gives me the expected listing though. I ran smbd at level 3 debug and here's the output when a user tries to connect to a share: [2008/05/29 09:29:43, 3] auth/auth.c:check_ntlm_password(221) check_ntlm_password: Checking password for unmapped user [WHO-HQ-1]\[strebelf]@[HQWD0060725] with the new password interface [2008/05/29 09:29:43, 3] auth/auth.c:check_ntlm_password(224) check_ntlm_password: mapped user is: [WHO-HQ-1]\[strebelf]@[HQWD0060725] [2008/05/29 09:29:43, 3] smbd/sec_ctx.c:push_sec_ctx(208) push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 1 [2008/05/29...

...fer my security setting to be domain, but of course as the machine was messing me about i'm not sure if that's necessary or not. still, seems to have done the trick, and seems cleaner than using nfs via samba to get to the home folders. :-) john --- On Wed 11/30, Strebel, Franz R. < strebelf@who.int > wrote: From: Strebel, Franz R. [mailto: strebelf@who.int] To: jhalfpenny@excite.com, samba@lists.samba.org Date: Wed, 30 Nov 2005 09:08:40 +0100 Subject: RE: [Samba] home folders query there should be no problem setting up home folders on a non-pdc<br>samba server. i have such...

Hai All, I am Unable to connect samba server using hostname the thing is.. its happen only from few windows machine in my network... but they can access the sambe share using IPAddress.. as like all other machine All the other Windows system in my network can access samba share using both... IP Address and Hostname.. This creating a big headache for me..... please suggest some solution to solve

>From what I know, if your PDC is on a different subnet, then the PCs won't be able to see it. This is a limitation of netbios and is addressed by having a WINS server. I haven't followed your problem entirely but I suppose that now that your server has 2 interfaces, it is able to listen to another subnet and can therefore address requests received there. As for the loopback

Would anyone have an idea why a group listing returned by wbinfo would be different from the one returned by the native groups command? Also, it turns out that the listing from wbinfo is incorrect. Has anyone else seen this before? I'm running 3.0.20b with my machine in an NT 4.0 domain. Accounts come from a trusted domain running AD mixed mode. Thanks, Franz