Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Networking issues between host and guest OS's

3 views
Skip to first unread message

C Masters

unread,
Feb 15, 2001, 6:31:14 PM2/15/01
to

Greetings,

I've just recently succeeded in migrating from Win98 to Linux. It took me
over three months to find an installation that worked; as a result, I am
using Mandrake 7.2.

I've been able to install VMware Workstation, and Win98 as my guest OS but
am unable to network between the host and guest OS's. I accepted defaults
for allowing the install script to configure Samba, but am unable to see
any "network" drives or explicitly map them in W98.

I am connected to the internet by a DSL that is routed through my local
ISP. Everything works wrt connecting to the internet, but I can't seem to
configure any of the virtual devices that are created by VMware. I have
tried both specifying a host name and leaving it blank. Either works well
on internet functions. However, when I assign a host name to my system, it
shows on the guest OS (W98) as a network entry, but then requires a
password to access the drives and devices on it. ~No~ combination of
passwords works for access. I have tried the root, my user, and another
user that has been set up on my system.

Could someone please advice in ~clear~ relatively non-technical terms how I
can facilitate ~full~ communication between my host and guest OS's.
Unfortunately I must continue to use W98 for some accounting software and
need to be able to print reports and have access to the raw data for spread
manipulation in Linux.

Many thanks,
C. Masters

p.s. please cc to my email as I could easily get lost in the volume of
traffic on this groups.

Chuck Gladu

unread,
Feb 15, 2001, 11:00:10 PM2/15/01
to
Sorry, I do not reply by e-mail.

And since a ~full~ explanation of what you need to do would involve
copying and pasting all of the Samba documentation into this message,
you're not getting that either.

Welcome to the world of Linux. You need to learn to use TECHNICAL
terms and documentation.

Start with the documentation for Samba.


On Thu, 15 Feb 2001 23:31:14 +0000, C Masters <cmas...@nbnet.nb.ca>
wrote:

C Masters

unread,
Feb 15, 2001, 7:33:30 PM2/15/01
to
Chuck Gladu wrote:

I had ~hoped~ that was unnecessary, as during installation of VMware, it is
~strongly~ implied that it will "set up Samba" for you. I find it difficult
to equate this with the need to re-configure Samba when VM has been
installed.

Quote from pg 1-4 of the installation guide:

"If Samba is not already running on your host computer, answer Yes to [the
installation question regarding configuring virtual/host access] and the
VMware installer will configure it for you. When prompted for a user name
and password to use with Samba configuration, enter the user name you used
in set 1 above."

Couldn't seem like a clearer statement of automatic set-up to me!

C. Masters


David D. Huff Jr.

unread,
Feb 15, 2001, 11:56:28 PM2/15/01
to C Masters

C Masters wrote:

> Greetings,
>
> I've just recently succeeded in migrating from Win98 to Linux. It took me
> over three months to find an installation that worked; as a result, I am
> using Mandrake 7.2.
>
> I've been able to install VMware Workstation, and Win98 as my guest OS but
> am unable to network between the host and guest OS's. I accepted defaults
> for allowing the install script to configure Samba, but am unable to see
> any "network" drives or explicitly map them in W98.
>
> I am connected to the internet by a DSL that is routed through my local
> ISP. Everything works wrt connecting to the internet, but I can't seem to
> configure any of the virtual devices that are created by VMware. I have
> tried both specifying a host name and leaving it blank. Either works well
> on internet functions. However, when I assign a host name to my system, it
> shows on the guest OS (W98) as a network entry, but then requires a
> password to access the drives and devices on it. ~No~ combination of
> passwords works for access. I have tried the root, my user, and another
> user that has been set up on my system.

Ahh use lower case for both User ID and password. I wouldn't use root if
you will be accessing the internet using xDSL and windoze98. Some little
fiend from M$ could reek havoc on your system.

Bob G

unread,
Feb 16, 2001, 2:40:53 AM2/16/01
to

"C Masters" <cmas...@nbnet.nb.ca> wrote in message
news:96ig32$s7a$1...@london.vmware.com...
> [...]

> I had ~hoped~ that was unnecessary, as during installation of VMware, it
is
> ~strongly~ implied that it will "set up Samba" for you. I find it
difficult
> to equate this with the need to re-configure Samba when VM has been
> installed.

But keep in mind that VMware has no control over how you've configured your
_guest_. And you've given us precious little to go on. How about some hints?
Start with: What Domain/Workgroup did you use? How is it configured?

> Quote from pg 1-4 of the installation guide:
>
> "If Samba is not already running on your host computer, answer Yes to [the
> installation question regarding configuring virtual/host access] and the
> VMware installer will configure it for you. When prompted for a user name
> and password to use with Samba configuration, enter the user name you used
> in set 1 above."

Chuck's dead-on in that you need to understand the technical aspects, even
IF VMware has set up a default to get you started. If basic networking is
working and you're

Samba probably *IS* configured and running, but you need to configure your
guest to talk to it. Do you see ANYTHING? Did you try connecting to the
server using a UNC?

