I'm using vmware workstation with Windows server 2012 host and Windows server 2008 guests.
I narrowed it down to something with the nat configuration. I normally configure 2 nics, nat (default) and bridged. If I disable the nat adapter my problem goes away. The debug logs go by really fast so I can't really tell when the problem occurs but I'm fairly sure it occurs during port pruning, forwarding, configuring. On Jan 19, 2015 4:04 PM, "Alvaro Miranda Aguilera" <[email protected]> wrote: > hello, > > I have read in the past that some changes in the network on vmware it may > require some network reloads and cause similar issues. > > I don't know what you are using (host/provider/guest_os) so is hard to > elaborate more. > > What I could suggest is, let Vagrant configure a 2nd interface, and from > the host you should able to connect directly to that given IP:port without > nat at all, just be sure to configure/disable the firewall > > > if you want to add an ip over a private network, just is only available to > the host and the guest on the same host: > > https://docs.vagrantup.com/v2/networking/private_network.html > > > if you want to add an ip over a bridge network, that will be available to > host, other guest, and other computer on the network: > > https://docs.vagrantup.com/v2/networking/public_network.html > > Alvaro > > On Sat, Jan 17, 2015 at 8:31 PM, Umair Chagani <[email protected]> > wrote: > >> It's not a vagrant error. It is an error in the app I am testing but it >> happens when I spin up multiple boxes. >> >> For example: >> >> Spin up box 1, deploy my app, while testing another box is spun up, >> application on first box crashes. >> >> I've narrowed it down to the nat configuration that happens before each >> box. The nat configuration that happens causes slight interruptions which >> causes one of our services to crash. >> >> I was hoping to narrow down exactly what was happening so I could provide >> the developers with concrete steps to fix our app. >> >> >> On Jan 17, 2015 12:41 AM, "Alvaro Miranda Aguilera" <[email protected]> >> wrote: >> >>> what error? >>> >>> On Sat, Jan 17, 2015 at 9:05 AM, Umair Chagani <[email protected]> >>> wrote: >>> >>>> I'm seeing a weird error when spinning up machines on the same host. >>>> I'm pretty sure it is a port forwarding problem but I can't isolate it to a >>>> single line in the debug logs. >>>> >>>> -- >>>> 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]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> 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]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> 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]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
