Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hyperv-iso: Waiting for WinRM to become available #16

Open
Makru opened this issue Jul 5, 2018 · 1 comment
Open

hyperv-iso: Waiting for WinRM to become available #16

Makru opened this issue Jul 5, 2018 · 1 comment

Comments

@Makru
Copy link

@Makru Makru commented Jul 5, 2018

Hello,

i tried the hyperv-windows-2016-serverstandard-amd64.json, adapted the variables to my enviroment, changed the ports in the powershell files to 5986 and added:
"winrm_use_ssl": true,
"winrm_insecure": true,

The result is "==> hyperv-iso: Waiting for WinRM to become available" with that error in the Logfile:

[ERROR] WinRM connection err: unknown error Post https://169.254.171.97:5986/wsman: dial tcp 169.254.171.97:5986: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

The Host is Hyper-V host is Windows2012R2.
What could be the problem?
Many thanks in advance.

Regards Mathias

@andrewbbrown

This comment has been minimized.

Copy link

@andrewbbrown andrewbbrown commented Aug 18, 2018

@Makru - If you're getting an IP address that starts with 169.254, it means that your virtual machine that was just created has been configured to use DHCP (get an ip address from the DHCP server on the network ) and is not getting any ip address from the network. I had this issue earlier and quickly found that my issue was that I attached the VM to a network that did not have a DHCP server... once I changed the network to attach the VM to, choosing one that was internet accessible, it worked just fine. (another idea after you fix your network - make sure you're using a consistent username/password for winrm, since you'll get the same error message but a different message in the logfile)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.