> Couldn't seem like a clearer statement of automatic set-up to me!

Exactly. **SAMBA** has been set up automatically. Now you need to work on
the guest that you want to use it.

- Bob


C Masters

unread,
Feb 16, 2001, 1:56:43 PM2/16/01
to
Greetings Bob,

Firstly, thank you for the encouragement and explanations. Details as
required below:

Bob G wrote:

>
> "C Masters" <cmas...@nbnet.nb.ca> wrote in message
> news:96ig32$s7a$1...@london.vmware.com...
> > [...]
> > I had ~hoped~ that was unnecessary, as during installation of VMware, it
> is
> > ~strongly~ implied that it will "set up Samba" for you. I find it
> difficult
> > to equate this with the need to re-configure Samba when VM has been
> > installed.
>
> But keep in mind that VMware has no control over how you've configured
> your _guest_. And you've given us precious little to go on. How about some
> hints? Start with: What Domain/Workgroup did you use? How is it
> configured?

On my host -- all assigned by my ISP:

Domain: ip010169233146
ip: 10.169.233.146
subnet mask: 255.255.255.248
gateway: 10.169.233.145
DNS (1/2) 192.168.254.2 / 192.168.253.2

On my guest (W98):

I used the same info and have "use DHCP" selected in WINS resolution. I
guess what's confusing me, is that the examples in the set-up guide for IP
addresses all begin with "192" and therefore more closely resemble my DNS
assignments.

Am I able to assign a "virtual" IP address to my guest? My ISP "doesn't
officially support ~any~ Linux configurations" and assumes that all are
using MS apps. Also, I'm having difficulty identifying the exact nature of
my problem in order to solve it through the various Samba and networking
docs.

Any help would be greatly appreciated.
>
> > ... snip quote from install manual ...


>
> Chuck's dead-on in that you need to understand the technical aspects, even
> IF VMware has set up a default to get you started. If basic networking is
> working and you're
>
> Samba probably *IS* configured and running, but you need to configure your
> guest to talk to it. Do you see ANYTHING? Did you try connecting to the
> server using a UNC?

Again, unfamiliar with the tech terminology. It's like me using shortforms
and numerical codes for "common" accounting terms when explaining
bookkeeping to a newbie.

> > Couldn't seem like a clearer statement of automatic set-up to me!
>
> Exactly. **SAMBA** has been set up automatically. Now you need to work on
> the guest that you want to use it.

I suspect this is so, but I can't figure out how the settings change when
W98 becomes a guest OS on a Linux system. The defaults don't seem to apply.

>
> - Bob
>
>

Thanks for any help you can provide.

C. Masters

Brian Marr

unread,
Feb 16, 2001, 11:54:27 PM2/16/01
to

What does ifconfig say ?

Try.... smbstatus

Try to ping the Guest.....ping 192.168.50.? Try to ping the address in
vmnet 1(from ifconfig) from guest.

Remember to start and stop Samba everytime you make a config change

........./usr/sbin/smbd stop
........./usr/sbin/smbd start

Try.... testparm

Dont forget that Win98 has to have file and print sharing enabled, and
shared level access control.

Brian Marr

Bob G

unread,
Feb 18, 2001, 9:36:39 PM2/18/01
to

"C Masters" <cmas...@nbnet.nb.ca> wrote in message
news:96kgn0$uri$1...@london.vmware.com...
> [...]

> Am I able to assign a "virtual" IP address to my guest? My ISP "doesn't
> officially support ~any~ Linux configurations" and assumes that all are
> using MS apps. Also, I'm having difficulty identifying the exact nature of
> my problem in order to solve it through the various Samba and networking
> docs.

Your ISP no doubt only assigns you one IP address. You probably need to
share it, either using NAT or proxy. The VMware docs cover all this, and
you'll need to spend some time with the (non-VMware) Linux documentation to
truly understand it. Try "Linux NAT proxy" in any search engine to get
going.

> [...]


> Again, unfamiliar with the tech terminology. It's like me using shortforms
> and numerical codes for "common" accounting terms when explaining
> bookkeeping to a newbie.

> [...]


> I suspect this is so, but I can't figure out how the settings change when
> W98 becomes a guest OS on a Linux system. The defaults don't seem to
apply.

Which is why folks are pointing you to the (non-VMware) Samba documentation.
It's all described VERY clearly in the Samba documentation. If browsing
isn't working, start there. You'll learn lots.

Good luck,

- Bob

C Masters

unread,
Feb 18, 2001, 8:53:46 PM2/18/01
to
Greetings Bob,

Thanks again for the sage advice. I'm happy to report that after much
searching/reading/experimenting I've been able to get my networking issues
resolved.

It involved viewing both the standard and VM 'smb.conf' files to find which
IP had been assigned when VM was installed, then making the necessary
entries in W98 to allow it to communicate with Linux.

Now I'm a little better read and a tad smarter *grin*. Wouldn't have
happened without encouragement and help from here.

Thanks again.

C. Masters

0 new messages