Prior to installing Windows 10 on my Mid-2014 15" Retina MacBook Pro, I was able to share the screen over a Thunderbolt connection (not an ethernet adapter). It was lightning fast. However, I cannot seem to get this to work in Windows 10 on that same MacBook Pro.
Has anybody had any success getting this to work? If so, how?
Thanks,
Shawn
MacBook Pro Retina
If the same physical connection allows IP over the bridge, when both machines are in macOS, but not when either of them is in W10, then the lack of Bridge is a driver issue related to W10.
Whether it is an Apple--provided W10 driver or Windows WHQL driver, we can check that in Windows Device Manager and ascertain that.
Pinged the old MacBook Pro from the new MacBook Pro:
ping -c 3 192.168.2.2
PING 192.168.2.2 (192.168.2.2): 56 data bytes
64 bytes from 192.168.2.2: icmp_seq=0 ttl=64 time=0.460 ms
64 bytes from 192.168.2.2: icmp_seq=1 ttl=64 time=0.528 ms
64 bytes from 192.168.2.2: icmp_seq=2 ttl=64 time=0.622 ms
--- 192.168.2.2 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.460/0.537/0.622/0.066 ms
Pinged the new MacBook Pro from the old MacBook Pro:
ping -c 3 192.168.2.1
PING 192.168.2.1 (192.168.2.1): 56 data bytes
64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=0.258 ms
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.412 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.666 ms
--- 192.168.2.1 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.258/0.445/0.666/0.168 ms
HotHead wrote:
Pinged the old MacBook Pro from the new MacBook Pro:
ping -c 3 192.168.2.2
PING 192.168.2.2 (192.168.2.2): 56 data bytes
64 bytes from 192.168.2.2: icmp_seq=0 ttl=64 time=0.460 ms
64 bytes from 192.168.2.2: icmp_seq=1 ttl=64 time=0.528 ms
64 bytes from 192.168.2.2: icmp_seq=2 ttl=64 time=0.622 ms
--- 192.168.2.2 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.460/0.537/0.622/0.066 ms
Pinged the new MacBook Pro from the old MacBook Pro:
ping -c 3 192.168.2.1
PING 192.168.2.1 (192.168.2.1): 56 data bytes
64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=0.258 ms
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.412 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.666 ms
--- 192.168.2.1 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.258/0.445/0.666/0.168 ms
If you truly want to test the Bridge connection, you should disable all other Network interfaces.
I've given that a shot, but nothing changes. Just so you know, Thunderbolt does appear under System devices in the Device Manager on Windows, and is configured to use the Apple-supplied Bootcamp drivers.
I've wasted far too much valuable time on this, and it's likely an issue with the driver Apple provides for Bootcamp. So, although it's a bit laggy, I'm going to stick with the thunderbolt to gigabit ethernet adapter for now. Hopefully, Apple will eventually update their drivers (preferably before I get rid of the old MacBook Pro).
Thank you for the help.
If you boot the 2018 Mac in Target Disk Mode (Use target disk mode to move files to another computer - Apple Support) can you see the storage on your 2014 Mac? Were any recent Security updates applied to either of the Macs?
Both Macs were running the latest supported MacOS X software (10.14.5) prior to installing Bootcamp and Windows 10 Pro. No additional software or updates have been installed on the MacBook Pro running Windows. Target disk mode works just fine.
Does TDM work in both directions? I will assume you are trying an IP connection when both Macs are in Mojave.
If you are in System Preferences on either machine, do you see the Thunderbolt Bridge?
Part 1...
My setup
2013 rMBP with W10 installed (on macOS Sierra.6).
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 72:00:00:7d:a3:10
inet6 fe80::1c9c:1b89:2054:dd33%bridge0 prefixlen 64 secured scopeid 0x9
inet 169.254.15.174 netmask 0xffff0000 broadcast 169.254.255.255
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 5 priority 0 path cost 0
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 6 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
2018 Mini (Mojave.4 connected via USBc-to-TB2 adapter to the 2013 rMBP.
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 3a:00:28:18:6f:01
inet6 fe80::1c88:38ed:a72:41fb%bridge0 prefixlen 64 secured scopeid 0x12
inet 169.254.58.44 netmask 0xffff0000 broadcast 169.254.255.255
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 14 priority 0 path cost 0
member: en3 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 15 priority 0 path cost 0
member: en4 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 16 priority 0 path cost 0
member: en5 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 17 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
Part 2...
and (after the first packet is lost to bring up the bridge...)
ping -c 3 169.254.58.44
PING 169.254.58.44 (169.254.58.44): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 169.254.58.44: icmp_seq=1 ttl=255 time=0.536 ms
64 bytes from 169.254.58.44: icmp_seq=2 ttl=255 time=0.675 ms
--- 169.254.58.44 ping statistics ---
3 packets transmitted, 2 packets received, 33.3% packet loss
round-trip min/avg/max/stddev = 0.536/0.606/0.675/0.070 ms
the connection works properly...
ping -c 10 169.254.58.44
PING 169.254.58.44 (169.254.58.44): 56 data bytes
64 bytes from 169.254.58.44: icmp_seq=0 ttl=255 time=0.440 ms
64 bytes from 169.254.58.44: icmp_seq=1 ttl=255 time=0.675 ms
64 bytes from 169.254.58.44: icmp_seq=2 ttl=255 time=0.734 ms
64 bytes from 169.254.58.44: icmp_seq=3 ttl=255 time=0.670 ms
64 bytes from 169.254.58.44: icmp_seq=4 ttl=255 time=0.681 ms
64 bytes from 169.254.58.44: icmp_seq=5 ttl=255 time=0.661 ms
64 bytes from 169.254.58.44: icmp_seq=6 ttl=255 time=0.669 ms
64 bytes from 169.254.58.44: icmp_seq=7 ttl=255 time=0.683 ms
64 bytes from 169.254.58.44: icmp_seq=8 ttl=255 time=0.475 ms
64 bytes from 169.254.58.44: icmp_seq=9 ttl=255 time=0.414 ms
--- 169.254.58.44 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.414/0.610/0.734/0.112 ms
Can you run a similar test?
Sorry it took so long to get back to you. I returned the 2018 MacBook Pro and picked up a 2019 15-inch MacBook Pro instead. Still having the same problem though.
Here's the bridge config from the new MacBook Pro:
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 1a:00:18:22:46:01
inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255
inet6 fe80::1800:18ff:fe22:4601%bridge0 prefixlen 64 scopeid 0x15
inet 169.254.95.147 netmask 0xffff0000 broadcast 169.254.255.255
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 17 priority 0 path cost 0
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 18 priority 0 path cost 0
member: en3 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 19 priority 0 path cost 0
member: en4 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 20 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
Here's the bridge config from the old MacBook Pro:
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 72:00:06:b6:e3:d0
inet6 fe80::1c17:9d4:cd34:2fff%bridge0 prefixlen 64 secured scopeid 0xb
inet 192.168.2.2 netmask 0xffffff00 broadcast 192.168.2.255
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 7 priority 0 path cost 0
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 8 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
Everything is working just fine, so long as both Macs are booted into their native operating systems (Mojave, version 10.14.5). When I boot my older MacBook Pro into Windows 10, no bridge is detected.
Here's the config:
Windows IP Configuration
Host Name . . . . . . . . . . . . : WINDOWS-10-PRO
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 0C-4D-E9-BC-E6-27
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wi-Fi 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11ac Network Adapter #2
Physical Address. . . . . . . . . : 6C-40-08-B8-E9-D8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 6E-40-08-B8-E9-D8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 6C-40-08-B8-E9-D9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
What is the device at the other end of the Thunderbolt cable?
It’s a 2018 MacBook Pro.
What type of USBc-to-TB2 adapter are you using? Is it different between now and when it worked?
Excellent.
I'm using an Apple Thunderbolt 3 (USB-C) to Thunderbolt 2 Adapter and an Apple Thunderbolt 2 cable. The connection works as expected when I'm booted into Mojave 10.14.5. I haven't changed anything other than partitioning the drive and using Bootcamp to install of Windows 10 Pro from scratch (which went perfectly smooth).
TCP/IP over Thunderbolt on Windows 10 in Bootcamp