Web and WebWorks Development

[docaholic]

Hey guys, got a question here:

I'm getting this error when I try to deploy my app using the WebWorks SDK:

Error: Cannot connect: Connect to /192.168.190.130:443 timed out. Please check IP address settings for the target. You may have to reboot the target.

 If I try deploying using Ripple, I get the same error message. I've checked the simulator IP address (matches the one i've given), and I've restarted the simulator, still no luck.

Any ideas?

Thanks 

[bnolan001]

Are you deploying it to a tablet or phone simulator?  And what are the command line arguments that you are using?

[docaholic]

I was deploying it to the phone simulator; and don't worry!

I've actually figured out my issue; it was a problem with VMWare

[aditiaa]

Hi please can you help me I am getting the same error timed out while launching the app on playbook

Thanks

[chadtatro]

First, can you ping the IP address from windows command prompt?

[aditiaa]

Can u please explain me in detail what do u mean by  ping the IP address from windows command prompt? as i m new in black berry

Thanks

[RosendoLSL]

I am having the same problem, can you please tell me the steps to fix this?  You mentioned this was on the VMware player but I am not sure how.

I appreciate your help.

Rosendo

[oros]

The time's that I've seen this, a PC reboot fixed it. I've only seen this myself on a physical Dev Alpha, and only if I switch between side-loading, then connect to the device's file system, and then try to go back to side-loading; which likely wouldn't be the case if you're using a simulator though...

[RosendoLSL]

Thanks for the reply, but I have tried restarting thes simulator and the laptop but the result is still the same.  Very frustrating, but don't have a way to test my apps (5) for BB10.  Any feedback is highly appreciated.

[chadtatro]

Are you able to ping the simulator's IP address?

Open a command prompt and type:  Ping <address here>,  example would be "ping 192.168.0.1".  

If it comes back with results then we can eliminate a network issue (or vmware network in this case).  If it can't reach the host, then we know we're dealing with some type of vmware network settings.