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

Vagrant RDP Issue #3973

Closed
cjbush opened this Issue Jun 4, 2014 · 3 comments

Comments

Projects
None yet
3 participants
@cjbush

cjbush commented Jun 4, 2014

As of 1.6.3, seem to have the following issue when running vagrant RDP on a Windows host for a Windows guest:

==> default: Detecting RDP info...
default: Address: 127.0.0.1:2200
default: Username: Administrator
==> default: Vagrant will now launch your RDP client with the connection parameters
==> default: above. If the connection fails, verify that the information above is
==> default: correct. Additionally, make sure the RDP server is configured and
==> default: running in the guest machine (it is disabled by default on Windows).
==> default: Also, verify that the firewall is open to allow RDP connections.
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/hosts/windows/cap/rdp.rb:24:in block (2 levels) in rdp_client': private methodputs' c
alled for nil:NilClass (NoMethodError)
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/hosts/windows/cap/rdp.rb:23:in each' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/hosts/windows/cap/rdp.rb:23:inblock in rdp_client'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/hosts/windows/cap/rdp.rb:22:in open' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/hosts/windows/cap/rdp.rb:22:inopen'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/hosts/windows/cap/rdp.rb:22:in rdp_client' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/capability_host.rb:111:incall'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/capability_host.rb:111:in capability' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/commands/rdp/command.rb:50:inblock in execute'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/plugin/v2/command.rb:226:in block in with_target_vms' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/plugin/v2/command.rb:220:ineach'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/plugin/v2/command.rb:220:in with_target_vms' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/commands/rdp/command.rb:33:inexecute'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/cli.rb:42:in execute' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/environment.rb:252:incli'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.6.3/bin/vagrant:166:in `

'

@mitchellh

This comment has been minimized.

Show comment
Hide comment
@mitchellh

mitchellh Jun 4, 2014

Member

Fixed in git, will be part of the next release .Sorry about that. As a workaround you can use 1.6.2

Member

mitchellh commented Jun 4, 2014

Fixed in git, will be part of the next release .Sorry about that. As a workaround you can use 1.6.2

@mitchellh mitchellh closed this Jun 4, 2014

@cjbush

This comment has been minimized.

Show comment
Hide comment
@cjbush

cjbush Jun 4, 2014

We were having other issues with provisioning with 1.6.2 that were fixed in 1.6.3. In case anyone else who cares is reading this, our workaround for now is to just manually connect with the RDP client. Thanks Mitchell!

cjbush commented Jun 4, 2014

We were having other issues with provisioning with 1.6.2 that were fixed in 1.6.3. In case anyone else who cares is reading this, our workaround for now is to just manually connect with the RDP client. Thanks Mitchell!

@andmos

This comment has been minimized.

Show comment
Hide comment
@andmos

andmos Jul 31, 2014

Thanks for this. Hope 1.6.4 comes soon :)

andmos commented Jul 31, 2014

Thanks for this. Hope 1.6.4 comes soon :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment