Thank you very much. That worked for me.

I really appreciate your help.

Sent from my iPhone

> On 6 Oct 2015, at 10:44, Alvaro Miranda Aguilera <[email protected]> wrote:
> 
> Hello,
> 
> If the guest is linux, you need to look into how linux will broadcast
> himself into the windows network.
> 
> That usually is done with Samba, and configuration on how to make
> himself known in the workgroup.
> 
> I am not aware of any plugin that will setup that for you, so I think
> you should look into how to do it manually first (on the linux vm) and
> then how to put that in a script.
> 
> Alvaro.
> 
> 
>> On Tue, Oct 6, 2015 at 8:22 AM, Rajiv Jain <[email protected]> 
>> wrote:
>> Hi
>> 
>> I have been using Vagrant for some time and I wanted to find out whether it
>> is possible to set the network name when specifying public network.
>> 
>> I am trying to join the Vagrant guest to the network such that when I log in
>> using Windows, the guest machine name is displayed in the Network section.
>> 
>> Vagrant is hosted on my MacBook Air and I am trying to join the Vagrant
>> guest machine to home network for it to be displayed to the Network section
>> of Windows. I have successfully created a bridge network over wifi. I can
>> however ping over the network to the Vagrant guest and have created a
>> Vagrant guest (DNS Server) and that works perfectly well over the network.
>> All I need to do is somehow display the Vagrant guest as a computer in the
>> Network section in Windows.
>> 
>> Thanks.
>> 
>> --
>> This mailing list is governed under the HashiCorp Community Guidelines -
>> https://www.hashicorp.com/community-guidelines.html. Behavior in violation
>> of those guidelines may result in your removal from this mailing list.
>> 
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Vagrant" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vagrant-up/c121f7e1-d229-46d1-a465-62295573d6d6%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> This mailing list is governed under the HashiCorp Community Guidelines - 
> https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
> those guidelines may result in your removal from this mailing list.
> 
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> --- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Vagrant" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/vagrant-up/iZnK3tI6Ojc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vagrant-up/CAHqq0ez_QCyOc8vqR5g%3Dof-Om0ObtjMsDo6i6L%3Db5CeP8sSmZQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/D0394E54-2A4B-4221-B8C1-0ACC2512A346%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to