Closed AritzaSm closed 3 years ago
I have seen this a couple of times on a Windows laptop (my main workstation). I've not seen it on macOS or Linux. It is almost like node1 can't see the DNS, even though it is there, and node2 can see it. I figure it must be some silly eccentricity of VirtualBox on Windows.
I do have a workaround for this.
1) Start up DNS. 2) Start node2. 3) Start node1. 4) While node1 is doing the OS prerequisites, stop and start the DNS node (vagrant halt, then vagrant up). That's not a rebuild. Just a restart.
If I see this issue you've reported, that seems to work for me. Let me know how you get on.
It was really simple, Thanks. It worked after restarting dns node during the the OS prereq. Strange things happnes on windows.
Thank you for this awesome work!
Great news. Glad it worked for you!
Fixed worked for me also - Windows 11 - thank you Tim.
Tim - This fix (dns node (vagrant halt, then vagrant up) did work for me on win 11 and virtualbox 7, but, after numerous retries and what finally worked for me was bringing up the dns node almost when grid software extraction step was launched... thank you !
DNS up un running Node2 un un running Node1 grid configuration fails with: