The Apple AirPort extreme had NO problems with this.adding my virtual computers as new, individual, devices right along the actual, physical, devices. WHY IN THE WORLD is the Google/Nest router not seeing a new device (the Win11 virtual computer) on that IP address and simply adding it AS another device.instead of replacing the iMac's IP address? Of course.the port forwarding rule now fails. Instead of adding a new device on the network with the address of 192.168.10.29 it REPLACES the IP address for the iMac changing it from 192.168.10.14 to 192.168.10.29. Within moments of firing up the Virtual Win11 computer the Google/Nest router NOW sees the iMac's IP address as 192.168.10.29. This virtual Windows 11 computer has an IP address of 192.168.10.29 ![]() I then fire up a Parallels Virtual Windows 11 system on the Mac. Once the port forwarding rule is in place.all is well with the world and the application needing that port works perfectly. I then set up port forwarding for a specific port (32678) My main iMac computer has an IP address of 192.168.10.14 ![]() I changed the routers default DHCP settings so the router is at 192.168.10.1 and it dishes out IP address in the range of 192.168.10.10 thru 192.168.10.250.Įverything is working perfectly.no problems.except this ONE: The mesh network has been created successfully. I just retired my Apple AirPort Extreme and replaced it with a Google/Nest Wifi router along with an additional Google/Nest Point.
0 Comments
Leave a Reply. |