Displaying 20 results from an estimated 2000 matches similar to: "fwd: tree connect failed: NT_STATUS_BAD_NETWORK_NAME"
2005 Jul 07
0
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Hello everyone!
I've searched the archives and seen this problem crop up a couple of different
times. None of the solutions I've found seemed to have worked.
Here's the synopsis:
I've recently installed FC4 and samba shares for home directories should work
right out of the box. Default settings, etc...
I get this error:
sohmc@bart:~$ smbclient //127.0.0.1/sohmc
added
2008 May 04
1
S4 / S3 / Sweave problem
I'm not sure if this as a bug or something I am doing wrong. It occurs
in both 2.7.0 and 2.6.2.
require("methods")
setClassUnion("OptionalPOSIXct", c("POSIXct", "NULL"))
setClass("TSmetax",
representation(serIDs="character", ExtractionDate="OptionalPOSIXct" ))
setGeneric("TSmetax",
def= function(x,
2017 Aug 22
0
boot.stepAIC fails with computed formula
The error is "the model fit failed in 50 bootstrap samples
Error: non-character argument"
Cheers,
SOH.
On 22/08/2017 17:52, Bert Gunter wrote:
> Failed? What was the error message?
>
> Cheers,
>
> Bert
>
>
> Bert Gunter
>
> "The trouble with having an open mind is that people keep coming along
> and sticking things into it."
> -- Opus (aka
2017 Aug 22
1
boot.stepAIC fails with computed formula
SImplify your call to lm using the "." argument instead of
manipulating formulas.
> strt <- lm(y1 ~ ., data = dat)
and you do not need to explicitly specify the "1+" on the rhs for lm, so
> frm2<-as.formula(paste(trg," ~ ", paste(xvars,collapse = "+")))
works fine, too.
Anyway, doing this gives (but see end of output)"
bst <-
2004 Dec 01
0
Can not connect to share "NT_STATUS_BAD_NETWORK_NAME"
I have Suse 9.1 + Samba 3.0.9 + winbind joined to a Windows
2000 AD domain "MyCompany". Yesterday for some unknown
reason (appears to be Win2K issue) connections to Samba and
the ability to browse the domain "MyCompany" from Win2K/XP
workstations failed but connections to the public share
offered by the Win2K server were OK. Also, all Win98
workstations and were unable to
2017 Aug 22
1
boot.stepAIC fails with computed formula
Failed? What was the error message?
Cheers,
Bert
Bert Gunter
"The trouble with having an open mind is that people keep coming along
and sticking things into it."
-- Opus (aka Berkeley Breathed in his "Bloom County" comic strip )
On Tue, Aug 22, 2017 at 8:17 AM, Stephen O'hagan
<SOhagan at manchester.ac.uk> wrote:
> I'm trying to use boot.stepAIC for
2017 Aug 22
4
boot.stepAIC fails with computed formula
I'm trying to use boot.stepAIC for feature selection; I need to be able to specify the name of the dependent variable programmatically, but this appear to fail:
In R-Studio with MS R Open 3.4:
library(bootStepAIC)
#Fake data
n<-200
x1 <- runif(n, -3, 3)
x2 <- runif(n, -3, 3)
x3 <- runif(n, -3, 3)
x4 <- runif(n, -3, 3)
x5 <- runif(n, -3, 3)
x6 <- runif(n, -3, 3)
x7
2005 Jan 01
1
extlinux probs
I gave extlinux a whirl,
1. installed debian onto a usb hard drive from laptop (onto /dev/sda1)
did *not* install grub or lilo.
2. set up extlinux on /dev/sda
# mount /dev/sda1 /mnt/t1
[root at harpo syslinux-3.00]# cd /mnt/t1/
[root at harpo t1]# ls boot/
config-2.6.8-1-386 initrd.img-2.6.8-1-386 System.map-2.6.8-1-386
vmlinuz-2.6.8-1-386
[root at harpo t1]# mkdir boot/extlinux
[root
2009 Nov 25
1
Eliminating 'Unprintable ASCII' characters
Hi all,
I have a csv file containing words with *UNPRINTABLE ASCII* characters
(described in the following table).
Are there any viable method in eliminating these characters?
I realise that *EXTENDED ASCII* characters (i.e , ¡, ¢, £, ¤ etc) can be
removed or replaced via *"gsub"* or *"gregexpr"* functions. But am not
certain with the *UNPRINTABLE ASCII* characters.
Your
2009 Sep 06
1
NT_STATUS_BAD_NETWORK_NAME
Hi i'm trying to list the shares on my Brother HL-5250DN printer with the
smbtree command on linux but i keep getting the NT_STATUS_BAD_NETWORK_NAME
error message. I can however print to one of the shared printing services with
cups through the Device URI: smb://BRN_E1BEFA/BINARY_P1. Does anyone know what
the problem could be?
linux-wick:~ # smbtree
Password:
WORKGROUP
2002 Jun 23
2
NT_STATUS_BAD_NETWORK_NAME
What is the cause of this particular error.
# smbclient -L localhost
will either work or return this
added interface ip=192.168.0.16 bcast=192.168.0.255 nmask=255.255.255.0
Got a positive name query response from 192.168.0.16 ( 192.168.0.16 )
Anonymous login successful
Domain=[HOME] OS=[Unix] Server=[Samba 2.2.4]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
It working is an intermittent
2006 Mar 29
1
NT_STATUS_BAD_NETWORK_NAME
Hello,
I could use a bit of help with a samba install.
Installation is Samba 3.0.21c on fedora 4
No major changes to smb.conf just added a share point.
[disk]
comment = Disk shares
path =/disk
public = yes
writable = yes
printable = no
guest ok = yes
I opened my share up wide.
ls -l
drwxrwxrwx 10 bob users 1024 Mar 21 16:07 disk
I get my share
2008 Apr 15
0
diagnosing cause of NT_STATUS_BAD_NETWORK_NAME error
I'm trying to find out why I am unable to access public shares on host
mythbe (from host mythbe) due to a NT_STATUS_BAD_NETWORK_NAME error.
I am able to access home shares. I've checked all of the host setup
issues I know about (smb.conf, directory permissions, iptables,
selinux) but I don't see any problems. Can anyone spot a problem or
suggest where I could investigate? Below is
2004 Aug 09
0
Error 4617: SMB connection failed & NT_STATUS_BAD_NETWORK_NAME
Hi folks,
I'm trying to access a share on a RedHat 9 server from a Fedora Core 1
workstation. Here is the environment (pretty vanilla), the error I'm getting,
and what I've done to try hunt down the problem.
Server, 192.168.1.100, has a share of /home/users/herman
Workstation, 192.168.1.101, has a mount point of /home/herman/serverdata
smb.conf on server has
[global]
hosts deny =
2002 Jun 20
1
NT_STATUS_BAD_NETWORK_NAME - Samba 2.2.5
[spstarr@coredump]# smbclient //coredump/ -U spstarr
added interface ip=192.168.10.2 bcast=192.168.10.255 nmask=255.255.255.0
Password:
Domain=[SH0N.NET] OS=[Unix] Server=[Samba 2.2.5]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Yet, if I do smbclient -L coredump -U spstarr, it displays the list of
shares!
I've never seen this before and I'm not sure why this is occuring, When
2007 Aug 29
1
samba-error: tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Hi everyone!
I'm getting mad: On a running debian-edu/skolelinux 3 with samba
3.0.24-6etch4 my win clients lost their server-shares during work and
can't get them back. Tried smbclient
and got:
tjener:~# smbclient -U frank -L tjener
Password:
Domain=[SKOLELINUX] OS=[Unix] Server=[Samba 3.0.24]
Sharename Type Comment
--------- ---- -------
2013 Jun 05
1
NT_STATUS_BAD_NETWORK_NAME for Windows Server 2008
Hi,
Our smbclient calls have started failing on connections to Windows 2008 AD servers. (Previously there were only Windows 2003 Servers, so we had no issues.)
Domain=[INTRANET] OS=[Windows Server 2008 R2 Enterprise 7601 Service Pack 1] Server=[Windows Server 2008 R2 Enterprise 6.1]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Is this post [ http://serverfault.com/a/303483 ] correct when
2009 Dec 29
1
FW: tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Hi Dominic,
I wanted to wait for the original mail to pop up on the list.
But somehow it did not appear yet.
So while the problem seems to be solved meanwhile, I wanted to
comment on the relevant log portion below (see inline):
Dominic Gamble wrote:
> Hi Michael,
>
> As I mentioned, here is the full log file.
>
> Thanks for your time.
>
> Cheers,
> Dominic.
>
>
2010 Jul 06
0
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Hi all,
I have deleted and reinstalled samba 3.4.0 and then I got a failure at starting samba .I guess that was because of lacking of smb.conf ( I have deleted it manually and it didn't install it back)
And I have decided to install samba4 which gave me also the same failure so I have again installed samba 3.4.0 and I found out an smb.conf file from
2008 Aug 07
1
smbclient failed --> NT_STATUS_BAD_NETWORK_NAME
I make all steps in the guide:
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/install.html#id2546028
but command (exetuded in the same computer where is samba):
smbclient //fc9/tester -Utester%test
gives error:
Domain=[DZTI] OS=[Unix] Server=[Samba 3.2.0-17.fc9]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
The user tester have been created by commands:
useradd tester
smbpasswd -a