@fcwilt yes.

@jcwild I'm not sure how much additional help I can be, but i am also running a genuine BL Touch on a Maestro board. I just went and checked my connections against yours, and your wiring is correct. Also, my bltouch wiring is ~ 24" long, with 1 JST connector in the middle, so i wouldn't think that the wiring itself was too terribly sensitive. I retract this, and after reading what @Phaedrux has been saying, i agree there must be ghosts in the wiring Do you have the means to re-crimp a new one?

Edit:
I've pasted the probe section of my config. Hopefully this will give you a starting point for troubleshooting.

; Z-Probe
M558 P9 C"^zprobe.in" H5 F1500 T8000            ; set Z probe type to bltouch and the dive height + speeds
M950 S0 C"zprobe.mod"                           ; create servo pin 0 for BLTouch
G31 P500 X0 Y-43 Z2.35                          ; set Z probe trigger value, offset and trigger height
M557 X0:117 Y-6:81 S23.4                        ; define mesh grid 

Quality of Life Improvement:
I would suggest setting up a macro for resetting the BLTouch in the event it ever enters an error state. (eg. if you crash the probe on deployment.) Especially when troubleshooting, it'll come in super useful!

M280 P0 S160 I1

@jcwild No problem. Since i'm running nearly the exact setup you're having trouble with, if you need anything specific from me to reference while troubleshooting just let me know!

@jcwild I'm not sure how much additional help I can be, but i am also running a genuine BL Touch on a Maestro board. I just went and checked my connections against yours, and your wiring is correct. Also, my bltouch wiring is ~ 24" long, with 1 JST connector in the middle, so i wouldn't think that the wiring itself was too terribly sensitive. I retract this, and after reading what @Phaedrux has been saying, i agree there must be ghosts in the wiring Do you have the means to re-crimp a new one?

Edit:
I've pasted the probe section of my config. Hopefully this will give you a starting point for troubleshooting.

; Z-Probe
M558 P9 C"^zprobe.in" H5 F1500 T8000            ; set Z probe type to bltouch and the dive height + speeds
M950 S0 C"zprobe.mod"                           ; create servo pin 0 for BLTouch
G31 P500 X0 Y-43 Z2.35                          ; set Z probe trigger value, offset and trigger height
M557 X0:117 Y-6:81 S23.4                        ; define mesh grid 

Quality of Life Improvement:
I would suggest setting up a macro for resetting the BLTouch in the event it ever enters an error state. (eg. if you crash the probe on deployment.) Especially when troubleshooting, it'll come in super useful!

M280 P0 S160 I1

@gnydick that sounds great! I've sent you a DM so we can arrange something.

@dc42 Yes, i've tried explicitly using the "http://" prefix.

The strange part is that yes, i can successfully ping the duet ip address from the VM.

@fcwilt yes.

@phaedrux @gnydick Thanks for replying. I'm trying to reach the ip address directly.

-The ip address of the 3D printer is 192.168.0.10
-The ip address of the VM in question is 192.168.0.47

The VM can successfully browse any other public websites, and can also access several other local docker Web interfaces.

I only have windows 10 VMs right now, but have tried accessing the printer through my iPhone, iPad, Macbook, generic android tablet, and a windows 10 laptop. All were able to connect to 192.168.0.10 successfully.

I have 2 windows 10 VMs, and both were unsuccessful in connecting. I do not have any non-windows VMs to test.

Someone on the Unraid forum suggested i look into manual DNS settings on the board, but i didn't have any luck with changing the network settings (M552, 553, 554)

I'm not sure if anyone else has had this issue, but i cannot access the Duet Maestro WebUI from any browser window on any Windows 10 VM. (tested on 2). }

I've been speaking with those much smarter than me over at the Unraid forums, but wanted to see if i'm missing something from the duet config side.

In short, does anyone know why my WebUI would be reachable by any and all devices except virtual machines? (and how to solve it)

Any direction is really appreciated!

Thanks everyone that gave me direction on this one. I'm running firmware 2.02RC5(RTOS) (2018-11-28b1).

Turns out you were right @ phaedrux. I had my motors AND my endstops backwards, making it appear as though everything was playing nice. I flipped the motors and home code around and it's moving as expected now!

I really appreciate the help!

Thanks, i'll try that after i've checked firmware. I figured the motor direction wasn't an issue because the y axis moves properly. Wouldn't that mean that both the x and y motors are spinning correctly since they're both used for both axis?

@deckingman Thanks for the quick reply! I'll check my firmware (update if necessary) and change that M667 code tonight and report back.