• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1296
  • Last Modified:

VMWare Guest Can't Access Shares on Host Server

Host Machine running Server 2003 sp 2 and VMWare Workstation 7.01.

Guest Machine is Server 2003 R2.

The Guest Machine can see (and be seen by) all computers on the network and it can ping (and be pinged by) the host, by name.  The Guest Machine can also access all other shares on the network.

However, opening windows explorer and trying to access \\host\share  (it's a good share that everyone else can see all over the network), times out.

Trying the NET USE command gets an error 67, network name cannot be found.

But pinging the host by name works.

Any ideas?

Thanks.
0
gateguard
Asked:
gateguard
  • 4
  • 4
  • 2
1 Solution
 
Paul SolovyovskySenior IT AdvisorCommented:
Try mapping via IP address.  Also make sure the VM is configured in bridge mode.  
0
 
coolsport00Commented:
Have you enabled sharing?
See pg. 190-191:
http://www.vmware.com/pdf/ws7_manual.pdf

Regards,
~coolsport00
0
 
gateguardAuthor Commented:
It is in bridged mode (could it see the rest of the network otherwise?) and net use \\ipaddress\share gets the same error 67.
0
Take Control of Web Hosting For Your Clients

As a web developer or IT admin, successfully managing multiple client accounts can be challenging. In this webinar we will look at the tools provided by Media Temple and Plesk to make managing your clients’ hosting easier.

 
gateguardAuthor Commented:
Whoops.  I made a mistake.

I have  a server running VMWare Workstation 7.01 and another running VMWare Server 1.0.9.

This problem I'm having is on a Server 2003 sp2 Host running VMWare Server 1.0.9.

The guest is the way I said, though, Server 2003 R2.

Sorry about the confusion.  Should I ask to have this question deleted and start over?

Otherwise, the problem is the same, and there is no Sharing in Options on Server 1.0.9.

But anyway, the host can see the guest shares... it's the guest who can't see the host shares.

0
 
coolsport00Commented:
Nah...you should be ok, as long as it's now clarified. :)

I came across this MS KB...did you try it?
http://support.microsoft.com/kb/875441

~coolsport00
0
 
Paul SolovyovskySenior IT AdvisorCommented:
From the guest try to do a nslookup, make sure the ip matches hostname. Also check you arp tables on the guest to make sure it's picking up the correct mac for the host and not the mac for the nat mode virtual nic.
0
 
gateguardAuthor Commented:
I'm being warned that this is an abandoned question so I'm putting this note here to keep it active.

Nothing so far has worked... nothing.  Not the solutions offered in this thread or in any thread I've read on this subject on the internet, including threads regarding the EXACT SAME PROBLEM for LINUX users!

There is SOMETHING about guest-accessing-host-share that is problematic.

Today I think I stumbled on a solution.

But before I post that solution here I want to do some more testing to make SURE it works.

0
 
coolsport00Commented:
Ok...well, please keep us posted. :)

~coolsport00
0
 
gateguardAuthor Commented:
ok, it's fixed.

Here's what I had to do:

I added a second nic card to the vm and chose custom networking and then chose one of the 2 vm nic cards (VMNet1).

Then I manually gave it an ip address that was on the same network as the host machine's VMNet1 card.

On the host machine, VMNet1 has an address of 172.16.112.1 255.255.255.0, no gateway.  I have the vm's new nic card 172.16.112.2 255.255.255.0, no gateway.

Then, in the vm, I edited the hosts file with this line:
172.16.112.1 hostmachinename

It worked.  I did the same thing on all the other vm's on this host server, incrementing the ip address in each case, of course, and editing the hosts file on each machine (only with the hostmachinename, they can talk to each other over their 1st bridged nic card).

So now all the vm's running on the host server can see the share published on the host server and all are happy and I am happy and I am also very appreciative of the help given here (as always) and the only remaining task is to close this question in such a way that this note gets marked as the solution so that when others run into this problem they will be directed to the solution.

How do I go about doing that?
0
 
coolsport00Commented:
Click on the link below your comment that says something like "accept as solution" and that should do it...

Glad it's resolved and thanks for posting the answer.

~coolsport00
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now