Something happened (though I don't know what) and a setup that was working for the last 4-5 months, all of a sudden does not work. My Win-XP VM cannot see the Host.
- Host is Windows Vista
- VM is Windows XP SP3, with bridged network adapter
- Have disabled all firewalls (on Host and VM), for testing purposes.
- ALL nodes on the Network can see each other and can see both the Host and the VM
- Host can see all other nodes on the network, but NOT the VM
- VM can see all other nodes on the network, but NOT the Host
I have deleted all other VMs (just in case they were interfering), have double and triple-checked all network adapter settings,... don't know what to try next.
CT
Since I didn't hear about a "server" anywhere in the discussion, I am going to assume the problem is Workgroups, or Network Discovery.
Make usre that both the Host and Guest machines are in the same workgroup. I wuold typically begin at the host to verify that it participates in correct workgroup name. Next, since it is a Vista Host, make sure to turn on Network Discovery....
It is acceptable to use a "private" network as opposed to a public one, since even the guest OS will be a part of the private network workgroup.
Now, lather, rinse, repeat -- that is -- Go into the guest OS and ensure it is in the same workgroup, then enable network discovery by managing Network Settings.
Thank you for the post.
I guess I didn't want to complicate things, that's why I didn't mention a server. The host box is a laptop that's on a domain (when at the office), and a workgroup (when at home) . The workgroup is given the same name as the workgroup, and for the last 3-4 months, access to the the other nodes and the VM has been transparent, as the laptop has been going back-and-forth from home to the office. Access between the host and the VM was lost a couple of days ago, both when at home or at the office.
I checked again, after you post, and the name is indeed the same, and Network discovery is indeed already ON. And, I had already turned the network setting to "Private" for the same reasons you stated.
CT
Replying to my own message... I just wanted to add some more details...
I have tried to eliminate some of the variability in the set-up, so now, the laptop that is running the host OS and the Win-XP VM, is on a domain. Both the host and the VM are members of the domain. Both the host and the VM can see all other nodes on the domain and all other nodes can see the host and the VM. But the two, still can't see each other.
CT
I'm just about ready to delete the VM and uninstall Vmware and start from scratch A lot of wasted hours re-installing all the software on the VM, but at this point if the host can't see the VM, it's not of much use anyway, so... I'm just surprised at how fragile a set-up this is. For months I had this false sense of security that once I set up the VM and it was working properly, nothing major would go wrong. Oh, well.. I've gone over all the help in the on-line FAQs, I have the Virtual network editor to try and see if I could anything jump out as wrong... Don't really know of much else to try
CT
Some basic questions. I am assuming that when you say they can't "see" each other, you are just looking in my network places in XP and Network in Vista?
Do you get any error messages, or do they just not show up?
How about if you do a search for computers on the XP machine?
Can they ping each other by name?
If not, can they ping each other by IP
Can you create a mapped drive using the "net use" command?
Do they both have the DC as the primary DNS server (assuming that it has the DNS role installed).
Do they have NetBios over TCP/IP enabled?
It may help if you post the results of ipconfig/all for both machines.
Just some thoughts...
Lou
Thanks, answers to your thoughtful questions, below. I hope you can spot something that's wrong.
>> Some basic questions. I am assuming that when you say they can't "see" each other, you are just looking in my network places in XP and Network in Vista?
Well, yes, that's one of the ways I tried to see each system
Do you get any error messages, or do they just not show up?
>> They just don't show up
How about if you do a search for computers on the XP machine?
>> Have already tried that, too. Host (Vista) cannot be found
Can they ping each other by name?
>> No
If not, can they ping each other by IP
>> Yes, most of the time
Can you create a mapped drive using the "net use" command?
>> No. I tried using the name and the IP address, but was not able to.
Do they have NetBios over TCP/IP enabled?
>> Yes
It may help if you post the results of ipconfig/all for both machines.
>> Here it is...
Host Win Vista ***
**********************
C:\Users\Pt>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : IBMT62
Primary Dns Suffix . . . . . . . : trius.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : trius.local
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
Physical Address. . . . . . . . . : 00-21-5C-08-76-93
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c52b:302a:b760:6479%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.162.1.115(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, August 17, 2009 7:07:54 PM
Lease Expires . . . . . . . . . . : Tuesday, August 18, 2009 7:07:53 PM
Default Gateway . . . . . . . . . : 192.162.1.1
DHCP Server . . . . . . . . . . . : 192.162.1.1
DNS Servers . . . . . . . . . . . : 71.243.0.12
71.250.0.12
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : trius.local
Description . . . . . . . . . . . : Intel(R) 82566MM Gigabit Network Connection
Physical Address. . . . . . . . . : 00-21-86-5C-0E-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1d80:5e3e:b2d8:8efa%14(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.190.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, August 17, 2009 7:07:47 PM
Lease Expires . . . . . . . . . . : Monday, August 17, 2009 10:13:12 PM
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.190.254
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Virtual Machine Win-XP ***
******************************
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : IBMT62-VM-XP
Primary Dns Suffix . . . . . . . : trius.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : trius.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-14-94-04
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.162.1.117
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.162.1.1
DHCP Server . . . . . . . . . . . : 192.162.1.1
DNS Servers . . . . . . . . . . . : 71.243.0.12
71.250.0.12
Lease Obtained. . . . . . . . . . : Monday, August 17, 2009 7:52:46 PM
Lease Expires . . . . . . . . . . : Tuesday, August 18, 2009 7:52:46 PM
Chris
So, the Host is connecting via WiFi, and the Guest is via bridged, do I read that correct? then I would configure the Default Gateway for the Guest VMNet1 to be 192.162.1.1 so that it can reach the DNS.
Hope that's the ticket?!
Thanks, JasonInLasVegas. That might work, when I am at home, connected through the wifi, but then that would not work next day when I got back to the office, where the setup is different. For example, this morning, after I got to the office, I resumed the VM (like I always did, before I started having these problems, i.e., if I shut down the VM and restart it will have an IP in the new range, but I never had to do that on a paused VM, prior to that ), and here is what the new IPCONFIG info looks like (see below), so setting the default gateway to be 192.162.1.1, would work at home but not at the office, right?
Microsoft Windows http://Version 6.0.6001
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
======= Host, Win Vista
Windows IP Configuration
Host Name . . . . . . . . . . . . : IBMT62
Primary Dns Suffix . . . . . . . : trius.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : trius.local
Wireless LAN adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : trius.local
Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
Physical Address. . . . . . . . . : 00-21-5C-08-76-93
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : trius.local
Description . . . . . . . . . . . : Intel(R) 82566MM Gigabit Network Connection
Physical Address. . . . . . . . . : 00-21-86-5C-0E-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c036:479:6ae9:58cb%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.20(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, August 17, 2009 3:28:46 PM
Lease Expires . . . . . . . . . . : Wednesday, August 26, 2009 7:27:28 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.88
DNS Servers . . . . . . . . . . . : 192.168.1.88
Primary WINS Server . . . . . . . : 192.168.1.88
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1d80:5e3e:b2d8:8efa%14(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.190.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, August 18, 2009 7:27:19 AM
Lease Expires . . . . . . . . . . : Tuesday, August 18, 2009 7:57:18 AM
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.190.254
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
===== VM, Win XP
Windows IP Configuration
Host Name . . . . . . . . . . . . : IBMT62-VM-XP
Primary Dns Suffix . . . . . . . : trius.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : trius.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-14-94-04
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.162.1.117
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.162.1.1
DHCP Server . . . . . . . . . . . : 192.162.1.1
DNS Servers . . . . . . . . . . . : 71.243.0.12
71.250.0.12
Lease Obtained. . . . . . . . . . : Monday, August 17, 2009 7:52:46 PM
Lease Expires . . . . . . . . . . : Tuesday, August 18, 2009 7:52:46 PM