VMWARE 10: Problem with Applications accessing the internet and problem with the network printer finding the printer

I have my personal laptop loaded with Centos 7.  It uses a wireless connection to my local (personal) network.  I have a HP priner on my network and a Seagate NAS.  Centos has access to the NAS and the printer.  I try to always use linux, but at times have to use Windows applications -- iTunes, Quicken, GPS updates ,etc.  So I installed VMWare 10 and created a Windows 7 virtual machine. When creating the default VMWare Windows 7 VM machine, it setup a NAT network adapter.   With NAT, I was unable to see my local network printer and my NAS, but could connect to the internet.  I setup iTunes, Quicken and other applications.  They were able to connect to the internet without issues.

Then I read that I needed to setup a bridge, rather than net - to fix my local are network issues.  I changed my VM setting to bridge, replicate physical network connection state.  Once I did this, all of my NAS drives became visible in Windows explorer.  They work great.  I could connect to the internet via a browser - no problem.  However, now my HP printer is no longer available, and iTunes errors states it cannot connect to the internet - but my browser can connect to the internet.

I mainly focused on iTunes access to the internet, so I thought maybe iTune locks into the network adaptor hardware.  So, I uninstall iTunes and re-installed it.  Did not work.  Moreover, an add on installed on my browser gives an error that it can not longer access the internet.  Yet my browser (google chrome, firefox) can access the internet.

What is going on here????
LVL 1
DCCoolBreezeAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
When using NAT the internet information is "routed" through your Host ethernet connection, and also DNS and Default gateway information is used from the host.

