Виртуальная винда не видит host
Добавлено: 20 окт 2002, 17:41
OS AspLinux 7.3 Vmware 3.2.0
Настроил на виртуальной винде сеть. Сама себя через вирт. сетевуху видит, хост - ни в какую. Ping на хост не проходит.
Мои настройки:
вывод route в linux
[root@localhost samba]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.5.0 * 255.255.255.0 U 0 0 0 vmnet8
192.168.210.0 * 255.255.255.0 U 0 0 0 vmnet1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
В винде настроено так:
IP 192.168.210.2
Шлюз 192.168.210.1
В линуксе
vmware-samba
host-only
файл /etc/vmware/vmnet1/smb/smb.conf - усе по умолчанию
;
; Configuration file for Samba 2.0.6 vmware-[sn]mbd operating on vmnet1.
; Global settings
[global]
;
; Identity
;
; Allow several Samba servers on different subnet without conflicts
socket address = 192.168.210.1
interfaces = 192.168.210.0/255.255.255.0
bind interfaces only = yes
; Workgroup the host belongs to
workgroup = 1
; SMB name of the host (the hostname by default)
netbios name = 192.168.52.1
; 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.52.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 = yes
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
В чем может быть проблема, может какие-нить конфиги еще посмотреть надо.
Help pleaazzzze
ЗЫ А то мне так 30 дневной лицензии не хватит.
Настроил на виртуальной винде сеть. Сама себя через вирт. сетевуху видит, хост - ни в какую. Ping на хост не проходит.
Мои настройки:
вывод route в linux
[root@localhost samba]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.5.0 * 255.255.255.0 U 0 0 0 vmnet8
192.168.210.0 * 255.255.255.0 U 0 0 0 vmnet1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
В винде настроено так:
IP 192.168.210.2
Шлюз 192.168.210.1
В линуксе
vmware-samba
host-only
файл /etc/vmware/vmnet1/smb/smb.conf - усе по умолчанию
;
; Configuration file for Samba 2.0.6 vmware-[sn]mbd operating on vmnet1.
; Global settings
[global]
;
; Identity
;
; Allow several Samba servers on different subnet without conflicts
socket address = 192.168.210.1
interfaces = 192.168.210.0/255.255.255.0
bind interfaces only = yes
; Workgroup the host belongs to
workgroup = 1
; SMB name of the host (the hostname by default)
netbios name = 192.168.52.1
; 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.52.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 = yes
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
В чем может быть проблема, может какие-нить конфиги еще посмотреть надо.
Help pleaazzzze
ЗЫ А то мне так 30 дневной лицензии не хватит.