> > est-ce que qn peut m'aider à configurer un réseau (host-only) entre
> > windaube 98 sous vmware et ma mandrake 7.1 ? Par exemple, j'ai un
> > vmware samba server, mais je sais pas que faire avec, la doc n'est
> > pas évidente pour qn qui connaît rien au réseau.
> On peut t'aider: étoffes juste un peu tes questions pour entamer un
> sujet de débat :)
> Jean
merci de la réponse, je vais donc étoffer. D'abord voici la config
automatique par vmware:
Stopping VMware services:
Virtual machine monitor [ OK ]
Virtual bidirectional parallel port [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
DHCP server on /dev/vmnet1 [ OK ]
SMB share server on /dev/vmnet1 [ OK ]
SMB name server on /dev/vmnet1 [ OK ]
Host-only networking on /dev/vmnet1 [ OK ]
Virtual ethernet [ OK ]
Trying to find a suitable vmmon module for your running kernel.
None of VMware's pre-built vmmon modules is suitable for your running
kernel. Do you want this script to try to build the vmmon module for your
system (you need to have a C compiler installed on your system)? [yes] y
What is the location of the directory of C header files that match your
running kernel? [/usr/src/linux/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make[1]: Entering directory `/tmp/vmware-config0/vmmon-only'
make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.2.15-4mdk'
make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.2.15-4mdk'
make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.2.15-4mdk'
make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.2.15-4mdk'
make[1]: Leaving directory `/tmp/vmware-config0/vmmon-only'
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.
Making sure that both the parport and parport_pc kernel services are
available.
Trying to find a suitable vmppuser module for your running kernel.
None of VMware's pre-built vmppuser modules is suitable for your
running kernel. Do you want this script to try to build the vmppuser
module for your system (you need to have a C compiler installed on your system)? [yes]
y
Extracting the sources of the vmppuser module.
Building the vmppuser module.
make: Entering directory `/tmp/vmware-config0/vmppuser-only'
make: Leaving directory `/tmp/vmware-config0/vmppuser-only'
The module loads perfectly in the running kernel.
Do you want this script to automatically configure your system to allow
your Virtual Machines to access the host filesystem?
(yes/no/help) [yes] y
The version of Samba used in this version of VMware is licensed as
described in the "/opt/vmware/doc/SAMBA-LICENSE" file.
Hit enter to continue.
Enabling networking (this is required to share the host filesystem).
Trying to find a suitable vmnet module for your running kernel.
None of VMware's pre-built vmnet modules is suitable for your running
kernel. Do you want this script to try to build the vmnet module for your
system (you need to have a C compiler installed on your system)?
[yes] y
Extracting the sources of the vmnet module.
Building the vmnet module.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make: Leaving directory `/tmp/vmware-config0/vmnet-only'
The module loads perfectly in the running kernel.
Enabling host-only networking (this is required to share the host filesystem).
Host-only networking is currently configured to use the private subnet
192.168.167.0/255.255.255.0. Do you want to keep these settings? [yes] y
Starting VMware services:
Virtual machine monitor [ OK ]
Virtual bidirectional parallel port [ OK ]
Virtual ethernet [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
Host-only networking on /dev/vmnet1 (background) [ OK ]
You have successfully configured VMware to allow your Virtual Machines
to access Password changed for user klaus.
You have successfully configured VMware to allow your Virtual Machines
to access the host filesystem. Your system appears to already be
set up with usernames and passwords for accessing the host
filesystem. Would you like to add another username and password at
this time? (yes/no/help) [no] n You can add more usernames at any
time by invoking the following command as root:
"/opt/vmware/vmware-smbpasswd vmnet1 -a <username>" The
configuration of VMware 2.0.2 build-621 for Linux for this running
kernel completed successfully.
Donc si j'ai bien compris, vmware contient une version spéciale de
samba (je n'ai installé samba) qu'il a configuré automatiquement,
donc du côté linux, plus rien à faire.
Côté windaube:
Configuration:
- Client pour les rééseaux MS
- Carte réseaux virtuel (reconnu par windoze)
- Protocole compatible IPX/SPX
- TCP/IP
- Partage des fichier .... (activé)
Propriétés TCP/IP:
- Adresse IP: 181.36.10.131
- Masque de sous-réseau: 255.255.255.0
- Passerelles installées: 192.168.167.0
255.255.255.0
DNS activé:
- hôte: localhost
- domaine: localdomaine
- ordre de recherche DNS: 192.168.167.0
255.255.255.0
Identification
- Nom de l'ordinateur: windoof
- Groupe de travail: billou
Contrôle d'accès:
- ...au niveau utilisateur: 255.255.255.255 (par défault)
résultat: j'ai que le réseau global, parcours impossible. Je connais
rien au réseau, donc j'ai essayé et il y a sûrement des erreurs.
Précision: j'ai de pas carte réseau physique sur mon PC (mais je vais
en acheter une pour le ADSL), mais il me semble que la carte virtuelle
de vmware suffit. Ce qui m'intéresse, c'est importer des fichiers de
linux dans windaube sous vmware par le réseau (pour OCR), ensuite
l'export du texte en sens inverse se fait par copier-coller.
Voilà toutes les infos, à vous de jouer
d'avance merci
Klaus....pingouin virtuel.... :-)
--
. - . It's time to close the Windows
/ v \
// \\ Linux for free people !
/( )\
^^-^^ Le monde n'est pas une marchandise !