Now you have a Bridged Connection, just like your hosts ethernet connection, your IP Address (I'm assuming) is being issued by DHCP, and DNS, Default Gateway are all provided by DHCP.

This would suggest firewall, or DNS related issues.
DCCoolBreezeAuthor Commented:
yes. my vm has its own ip from dhcp and the dns gateway is that of the hosts, so yes, it is getting its own connection.   hmmm.  not sure i understand why it would be a firewall issue.  please understand, i am learning about different network connections.  when using NAT, iTunes was able to see the network - iTunes is not compatible with linux, so i would think that the host firewall settings would not be important - now i have bridged, and iTunes cannot access the internet.  I reinstalled iTunes, so it should have updated firewall settings accordingly.  I am confused, can you step me through the difference between NAT and bridge, and then what I must do to troubleshoot.

what i really find interesting is my local network printer application can no longer find the printer.  i use hp software  with the hp l7580.  why would the software no longer see the printer, when i can see my nas just fine????
ThomasMcA2Commented:
I use Linux on my employer-provided laptop, and currently run Win7 in a VM. I have distro-hopped through at least 5 distros and used both VMware and VirtualBox, and networking has always worked fine with just NAT. You usually don't need bridged when you only have a single VM. I also add a 2nd virtual NIC using "host-only" because I want the VM to access the web server that I run in the Linux host.

Once networking works from the VM to the Internet, it should work from the VM to your NAS and your printer, without any additional changes or configuration required. That is why Andrew suggested a firewall or DNS issue, because it is not a network config issue.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

DCCoolBreezeAuthor Commented:
OK.  I went back to NAT on my VMWare VM, but now I can no longer access my Seagate GoHome NAS.  Where as I can see it if I bridge the network card.  Why can I not see my NAS in my VMWare Windows VM???
DCCoolBreezeAuthor Commented:
Moreover, now my HP printer software can not longer see my printer... OK.  Interestingly, the IP address of my VM is NOT in the domain of my local network IP addresses.  So perhaps that is the problem.  Them my question would be how do I get my VM on the same network as my local network?
DCCoolBreezeAuthor Commented:
My local network is that standard 192.168.x.xxxx while my VM IP address is 172.16.xx.xxxx
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
it's because the traffic is NATTed...

if you knew the TCP and UDP ports, it's possible you could use Advanced NAT to resolve this issue, but you would need to find out what ports are being used by the HP software.

To get you VM on the same network as your local network, you would use Bridged networking.
DCCoolBreezeAuthor Commented:
OK.  I set my Windows 7 VM back to bridged from NAT.  I go back to the original problem.  I can see my printer and my NAS drives.  I can access the internet.  However,  Itunes Store and authorizing the computer for iTunes returns an error that there is no internet connection.  Another application that accesses the internet responds with the same no internet connection error message.   what do I need to do next?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
can you confirm that DNS and Default Gateway routing is working correctly ?
DCCoolBreezeAuthor Commented:
sure.  How can I do that?  I will have to look it up on the internet to see how to do it, or if you could give me some commands, I would appreciate it.
DCCoolBreezeAuthor Commented:
OK.  I used pingdom.com to test my DNS.  Everything checked out good except SOA.  Following is the log:

Begin testing delegation for google.com.
Name servers listed at parent: ns1.google.com,ns2.google.com,ns3.google.com,ns4.google.com
Name servers listed at child: ns1.google.com,ns2.google.com,ns3.google.com,ns4.google.com
No IPv6 name servers found.
Parent glue for google.com found: ns1.google.com (216.239.32.10)
Parent glue for google.com found: ns2.google.com (216.239.34.10)
Parent glue for google.com found: ns3.google.com (216.239.36.10)
Parent glue for google.com found: ns4.google.com (216.239.38.10)
Checking glue for ns1.google.com (216.239.32.10).
Child glue for google.com found: ns1.google.com (216.239.32.10)
Checking glue for ns2.google.com (216.239.34.10).
Child glue for google.com found: ns2.google.com (216.239.34.10)
Checking glue for ns3.google.com (216.239.36.10).
Child glue for google.com found: ns3.google.com (216.239.36.10)
Checking glue for ns4.google.com (216.239.38.10).
Child glue for google.com found: ns4.google.com (216.239.38.10)
Parent glue for google.com found: ns1.google.com (216.239.32.10)
Parent glue for google.com found: ns2.google.com (216.239.34.10)
Parent glue for google.com found: ns3.google.com (216.239.36.10)
Parent glue for google.com found: ns4.google.com (216.239.38.10)
Nameserver
Done testing delegation for google.com.
Begin testing name server ns1.google.com.
Begin testing host ns1.google.com.
Begin testing address 216.239.32.10.
Done testing address 216.239.32.10.
Done testing host ns1.google.com.
Name server ns1.google.com (216.239.32.10) answers queries over UDP.
Name server ns1.google.com (216.239.32.10) answers queries over TCP.
Name server ns1.google.com (216.239.32.10) is not recursive.
Name server ns1.google.com (216.239.32.10) authoritative for google.com.
Name server ns1.google.com (216.239.32.10) closed for zone transfer of google.com.
No answer received from 216.239.32.10 when querying for hostname.bind/CH/TXT.
No answer received from 216.239.32.10 when querying for version.bind/CH/TXT.
No answer received from 216.239.32.10 when querying for id.server/CH/TXT.
No answer received from 216.239.32.10 when querying for version.server/CH/TXT.
Done testing name server ns1.google.com.
Begin testing name server ns2.google.com.
Begin testing host ns2.google.com.
Begin testing address 216.239.34.10.
Done testing address 216.239.34.10.
Done testing host ns2.google.com.
Name server ns2.google.com (216.239.34.10) answers queries over UDP.
Name server ns2.google.com (216.239.34.10) answers queries over TCP.
Name server ns2.google.com (216.239.34.10) is not recursive.
Name server ns2.google.com (216.239.34.10) authoritative for google.com.
Name server ns2.google.com (216.239.34.10) closed for zone transfer of google.com.
No answer received from 216.239.34.10 when querying for hostname.bind/CH/TXT.
No answer received from 216.239.34.10 when querying for version.bind/CH/TXT.
No answer received from 216.239.34.10 when querying for id.server/CH/TXT.
No answer received from 216.239.34.10 when querying for version.server/CH/TXT.
Done testing name server ns2.google.com.
Begin testing name server ns3.google.com.
Begin testing host ns3.google.com.
Begin testing address 216.239.36.10.
Done testing address 216.239.36.10.
Done testing host ns3.google.com.
Name server ns3.google.com (216.239.36.10) answers queries over UDP.
Name server ns3.google.com (216.239.36.10) answers queries over TCP.
Name server ns3.google.com (216.239.36.10) is not recursive.
Name server ns3.google.com (216.239.36.10) authoritative for google.com.
Name server ns3.google.com (216.239.36.10) closed for zone transfer of google.com.
No answer received from 216.239.36.10 when querying for hostname.bind/CH/TXT.
No answer received from 216.239.36.10 when querying for version.bind/CH/TXT.
No answer received from 216.239.36.10 when querying for id.server/CH/TXT.
No answer received from 216.239.36.10 when querying for version.server/CH/TXT.
Done testing name server ns3.google.com.
Begin testing name server ns4.google.com.
Begin testing host ns4.google.com.
Begin testing address 216.239.38.10.
Done testing address 216.239.38.10.
Done testing host ns4.google.com.
Name server ns4.google.com (216.239.38.10) answers queries over UDP.
Name server ns4.google.com (216.239.38.10) answers queries over TCP.
Name server ns4.google.com (216.239.38.10) is not recursive.
Name server ns4.google.com (216.239.38.10) authoritative for google.com.
Name server ns4.google.com (216.239.38.10) closed for zone transfer of google.com.
No answer received from 216.239.38.10 when querying for hostname.bind/CH/TXT.
No answer received from 216.239.38.10 when querying for version.bind/CH/TXT.
No answer received from 216.239.38.10 when querying for id.server/CH/TXT.
No answer received from 216.239.38.10 when querying for version.server/CH/TXT.
Done testing name server ns4.google.com.
Consistency
Begin testing zone consistency for google.com.
SOA at address 216.239.38.10 has serial 2015041501.
SOA at address 216.239.36.10 has serial 2015041501.
SOA at address 216.239.34.10 has serial 2015041501.
SOA at address 216.239.32.10 has serial 2015041501.
All SOA records have consistent serial numbers.
All SOA records are consistent among all name servers.
Done testing zone consistency for google.com.
SOA
Begin testing SOA parameters for google.com.
Found SOA record for google.com.
Begin testing host ns1.google.com.
Begin testing address 216.239.32.10.
Done testing address 216.239.32.10.
Done testing host ns1.google.com.
SOA MNAME for google.com valid (ns1.google.com).
SOA MNAME for google.com (ns1.google.com) listed as NS.
SOA MNAME for google.com (ns1.google.com) is authoritative.
Begin testing email address dns-admin@google.com.
Mail exchangers for dns-admin@google.com found aspmx.l.google.com,alt1.aspmx.l.google.com,alt2.aspmx.l.google.com,alt3.aspmx.l.google.com,alt4.aspmx.l.google.com.
All mail servers for dns-admin@google.com are in zone google.com.
Begin testing host aspmx.l.google.com.
Begin testing address 173.194.71.26.
Done testing address 173.194.71.26.
Begin testing address 2a00:1450:4010:c04:0:0:0:1a.
Done testing address 2a00:1450:4010:c04:0:0:0:1a.
Done testing host aspmx.l.google.com.
Begin testing mail server aspmx.l.google.com (173.194.71.26) with dns-admin@google.com.
SMTP banner: mx.google.com ESMTP au9si6493842lbc.168 - gsmtp
SMTP testing of aspmx.l.google.com (173.194.71.26) with dns-admin@google.com succeeded without errors.
Done testing mail server aspmx.l.google.com (173.194.71.26) with dns-admin@google.com.
Begin testing host alt1.aspmx.l.google.com.
Begin testing address 74.125.23.27.
Done testing address 74.125.23.27.
Begin testing address 2404:6800:4008:c07:0:0:0:1b.
Could not find reverse address for 2404:6800:4008:c07:0:0:0:1b (b.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.0.c.0.8.0.0.4.0.0.8.6.4.0.4.2.ip6.arpa.).
Done testing address 2404:6800:4008:c07:0:0:0:1b.
Done testing host alt1.aspmx.l.google.com.
Begin testing host alt2.aspmx.l.google.com.
Begin testing address 173.194.72.27.
Done testing address 173.194.72.27.
Begin testing address 2404:6800:4008:c01:0:0:0:1b.
Done testing address 2404:6800:4008:c01:0:0:0:1b.
Done testing host alt2.aspmx.l.google.com.
Begin testing host alt3.aspmx.l.google.com.
Begin testing address 74.125.25.26.
Done testing address 74.125.25.26.
Begin testing address 2607:f8b0:400e:c03:0:0:0:1a.
Done testing address 2607:f8b0:400e:c03:0:0:0:1a.
Done testing host alt3.aspmx.l.google.com.
Begin testing host alt4.aspmx.l.google.com.
Begin testing address 173.194.64.27.
Done testing address 173.194.64.27.
Begin testing address 2607:f8b0:4003:c02:0:0:0:1a.
Done testing address 2607:f8b0:4003:c02:0:0:0:1a.
Done testing host alt4.aspmx.l.google.com.
Delivery over IPv4 to dns-admin@google.com ok.
Delivery over IPv6 to dns-admin@google.com could not be done.
Done testing email address dns-admin@google.com.
Successful attempt to deliver email for SOA RNAME of google.com (dns-admin.google.com) using dns-admin@google.com.
SOA TTL for google.com OK (86400) - recommended >= 3600.
SOA refresh for google.com too small (7200) - recommended >= 14400.
SOA retry for google.com too small (1800) - recommended >= 3600.
SOA expire for google.com OK (1209600) - recommended >= 604800.
SOA minimum for google.com OK (300) - recommended between 300 and 86400.
Done testing SOA parameters for google.com.
Connectivity
Begin testing connectivity for google.com.
Name server 216.239.38.10 announced by: 15169
Name server 216.239.36.10 announced by: 15169
Name server 216.239.34.10 announced by: 15169
Name server 216.239.32.10 announced by: 15169
Zone announced by ASN: 15169
Zone announced by only one ASN (1).
Zone announced by IPv6 ASN:
Zone announced by only one IPv6 ASN (0).
Done testing connectivity for google.com.
DNSSEC
Begin testing DNSSEC for google.com.
Did not find DS record for google.com at parent.
Servers for google.com have consistent extra processing status.
Did not find DNSKEY record for google.com at child.
No DNSKEY(s) found at child, other tests skipped.
Done testing DNSSEC for google.com.
Test completed for zone google.com.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
can you ping 158.152.1.222 ?

can you ping www.demon.net ?

can you trace route to www.demon.net ?
DCCoolBreezeAuthor Commented:
both pings were successful, and tracert worked as well.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
There is some networking issues, or firewall which is blocking this application whilst you are in BRIDGED MODE.

This must be on the host.
DCCoolBreezeAuthor Commented:
I am using Centos 7 host.  itunes is one of the problems.  What should I do?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
do you have a fixed network LAN socket on this laptop ?

it's just some WiFi chipsets do not work correctly with virtualisation and VMs.
DCCoolBreezeAuthor Commented:
no.  My laptop uses wifi.  i use a toshiba satellite A665-S6050. I have no access to LAN
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
So you have no fixed hard wired connection?

I would try updating the firmware on your network interface and update the network interface if possible.

what is the network interface in the laptop ?

Failing that I would Request Assistance on this question, and see if any other Experts have any other ideas, I believe this is a compatibility issue with the network driver, or network interface in the Host Computer, or host OS firewall or other network related issue, which is interfering with the VMware Virtual Network interfaces.
DCCoolBreezeAuthor Commented:
oh.  sorry.  yes, I do have a LAN connection on my laptop. I will see what I can do about updating my network card firmware.  I will let you know what I happens.  Could it be that Centos is blocking itunes, since itunes is not compatible with linux... perhaps a port is not open that should be open...  but that is automatically opened via windows setup
DCCoolBreezeAuthor Commented:
ah.  i think what you would want me to also do is disable wifi, plug in my LAN and see if that fixes the problem.  If it does, then it is a wifi adapter issue vice a firewall issue.  Is that correct?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
That is correct.
DCCoolBreezeAuthor Commented:
OK.  I connected my laptop to the lan and it worked just fine.  I was able to login to itune without getting the "internet is not connected error".   So what do I need to do to get the wireless access to be able to access itunes.  it is a little inconvenient to have a cable connected to my laptop...   :)
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Okay, this proves the issue is a incompatible WiFi card.

1. Update the firmware on the laptop, paying specific attention to the wireless WiFi interface.

2.  Update the OS network interface driver for the WiFi interface.

This is not the first time, I've seen issues with the WiFi interface, not compatible with VMware Workstation.

You could try VMware Workstation 11.
DCCoolBreezeAuthor Commented:
yes.  I have been using VMWare since their inception   :).   I hated those multiple computers... separate hard drives... to develop software on different platforms, so when VMWare was released, I jumped on it.  All that to say that I have a licensed copy of the latest version of workstation.  :)

I will make sure the firmware of the laptop is updated - specifically the WiFi interface.
I will see what I can do to make sure the latest Centos 7 WiFi interface driver is installed, and let you know
DCCoolBreezeAuthor Commented:
OK.  Just checked the versions of my laptop firmware, OS wireless interface driver - all are the latest versions.  I am also running the latest version of WMWare
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
VMware Workstation 11 ?
DCCoolBreezeAuthor Commented:
yes.  VMware Player 7.x  Workstation 11
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Well I think this is far as we can go, we've proved the issue is with your Hardware Wireless Network Interface or Operating System Driver.

You may want to discuss the issue further with VMware Support.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.