斉藤様 さっそくのレスポンス感謝します。 From: shukaku _at_ j-mac.co.jp Subject: [linux-users:90080] Re: vmware samba trouble Date: Sat, 15 Dec 2001 14:18:41 +0900 Message-ID: <87g06d2h8x.wl _at_ j-mac.co.jp> > At Sat, 15 Dec 2001 13:39:23 +0900, > Ken EBISAWA <ebisawa _at_ astro.isas.ac.jp> wrote: > > > > Window98のWinipcfgで、192.168.22.128が割り当てられていることも確認しま > > した。しかし、Window98でネットワークコンピューターを見てみるとlinuxマ > > シンが現われません。 > > (1) VMWare内のWindows 98のスタートメニュー→検索で、Linux(samba)のPC名を > 指定して探してみても見付からないでしょうか?(→接続したPCが"ネットワー > クコンピュータ"に現れない/現れるまで時間がかかる、ということがあるの > で。) だめみたいですねえ。。。 > (2) VMWare付属のsambaは、自動的にVMWare内の仮想PCからの接続と許可するん > ですよね?(smb.confに"hosts allow = ....."などと書いてやらなくても良 > い/書いてあるのかと。) そうなっています。デフォルトで、 socket address = 192.168.22.1 interfaces = 192.168.22.0/255.255.255.0 という行があり、 ; Allow connections from ; Beware: if we use this directive, smbd will try to do a reverse resolution ; of the guest IP. If the host is disconnected from the network and uses ; named, that reverse resolution will take a long time, and the smb client ; (the guest) will give up waiting for a smb reply before the reverse ; resolution timeout occurs :( ; Because it doesn't add any real security, we don't use this --hpreg ; hosts allow = 192.168.22.0/255.255.255.0 なんて書いてあります。このままでも、hosts allowを有効にしても駄目でした。 > # Windows(VMWare)→Linuxで、telnetなどsamba以外のサービスは機能するんで > # すよね?"VMWare付属samba"とは関係ないかな? Windows (VMware)から、192.168.22.1とlinuxの(仮想)IP address を指定して、teraterm sshでログインできました。でも、DOSプロンプトから open 192.168.22.1とすると、ftp: connect :10061と出て止まってしまいます。 というわけで、いまだsamba走っていません。参考にVMware附属のsmb.confを添付します。 海老沢
; ; Configuration file for Samba 2.0.6 vmware-[sn]mbd operating on vmnet1. ; ; This file was automatically generated by the VMware configuration program. ; If you modify it, it will be backed up the next time you run the ; configuration program. ; ; Global settings [global] ; ; Identity ; ; Allow several Samba servers on different subnet without conflicts socket address = 192.168.22.1 interfaces = 192.168.22.0/255.255.255.0 bind interfaces only = yes ; Workgroup the host belongs to workgroup = WORKGROUP ; SMB name of the host (the hostname by default) ; netbios name = ; Description of the host server string = VMware host ; ; Access ; ; Allow connections from ; Beware: if we use this directive, smbd will try to do a reverse resolution ; of the guest IP. If the host is disconnected from the network and uses ; named, that reverse resolution will take a long time, and the smb client ; (the guest) will give up waiting for a smb reply before the reverse ; resolution timeout occurs :( ; Because it doesn't add any real security, we don't use this --hpreg hosts allow = 192.168.22.0/255.255.255.0 ; Authentication scheme security = user encrypt passwords = yes ; ; Options ; ; Automatically load the printer list (from /etc/printcap by default) load printers = yes ; Gives better performance socket options = TCP_NODELAY ; VMware extension to use a different shared memory access key on each ; Samba server running on this host sysv shm key = /dev/vmnet1 ; ; Files and directories ; ; Debug log for _both_ daemons ; log file = /etc/vmware/vmnet1/smb/var/log.smb ; log level = 1 ; Max log size in KB ; max log size = 50 ; Locks lock directory = /etc/vmware/vmnet1/smb/var/locks ; SMB passwords smb passwd file = /etc/vmware/vmnet1/smb/private/smbpasswd ; VMware extension to use codepages in a different directory codepage dir = /usr/lib/vmware/smb/codepages ; ; Name browsing ; ; Allow the host to participate in master browser elections local master = yes ; Force a local browser election upon startup ; We need that otherwise it takes a long time before the windows network is ; browsable preferred master = yes ; Do not try to resolve SMB names via DNS dns proxy = no ; ; Shared resources ; ; Home directories [homes] comment = Home directories browseable = no writable = yes ; Printers [printers] comment = All printers path = /var/lpd browseable = no guest ok = no writable = no printable = yes [HostFS] comment = VMware host filesystem path = / public = no writeable = yes printable = no
Follow-Ups:
- [linux-users:90083] Re: vmware samba troubleShinichiro WAKASHIMA
- Prev by Subject: [linux-users:90080] Re: vmware samba trouble
- Next by Subject: [linux-users:90082] Re: vmware samba trouble
- Previous by thread: [linux-users:90080] Re: vmware samba trouble
- Next by thread: [linux-users:90083] Re: vmware samba trouble
- Indexes:[Main][Thread]