Solved Win 8 using virtual adapter rather than real

I use fixed IPs on my home network, all in the 192.168.1.X range, so was a bit surprised - and concerned - when Teamviewer on a 'connected to' system was reporting a connection from 192.168.216.1. As all machines on the LAN have Teamviewer set to accept only LAN connections, and as 192.168.216.1 did not look like any of my LAN systems, I had to get to the bottom of it.

Running ipconfig /all on the 'connecting' system revealed that 192.168.216.1 was in fact the IP of a VMWare Player virtual Ethernet adapter, so Win 8 was using that rather than the installed Ethernet adapter, address 192.168.1.30.

I'm unsure whether this is a Teamviewer issue, a VMWare issue or a Win 8 one but booting into Win 7, where VMWare Player is also installed, and connecting via Teamviewer to another system on the LAN, the receiving system was correctly reporting the connecting IP as 192.168.1.30. All system are using the same versions of WMWare Player and Teamviewer so I think the finger is probably pointing at Win 8 - but I really ain't sure!

I had something similar, but with a virtual adapter bridged with Hyper-V. It is described as a virtual switch. It is currently disabled.
In recent Windows versions, there are a slew of virtual network adapters, and goodness knows what most of them are there for. Perhaps someone knowledgeable can elucidate...?

This has gone from being 'just one of those things' to being a bit of a problem, as all the while it's using this virtual adapter I can't connect to it with Teamviewer from another LAN system. I can connect from it and then reverse sides but that's not very satisfactory so I need to fix it.

I have never been able to suss how Windows decides which of multiple network adapters it's going to use and it hasn't mattered much before, but now it does. Anyone know how to tell Win 8 which adapter to use? I don't want to disable the VMWare one as I use the VMs a lot.

Is this similar to my problem BJB? on my post basically saying theres no fix for the adapters until they bring a new fix out because im getting limited connection all the time on windows 8 but I know very little about this stuff lol, good luck getting sorted.

I've posted in your thread

BJB said:

This has gone from being 'just one of those things' to being a bit of a problem, as all the while it's using this virtual adapter I can't connect to it with Teamviewer from another LAN system. I can connect from it and then reverse sides but that's not very satisfactory so I need to fix it.

I have never been able to suss how Windows decides which of multiple network adapters it's going to use and it hasn't mattered much before, but now it does. Anyone know how to tell Win 8 which adapter to use? I don't want to disable the VMWare one as I use the VMs a lot.

Click to expand...

This has been going on with certain VM's and VPN's like Hamachi for quite awhile now.

Windows can't seem to decide which connection to use when there are multiple network interfaces and it's been going on since at least Windows 7.

You might try using a different version of VM, or maybe messing with the metric or MTU would have an effect.

chev65 said:

You might try using a different version of VM, or maybe messing with the metric or MTU would have an effect.

Click to expand...

I haven't updated VMWare recently but did upgrade to TeamViewer 8 during last week so next step will be to try reverting to TV 7. I am seeing some really weird things though, like the machine receiving the TeamViewer connection always reports it as coming from the virtual ethernet adapter even when the connecting machine is using its wireless adapter. Figure that!

BJB said:

chev65 said:

You might try using a different version of VM, or maybe messing with the metric or MTU would have an effect.

Click to expand...

I haven't updated VMWare recently but did upgrade to TeamViewer 8 during last week so next step will be to try reverting to TV 7. I am seeing some really weird things though, like the machine receiving the TeamViewer connection always reports it as coming from the virtual ethernet adapter even when the connecting machine is using its wireless adapter. Figure that!

Click to expand...

What really gets me is that on multiple occasions people can't even obtain a connection to the internet unless the offending VM or VPN is disabled completely. I haven't taken the time to find a better cure for this problem.

It may also help to update the driver for which ever connection you are using.

OK, it was the upgrade to Teamviewer 8 that was the problem and all systems are now connecting normally again, though machines receiving a connection from the Win 8 machine are still reporting the connection as being from its virtual adapter, which says there are still bugs in there somewhere.