Windows workgroups unusable when in Korean

Bug #90318 reported by Daeng Bo on 2007-03-07
2
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: gnome-cups-manager

I recently moved to Korea and am attempting to print to a network printer. Gnome-cups-manager reports only a few of the computers on the network. Some of the workgroup names and many of the computer names are in Korean. The non-ASCII names are not reported. This represents no problem to the Windows computers, who can communicate among the Korean workgroups well, but keeps me from using any network access for them. I suspect this problem would occur in other non-ASCII environments like Thai or Chinese.

Originally using Edgy in Xubuntu, I installed ubuntu-desktop (and Gnome) to see if the problem lay with XFCE. Further exploration with findsmb and smbclient on the command line showed similar problems, so I suspect the issue goes quite deep into a library I wouldn't know about.

Non-ASCII workgroups and hostnames are common in Windows environments in Asia. Ubuntu should be able to handle them.

ProblemType: Bug
Architecture: i386
Date: Wed Mar 7 16:30:53 2007
DistroRelease: Ubuntu 7.04
Uname: Linux danielbo 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

Till Kamppeter (till-kamppeter) wrote :

As this problem also shows up when using the command line tools of Samba, it seems to be a problem of Samba. Reassigning the bug to Samba.

Mathias Gug (mathiaz) wrote :

Can you be more specific about what doesn't work ?

Could you post which commands you're using, what are the results and what is expected ?

Changed in samba:
status: New → Incomplete

Wow, this is old!. I'm currently running the Gutsy preview in straight
Ubuntu, but the behavior is the same.

To reproduce:
Browse a Windows network with Korean names for workgroups and
computers (hint: these are NOT in UTF-8, but rather in the Korean
locale)
Browse to the Windows Network under Nautilus.
See some of the workgroups displayed (though not all)
Try to browse a computer or network, and receive and error.

I have attached scrrenshots.

On 9/20/07, Mathias Gug <email address hidden> wrote:
> Can you be more specific about what doesn't work ?
>
> Could you post which commands you're using, what are the results and
> what is expected ?
>
> ** Changed in: samba (Ubuntu)
> Status: New => Incomplete
>
> --
> Windows workgroups unusable when in Korean
> https://bugs.launchpad.net/bugs/90318
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Mathias Gug (mathiaz) wrote :

I don't see any attachement to the bug in LP. Could you attach your screenshot using the web interface ?

Daeng Bo (daengbo) wrote :
Daeng Bo (daengbo) wrote :
Daeng Bo (daengbo) wrote :

Done

Mathias Gug (mathiaz) wrote :

What is the result if you use the command lines you mentioned when you filed the bug report ?

Daeng Bo (daengbo) wrote :

Additional information:
http://lists.samba.org/archive/samba/2006-February/117549.html
My earlier investigations led me to believe there was a porblem with
character encoding similar to this problem in Chinese:
http://lists.samba.org/archive/jcifs/2006-March/005985.html

In order for this to work correctly, Samba need to set the locale
correctly. By default, it uses the locale of the system. It must be
explicitly declared in order to override that. This means that I must
be logged in using the Windows Korean locale (not UTF8) in order to
see anything on the network.

I'll check both that hypothesis and the samba tool output at work.

Daeng Bo (daengbo) wrote :
Download full text (3.3 KiB)

Sorry I dropped this. I guess it will have to wait for Hardy.

danielbo2@danielbo-laptop:~$ smbtree
Password:
╚ú░Þ├╩
╚ú░Þ
└»─í┐°Ãð╗²
(c)­ÁÊÃð¢└
WORKGROUP
        \\┬°ÃÐ╣¦
cli_start_connection: failed to connect to ┬°ÃÐ╣¦<20> (0.0.0.0). Error
NT_STATUS_BAD_NETWORK_NAME
        \\▒│░¿1
failed tcon_X with NT_STATUS_DUPLICATE_NAME
        \\RNP950281
failed tcon_X with NT_STATUS_WRONG_PASSWORD
        \\KMBT537A15
cli_rpc_pipe_open: cli_nt_create failed on pipe \srvsvc to machine
KMBT537A15. Error was ERRCMD - 1
                \\KMBT537A15\IPC$ Remote Inter Process
Communication
                \\KMBT537A15\C252
        \\5-5
                \\5-5\C$ Default share
                \\5-5\ADMIN$ Remote Admin
                \\5-5\print$ 프린터 드라이버
                \\5-5\D$ Default share
                \\5-5\IPC$ Remote IPC
MSHOME
        \\└³╗Û04 6-4
failed tcon_X with NT_STATUS_DUPLICATE_NAME

[As you can see, non-latin names appear as gibberish]

danielbo2@danielbo-laptop:~$ findsmb

                                *=DMB
                                +=LMB
IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
---------------------------------------------------------------------
192.168.1.19 1-9 [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.23 2-2 [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.26 2-5 [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.33 3-1 [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.39 3-7 [3-7] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.40 3-8 [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.43 4-1 [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.44 4-2 [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.47 4-5 [4-5] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.49 4-7 +[4-7] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.54 5-2 [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.56 5-4 [5-4] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.60 ............... [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.61 5-9 [5-9] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.64 6-2 [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.69 6-7 [6-7] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.76 ............... [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.84 ........... [교무] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.85 .......... [전산] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.89 ............... [행정과장] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.90 ............... [행정주임] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.91 ............... [급여통괄] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.96 .............. [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.101 3-10 [호계] [Windows 5.1] [Windows 2000 LAN Manager]
192.168.1.138 8........ +[모둠학습] [Windows ...

Read more...

Daeng Bo (daengbo) wrote :

As you can also see, typing the correct Korean into smbclient also fails:

danielbo2@danielbo-laptop:~$ smbclient //호계/1-9
Connection to 호계 failed (Error NT_STATUS_BAD_NETWORK_NAME)

Daeng Bo (daengbo) wrote :

Any resolution?

Chuck Short (zulcss) wrote :
Daeng Bo (daengbo) wrote :

The smbclient man page lists the following:

 -t terminal code
          This option tells smbclient how to interpret filenames coming from
          the remote server. Usually Asian language multibyte UNIX implementa‐
          tions use different character sets than SMB/CIFS servers (EUC
          instead of
           SJIS for example). Setting this parameter will let smbclient con‐
          vert between the UNIX filenames and the SMB filenames correctly.
          This option has not been seriously tested and may have some prob‐
          lems.

          The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8, CWjunet,
          CWhex, CWcap. This is not a complete list, check the Samba source
          code for the complete list.

It appears, though, that this is competely different than the client
code page setting which I could set to 949 MS-DOS Korean Hangul. I'm
not sure that the code page can be set from the client, though. It
appears to only be set from within the Samba server.

Chuck Short (zulcss) wrote :

Any update on this?

Thanks
chuck

Daeng Bo (daengbo) wrote :

From me? No. The page you linked to doesn't help me with the smbclient problem, as the -t flag just works on the server. Installing and setting the Samba server up isn't really an option for everyone.

I don't have any Ubuntu rigs now, though. They're all Debian.

Daeng Bo (daengbo) wrote :

Why is this still marked as "Incomplete" and expired? I've given all the information I've been asked for.

Chuck Short (zulcss) wrote :

User has no more ubuntu servers to test. Marking as invalid.

Regards
chuck

Changed in samba (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers