Support Questions

Find answers, ask questions, and share your expertise

starting network manager script dispatcher service

Explorer

starting network manager script dispatcher service .pls help to me

duraitulasi@gmail.com (+91 9884099785)

15335-sanboxerrr.png

1 ACCEPTED SOLUTION

Explorer

after some time and the issue showing up from time to time I discovered it was an IP problem . using the virtualbox fixed it because it uses a default different IP . the problem with the IP was caused by some limitations set up in my computer by my company.

View solution in original post

12 REPLIES 12

New Contributor

Same problem with me stuck at this screen for more than half an hour now nothing happening. Please help. Suggest some of the different options i can do and not the typical answers like providing 8 gb of ram etc. Thanks in advance.

New Contributor

I faced the same problem. After installing VB extension pack and re importing image, this issue is solved for me.

New Contributor

What versions of Virtual Box and VB Extension Pack? They don't all work the same. 😉

New Contributor

This behavior exists on both Virtual Box and VMWare instances.

Explorer

did anyone get to a solution? its still happening.

@Ilya Brodetsky Heya, I noticed you got past this issue - mind sharing what you found? Thanks!

Explorer
@Edgar Orendain

working with oracle virtual box fixed it for me. im pretty sure its connected to my env automatically masking the default vmware IPs

Explorer

@Edgar Orendain no I did not get past this issue..

New Contributor

Not a solution to stop the loop but i've found you can still access the sandbox once its got past the 'starting sandbox' step. For me this occurred after the second time I started the sandbox so I already knew the ip

New Contributor

I found the network manager wasn't needed so I deleted the script that initiates it.

Explorer

how did you delete the network manager? thanks

Explorer

after some time and the issue showing up from time to time I discovered it was an IP problem . using the virtualbox fixed it because it uses a default different IP . the problem with the IP was caused by some limitations set up in my computer by my company.

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.