similar to: Cannot add Domain Groups to Local Groups (D Users OK)

Hey guys, I'm trying to migrate my NT4 Domain and am having some problems. Ignoring my other post related to this, I can't get any of my machines to be able to login. Alls I ever get is "Your computer account was not found or the password is incorrect" I even tried rejoining the domain which works. I leave the domain and then rejoin it, it takes a LONG time (might just be

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Still having that problem with samba seemingly corrupting files, it seems to be the same files that are corrupted again and again, yet they are corrupted differently and sometimes not. I ran my md5 summer against one file ch02.pdf, and it almost contineously corrupts, I checked in a hex editor and there are some differences. Yet the problem is that

I have the following Problem, include doesn't seem to work very well, its VERY intermitantly. The files are attached below along with an smbclient output. Basically I am setting up a PUBLIC share, that if I connect to will give me admin access. It contains service packs and fixes, so when I install someones system, they can just click and connect, without being prompted for a password.

I have the following Problem, include doesn't seem to work very well, its VERY intermitantly. The files are attached below along with an smbclient output. Basically I am setting up a PUBLIC share, that if I connect to will give me admin access. It contains service packs and fixes, so when I install someones system, they can just click and connect, without being prompted for a password.

On 09/19/2018 10:03 AM, Ben Bolker wrote: ... > Balancing backward compatibility and correctness is a tough problem > here. I think improvements in the RNG is a situation where backward compatibility is not really going to be lost, because people can specify the old generator, they just will not get it by default. My opinion is that the default needs to generally be the best option

On 2018-09-19 09:40 AM, David Hugh-Jones wrote: > On Wed, 19 Sep 2018 at 13:43, Duncan Murdoch <murdoch.duncan at gmail.com> > wrote: > >> >> I think the analyses are correct, but I doubt if a change to the default >> is likely to be accepted as it would make it more difficult to reproduce >> older results. > > > I'm a bit alarmed by the logic

Dear all, Lattice provides automatic coloring for subgroups on each panel by the simple use of a groups statement. For an application I want to change these colors to a predifined set. This works well using a panel function in stead of the default as long as there are only points in the graphs. When I set type="b" things get messed up. Any idea why? I include sample code for

Hi, Our department has detected a bug in the implementation of the Kinderman-Ramage generator for normal random variates in version 1.7.0, which can be seen from the below R session. (Consecutive calls for chisq.test(...) always gives p-values very close to 0.) We have already encountered this bug in version 1.6.2 The error is in file R-1.7.0/src/nmath/snorm.c Here is a patch for this file to

Unfortunately, RNGkind is buggy. It will not generate warnings except the full name "Buggy Kinderman-Ramage" is supplied for normal.kind. match.arg is supposed to be called before "==" comparison. ======================================== Shengqiao Li Research Associate The Department of Statistics PO Box 6330 West Virginia University Morgantown, WV 26506-6330

Hi there, SuSE 8.2 Prof.+Samba 3.0.3 / WinXP Prof clients: I made a script to create new users (creates homedir, sets permissions, creates personalized logon-batch, creates smbpasswd and something more). When the new user logs in for the first time from the client-machine (domain-logon, only domain-users, no local users), he gets default profile with the xp-style menus and so on. I tried

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After a failed migrate from NT4 to Samba 3.0 using the rpc vampire method I decided I'd do it manually with 'net rpc samdump'. Well it sort of worked, except I can't edit any of the users settings, it might just be me, but it should modify the profile to that, just as a test but it doesn't. I'd actually like to get rid of the

On 7 February 2015 at 19:52, otoomet wrote: | random numbers. For instance, can I be sure that | set.seed(0); print(runif(1)); print(rnorm(1)) | will always print the same numbers, also in the future version of R? There Yes, pretty much. I've been lurking here over fifteen years, and while I am getting old and forgetful I can remember exactly one such change where behaviour was changed,

Hello David and Spencer, thank you for your replies! The systemfit-package was exactly what I was looking for. The only little drawback is, that the nonlinear systemfit does not support predifined weights yet (in oder to ensure homegenity of variances when predictios are hetescedastic) Thanks also to Katharina, who mailed me offline and drew my attention to the nls and the nlm function. This

Dear colleague, unfortunately 'rnorm' does not create normal distributed numbers as you can see with following histogramm: > hist(rnorm(1000000),breaks=100) and > hist(pnorm(rnorm(1000000)),breaks=100) I have done several chi^2-tests which have all failed: > chi2unif<- function(x,N) > { > anz=length(x) > f0<-rep(anz/N,times=N) >

I'm running into problems with set.seed--maybe I'm misunderstanding something. I'm running R 1.5.1 on Windows 2000. I'm basically trying to capture the random seed so that I can reproduce a simulation if it's necessary later. Using set.seed, I can certainly get reproducible results, but not the results I get on the first pass. Here's an example: # Generate a random

A short "private" discussion revealed that several people desire to get a prefix in the "subject:"s of R-devel mailings. I'd propose to set "[R-d]" as I've done it (manually, this time!) above. Unless I hear load protests, I'll set this. your mailing list maintainer: Martin Maechler

I've rolled up R-1.7.1.tgz a short while ago. This is a patch version mainly fixing up an assortment of issues (see below). Note also that it comes with an updated set of recommended packages, fixing a couple of nasty issues in at least foreign and nlme. You can get it from http://cran.us.r-project.org/src/base/R-1.7.1.tgz or wait for it to be mirrored at a CRAN site nearer to you. Binaries

I've rolled up R-1.7.1.tgz a short while ago. This is a patch version mainly fixing up an assortment of issues (see below). Note also that it comes with an updated set of recommended packages, fixing a couple of nasty issues in at least foreign and nlme. You can get it from http://cran.us.r-project.org/src/base/R-1.7.1.tgz or wait for it to be mirrored at a CRAN site nearer to you. Binaries

I've asked this before but I don't recall seeing anyone respond. Maybe the answer is so simple that it should jump right out, but its not. I've got three iax connections defined, two working fine (including one to iaxtel), and one that is somewhat intermitant. If I do a cli 'iax show registry' and 'iax2 show registry' I see "both" iax and iax2

I am managing two Xen containers which are exhibiting a spooky behavior. There are intermittent network failures that affect only the VM''s, and not dom0. This exhibits itself as problems with nfs locks, snmp, and even icmp ping. The arp tables look normal on both the dom0 and the guest. However, it is definitely arp related. Causing arp traffic of any sort results the problem curing