Displaying 12 results from an estimated 12 matches similar to: "Problem with roaming profiles and Samba 3.0"
2020 Oct 17
1
Re: [xml] Why does libxml2 limit port numbers to 999, 999, 999?
On Sat, Oct 17, 2020 at 06:32:18PM +0200, Nick Wellnhofer wrote:
> On Oct 17, 2020, at 12:24 , Richard W.M. Jones via xml <xml@gnome.org> wrote:
> > It seems like libxml2 chose to do this for convenience rather than
> > correctness.
>
> Yes, this is an arbitrary limit introduced to avoid integer overflow.
>
> > I think it should accept port numbers at least
2003 Feb 21
1
calculating mean direction (CircStats)
Hi,
I've currently to work with some circular data. Unfortunately I'm not very
familiar with circular statistics and would really appreciate if I could get
some help concerning the CircStats package this way.
My data lies in the range 0 to 2*pi, and is transformed to radians (as
expected by the CircStats methods). Calculating the mean direction
(circ.mean) results for some datasets in a
2020 Oct 17
3
Why does libxml2 limit port numbers to 999,999,999?
The AF_VSOCK protocol added in Linux 5.6 uses a 32 bit port number.
For NBD we map this to simple URIs[1] like nbd+vsock://CID:PORT (where
CID is a number that acts a bit like a hostname and PORT is a 32 bit
port number). eg: nbd+vsock://1:1000000000/ would be port 10^9 on the
loopback address VMADDR_CID_LOCAL (== 1).
The problem is that libxml2 arbitrarily limits port numbers to
999,999,999.
2005 Jul 11
4
Samba PDC problem
Hi all,
I'm trying to configure samba as PDC, I have a problem when windows
client log in this is the error:
Windows cannot load the profile and is logging you on with a temporary
profile. Changes you make to this profile will be lost when you log off
I have samba-3.0.11 and smbldap-tools-0.8.8. I tryed also samba-3.0.14
and smbldap-tools-0-9.1, I have the same problem on Gentoo and on
2004 May 04
3
Samba without netbios/WINS
I am running samba (2.2.7a) on a solaris box on a network seperate from
our windows clients. (different subnet) We have a mix of Win2k and
winXP clients that are connecting to it.
I recently upgraded from NT 4.0 domains to active directory on Win2K
servers, and I would like to completely do away with netbios and WINS.
The problem is getting clients to connect to the samba server. I have
2004 Jan 21
0
KB824141 on Win2K and Samba PDC with a mandatory profile
This one gave me a headache yesterday:
Last updated version of KB824141 hotfix on a Windows 2000 workstation in
a domain with Samba PDC has the following consequences:
1. When a user with a mandatory profile logs on, it doesn't load the
profile correctly. The cached profile looks like a default profile -
empty directories except for the NTUSER.MAN. No Desktop, no Application
data ...
2005 Apr 05
2
WIN2K with SP4 unab;e to save profiles on a Samba PDC
Hi all,
I have been noticing for a certain time that the Win 2K with Service
Pack 4 wasnt able to save its profile to a Samba PDC. Is this a known
fact or I have a problem ?
I am using 3.0.11 on Fedora Core 3.
regards
--
You cannot prevent the birds of sorrow
from flying over your head,
but you can prevent them from
building nests in your hair.
2004 May 03
2
Windows XP client - intermittent 'network name cannot be found' loading profile
I have seen a number of postings which seem similar to the problem I am
having, but am yet to find a fix for my situation. Problem is as
follows:
- Samba 3.0.2 rpm installed on Red Hat Enterprise ES 3.0, configured as
PDC with ldapsam backend
- Windows XP Professional client joined to the Samba domain.
The XP client successfully joins the domain and can browse and access
shares (including the
2014 Oct 30
4
roaming profile does not work for "Domain Admins"
I am facing an issue which I cannot explain myself. The roaming profiles don't work for users that are members of the group "Domain Admins". The [profiles] share on the member server was configured exactly as explained on the wiki for roaming profiles. It works like a charm for all domain users, *BUT*: if a user is member of the group "Domain Admins" it *doesn't* :-(
2004 May 04
0
Windows XP client - intermittent 'network name cannotbefound' loading profile
John, I have tried the suggestions you provided. I have setup Dynamic
DNS as per the Samba 3 By Example book and this is all updating
correctly. I have run the validation steps indicated in the book and all
names are resolvable and reachable via hosts, DNS and WINS.
I am not sure why winbind would need to be turned off, but seeing as I
do not need that currently, I have tried disabling it; the
2004 May 26
2
Samba 3 and LDAP - Error loading profiles
Hi,
I'm setting up Samba with ldap backend and everythin appears to be working
correctly except for profiles.
Using:
samba-3.0.2
openldap-2.1.26
smbldap-tools-0.8.4
When a user 'testa' tries to logon from a Win2K system that has joined the
domain he gets the following error message:
"Windows did not load your roaming profile and is attempting to log you on
with your local
2020 Oct 17
0
Re: [xml] Why does libxml2 limit port numbers to 999, 999, 999?
On Oct 17, 2020, at 12:24 , Richard W.M. Jones via xml <xml@gnome.org> wrote:
> It seems like libxml2 chose to do this for convenience rather than
> correctness.
Yes, this is an arbitrary limit introduced to avoid integer overflow.
> I think it should accept port numbers at least up to
> signed int (the type used to store port numbers), and give an error if
> the port