SSH Issues

[zaydancopengaza]

Everything is alright except this SSH issue im stuck on it for the past 2 days i even installed ssh service on indiviual machines also i could ssh into the vagrant provision couldnt find the root cause could you please help may fly :((((

GOAD/vmware/vm/10.1.56.X (5d09c1-goad-vmware) > install
[] Launch providing
[] CWD: /workspace/5d09c1-goad-vmware/provider
[] Running command : vagrant.exe up
Bringing machine 'GOAD-DC01' up with 'vmware_desktop' provider...
Bringing machine 'GOAD-DC02' up with 'vmware_desktop' provider...
Bringing machine 'GOAD-DC03' up with 'vmware_desktop' provider...
Bringing machine 'GOAD-SRV02' up with 'vmware_desktop' provider...
Bringing machine 'GOAD-SRV03' up with 'vmware_desktop' provider...
Bringing machine 'PROVISIONING' up with 'vmware_desktop' provider...
==> GOAD-DC01: Checking if box 'StefanScherer/windows_2019' version '2021.05.15' is up to date...
==> GOAD-DC01: Machine is already running.
==> GOAD-DC02: Checking if box 'StefanScherer/windows_2019' version '2021.05.15' is up to date...
==> GOAD-DC02: Machine is already running.
==> GOAD-DC03: Checking if box 'StefanScherer/windows_2016' version '2017.12.14' is up to date...
==> GOAD-DC03: Machine is already running.
==> GOAD-SRV02: Checking if box 'StefanScherer/windows_2019' version '2021.05.15' is up to date...
==> GOAD-SRV02: Machine is already running.
==> GOAD-SRV03: Checking if box 'StefanScherer/windows_2016' version '2019.02.14' is up to date...
==> GOAD-SRV03: Machine is already running.
==> PROVISIONING: Checking if box 'bento/ubuntu-22.04' version '202401.31.0' is up to date...
==> PROVISIONING: Machine is already running.
[] Prepare jumpbox if needed
[] Launch scp /mnt/c/GOAD/scripts/setup_local_jumpbox.sh -> [email protected]:~/setup.sh
[] CWD: /workspace/5d09c1-goad-vmware
[] Running command : scp -o StrictHostKeyChecking=no -i
/mnt/c/GOAD/workspace/5d09c1-goad-vmware/provider/.vagrant/machines/PROVISIONING/vmware_desktop/private_key
/mnt/c/GOAD/scripts/setup_local_jumpbox.sh [email protected]:~/setup.sh
ssh: connect to host 10.1.56.3 port 22: Connection timed out
scp: Connection closed
[] CWD:
[] Running command : ssh -t -o StrictHostKeyChecking=no -i
/mnt/c/GOAD/workspace/5d09c1-goad-vmware/provider/.vagrant/machines/PROVISIONING/vmware_desktop/private_key
[email protected] "cd ~ && bash setup.sh"
ssh: connect to host 10.1.56.3 port 22: Connection timed out
[] CWD:
[] Running command : ssh -t -o StrictHostKeyChecking=no -i
/mnt/c/GOAD/workspace/5d09c1-goad-vmware/provider/.vagrant/machines/PROVISIONING/vmware_desktop/private_key
[email protected] "cd ~ && mkdir -p ~/GOAD/workspace/5d09c1-goad-vmware"
ssh: connect to host 10.1.56.3 port 22: Connection timed out
[] Launch scp /mnt/c/GOAD/workspace/5d09c1-goad-vmware/instance.json ->
[email protected]:/GOAD/workspace/5d09c1-goad-vmware/instance.json
[] CWD: /workspace/5d09c1-goad-vmware
[] Running command : scp -o StrictHostKeyChecking=no -i
/mnt/c/GOAD/workspace/5d09c1-goad-vmware/provider/.vagrant/machines/PROVISIONING/vmware_desktop/private_key
/mnt/c/GOAD/workspace/5d09c1-goad-vmware/instance.json
[email protected]:/GOAD/workspace/5d09c1-goad-vmware/instance.json
ssh: connect to host 10.1.56.3 port 22: Connection timed out
scp: Connection closed
[] Launch scp /mnt/c/GOAD/workspace/5d09c1-goad-vmware/inventory ->
[email protected]:~/GOAD/workspace/5d09c1-goad-vmware/inventory
[] CWD: /workspace/5d09c1-goad-vmware
[*] Running command : scp -o StrictHostKeyChecking=no -i
/mnt/c/GOAD/workspace/5d09c1-goad-vmware/provider/.vagrant/machines/PROVISIONING/vmware_desktop/private_key
/mnt/c/GOAD/workspace/5d09c1-goad-vmware/inventory [email protected]:~/GOAD/workspace/5d09c1-goad-vmware/inventory

[jonathan-haubrich]

I was having the same issue. I set my network range to 10.0.1.X and for some reason VMware was not assigning my host an ip address. To fix it, I manually assigned an ip to one of my interfaces. I chose the 10.0.1.2/24 for my host with the gateway as 10.0.1.1. After that I could ping the 10.0.1.3 and connect to it on ssh.

I had to run prepare_jumpbox and then provision_lab after ensuring all my VMs were up and then everything started working.

[HamitKURT]

Host OS struggling to take ip address (Windows 11 22631.4317)
I think the issue is related to Windows and/or VMware.
For solution you can create vmnet adapter before starting the installation.

[zaydancopengaza]

it doesnt work tried changing the network a couple of times i have given up on this :(

[sandsoncosta]

I had a lot of problems with Windows11.
Personally, I gave up on setting up this lab on Windows. For some reason, the drivers wouldn't talk to each other during the installation. Something would always time out.
You can install on Linux and then import it again on Windows.
There are always problems with Windows.

I was able to install using Linux without any problems.
I started a linux-live and installed everything via live-usb.
You can start a linux-live-usb, configure virtualbox or vmware, configure all the dependencies and start the lab installation.
Then just start Windows normally and import the vms.
Virtualbox: click on .vbox, create a new network interface and configure the lab's network interface.
VmWare: configure the new network interface, click on .vmx and configure the interface in the vm.