Displaying 4 results from an estimated 4 matches for "3dzyxel".
2006 Dec 13
0
Null session problem when mounting share using domainuseraccount
...172.23.26.204 *
realm =3D NAS.LOCAL
idmap uid =3D 100000-500000
idmap gid =3D 100000-500000
winbind cache time =3D 15
template homedir =3D /tmp/users/home/%D/%U
template shell =3D /bin/bash
-----Original Message-----
From: samba-bounces+latrell.wang=3Dzyxel.com.tw@lists.samba.org =
[mailto:samba-bounces+latrell.wang=3Dzyxel.com.tw@lists.samba.org] On =
Behalf Of Latrell Wang =A4=FD=C4m=BA=F5
Sent: Wednesday, December 13, 2006 1:56 PM
To: samba@lists.samba.org
Subject: RE: [Samba] Null session problem when mounting share using =
domainuseraccount
In s...
2007 Feb 28
0
vista: error accessing profile, xp works (solved)
...thout a problem.
But when I use the Vista client, I get permission deny message.=20
I set host "msdfs =3D yes" in global session, and "msdfs root =3D yes" =
in SambaShare.
Are the two problems related?
Thanks,
Latrell.
-----Original Message-----
From: samba-bounces+latrell.wang=3Dzyxel.com.tw@lists.samba.org =
[mailto:samba-bounces+latrell.wang=3Dzyxel.com.tw@lists.samba.org] On =
Behalf Of Rainer Traut
Sent: Wednesday, February 28, 2007 6:39 PM
To: Volker.Lendecke@SerNet.DE
Cc: samba@lists.samba.org
Subject: Re: [Samba] vista: error accessing profile, xp works (solved)
Hi,
as...
2006 Dec 06
1
Anonymous access in windows 2003 sp1
Hi all:
=20
As far as I know, win2k3 sp1 disable anonymous access by default. It =
will remove user =A1=A7anonymous logon=A1=A8 from pre-windows 2000 =
compatible access group.
Under such circumstance, smbmount will not success because anonymous =
access will be blocked. One way to solve the problem is to re-add =
anonymous logon to pre-windows 2000 compatible access group. However, it =
seems
2006 Dec 07
7
Can connect to shares via IP but not hostname
Last night I upgraded my FC5 to samba-3.0.23c from 3.0.21b. As a result I can
no longer browse shares on the samba server via \\hostname\share\. I can,
however, access everything as usual via \\10.0.0.2\share\.
Nothing else in my config has changed. The hostname resolves from all machines
on the domain correctly so it's doesn't appear to be a name resolution issue. I
can see the