Displaying 20 results from an estimated 1000 matches similar to: "smbclient error: NT_STATUS_BAD_NETWORK_NAME, on shared foler with a Chinese name"
2010 Dec 21
4
D drive
Hello all,
I have installed Wine on Opensuse 10.3 and it works great. I need it to use a historical research program where the utility is on the C:/ drive and the data on the D:/ drive.
So, the program works on a very old Window 98 computer and in order to use it, the CD with data on it must be in the CD drive.
I installed Wine, copied the all the files in /home/me/.wine/c_drive/windows/
2011 Oct 22
1
Problem migrating to new Samba server
I am trying, but failing, to migrate an openSUSE Samba server from Samba
3.4.3 on openSUSE 11.2 (old) to Samba 3.5.7 on openSUSE 11.4 (new).
Samba 3.4.3-3.8.1-2508-SUSE-SL11.2
Samba 3.5.7-1.17.1-2505-SUSE-SL11.4-i386
I have a simple smb.conf to share a directory (shareddocs) with a few
users with Linux logins. My smb.conf is identical on both servers. I?ve
added log level = 3 and a temptest
2018 Apr 28
2
[Bug report] Chinese characters are not handled correctly in Rterm for Windows
Hi Tomas,
Sorry for the delayed response. I have tested the problem on the latest R-devel build (2018-04-27 r74651), and it still exists. RGui is always fine with Chinese characters, but some IDEs rely on the CLI version of R (e.g. Visual Studio Code with R plugin).
>Your example print("ABC\u4f60\u597dDEF") is printing two Chinese characters, right?
Yes. U+4F60, U+597D or C4E3,
2018 Mar 08
2
[Bug report] Chinese characters are not handled correctly in Rterm for Windows
Hello everyone,
I am new to R and I have experienced some bugs when using Rterm on Windows.
Chinese characters in the console output are discarded by Rterm, and trying
to type them into the console will crash the Rterm application.
---ENVIRONMENT---
Platform = x86_64-w64-mingw32
OS = Windows 10 Pro 1709 chs
R version = 3.4.3
Active code page = 936 (Simplified Chinese)
---STEPS TO
2009 Sep 18
4
Autofs and Fedora 11
Hi!
I'm having trouble accessing Samba shares via autofs.
Let me begin by saying that I can access the samba shares
directly using smbclient without any trouble. For example:
smbclient //Matsa/Pisi
works fine.
I first started out by copying a config line from an older
system (redhat 7) that has in its auto.misc:
(all on one line, of course)
pisi
2002 Nov 28
1
Samba share is not writeable
I am having difficulty with Windows shares mounted with smb on my linux
machine. The mount directory will not have write permissions for anyone,
no matter what. The mount directory that I use is /home/samba. It has
0700, or drwx------ permissions when it is not connected to Samba. It is
owned by the user jhall, and the group root. When I mount it, if I use
dmask 0777, I get dr-xr-xr-x. If I use
2012 Sep 02
2
possible work plugin deleted_to_trash for otrher foler
Hi Timo
in the present work would be possible to walk to another folder for
deleted_to_trash
please answer me
--
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC2626742
gpg --keyserver pgp.mit.edu --recv-key C2626742
http://about.me/fakessh
http://urlshort.eu fakessh @
http://gplus.to/sshfake
http://gplus.to/sshswilting
http://gplus.to/john.swilting
2003 Jun 06
1
mount a windows FS to a linux box
My friend,
I am trying to mount a windows FS to a linux box, so I can use it form
linux.
I mount my windows filesystem, without errors, the smbclient works great,
but an ls: .: Input/output error appear to my, so I cant see the windows
drive.
You have any ideas? I don't know what to do?
smb: \> ls
. D 0 Mon Jun 2 21
..
2005 Jun 04
1
Unable to browse XP directory
I'm trying to access a share on an XP Home system, from SuSE 9.3, using
Samba. When I use Konqueror to browse, I can't see anything under the
shared directory (D:\), though I can see the contents of the
"SharedDocs" folder. If I mount the XP share manually, I can then see
all the files. Any idea, why Konqueror can't browse that directory?
tnx jk
2007 Mar 01
1
How to detect a printer across a network?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
The shares are browsable again, but the printer can not get detected.
If i list the shares from the PC the printer is connected to, it is
visible..
But somehow it is not visible in konqueror, en thus not selectable.
I used to use the ip adress, but since we are behind a router, these
adresses vary...
monkey9@tribal-sfn2:~> smbclient -L
2004 Oct 03
1
Problem setting up Samba on Fedora Core 2 / XP
I am setting up Samba between a Windows XP and Fedora Core 2 machine but the
FC2 machine is not showing in network neighborhood although I have run the
commands below on the FC2 box with no errors. The FC2 box is leitrim and the
XP machine is kevinden.
[root@leitrim root]# smbclient -L leitrim
Password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.7-2.FC2]
Sharename Type Comment
---------
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
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
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