I have followed the steps provided in the following link to configure Pocket PC to Connect Internet: http://blog.rebex.net/news/archive/2009/01/28/howto-configuring-network-in-windows-mobile-pocketpc-device-emulator.aspx. Every thing Work fine , but when i tries to connect to internet it shows some error as follows:
Can any one tell me what , where it went wrong.... I followed the ablive mentioned steps in the URL.
http://msdn.microsoft.com/en-us/library/aa289160(v=vs.71).aspx
scan on
Configuring the Emulator to Connect to the Internet
Related
I downloaded the docker/awesome-compose flask-redis application using "Open in Docker Dev Environments" button, and when I started the app, I attached the container to VSCode and then tried to access the webpage,
but there was an error page saying "localhost didn’t send any data" with error code ERR_EMPTY_RESPONSE.
I don't know what happened.
Code is here: https://github.com/docker/awesome-compose/tree/master/flask-redis
I wanted
This webpage has been viewed 1 time(s)
to show up.
I tried methods shown in answers to similar question but nothing worked.
I didn't know what to try
Update: Now It changed to "localhost refused to connect"
I have pushed a Phoenix app to Heroku and it is running fine, apart from connecting to a channel from iOS.
Channels over the browser work as expected.
In iOS I am using PhoenixWebSocket, and in dev env, connecting to the local Phoenix app works as expected.
The problem I am getting is when I point the web socket url to the Heroku app I get the following error:
Error Domain=WebSocket Code=301 "Invalid HTTP upgrade" UserInfo={NSLocalizedDescription=Invalid HTTP upgrade}
Looking around for the error message earlier today, I found a post from Chris McCord, I think it was, saying that this error message is a result of the server refusing to upgrade the request.
However, I've looked around Heroku and found that; Websockets functionality is supported for all applications.
So I'm confused as to whether my problem is on the iOS side, or the Heroku side.
I have pushed Chris's example chat application to Heroku, and tried to connect with the demo app that comes with PhoenixWebSocket, but get the same error.
Has anyone else managed to get web socket requests working between iOS and Heroku hosting a Phoenix app?
Would anyone know if there is something differently I need to do with the request in iOS before trying to join the channel? Or, maybe there is something with the Heroku setup relating to web sockets that I've missed?
The url for the request in iOS:
let url = NSURL(string: "ws://app-name-32793.heroku.com/socket/websocket")!
Many thanks to anyone that can help, and please let me know if there's anything else I can supply to help.
Paul
I know this is old but one possible issue is you may need to connect via https/wss. So either
let url = NSURL(string: "wss://app-name-32793.heroku.com/socket/websocket")!
or:
let socket = Socket(domainAndPort: "app-name-32793.heroku.com", path: "socket", transport: "websocket", prot: "https", params: [])
Since last 4 days I am not able to play any video on youtube. It shows an error "An Error Occurered. Please Try again Later" on laptop but works fine on mobile. Both have same Internet connection
I did following things:
1. Updated my Google Chrome
2. Deleted all temp, cache and cookies
3. used CCLeaner to clean whatever is left out.
4. Checked and Updated Adobe Flash (anyway it was updated)
5. Some other trouble shooting steps were also tried.
6. Tried changing video quality (downgraded)
7. Tried changing DNS of IP4
Nothing seems to be working.. rest everything is working fine except Youtube. Please do help me.. Thanks in advance :)
look at this links: YouTube Help Forum and CCM- an error occurred please try again later.I would try some of the suggestions from those forums. But if it doesn't help try using different browser.
Try opening www.youtube.com in a different browser, like Mozilla firefox. If it doesn't help, check if www.youtube.com is listed in the blocked website list of windows firewall. To do this, go to C:/WINDOWS/SYSTEM32/DRIVERS/ETC/HOSTS . It's a text file which contains entries of blocked websites on your local host.
If you find such a entry as 127.0.0.1 www.youtube.com youtube.com ; cut it, save the file and try accessing youtube now.
Hope this helps.
I'm having some issues with direct update on iOS.
Following scenario describes my problem.
Add the code snippet below to main.js
Enabled worklightSettings in application-descriptor.xml
Run on Worklight Development Server
Open project in Xcode via eclipse
Run
Make a change and re-deploy
Verify Direct Update is received
Uninstall app
Obtain new IP (in my case by restarting my macbook the next day)
Open project in Xcode via eclipse
Run
Open myapp settings via Settings.app and enable Custom Server URL. The URL is pointing to the old IP.
Enable Custom Server URL and enter the correct IP
Open app
Direct Update is not received
Code snippet:
function wlCommonInit(){
WL.Client.connect({
onSuccess: onConnectSuccess,
onFailure: onConnectFailure
});
}
function onConnectSuccess() {
WL.Logger.debug("Connect success.");
}
function onConnectFailure() {
WL.Logger.debug("Connect failed.");
}
EDIT
Try following scenario:
create a new app from scratch and deploy it on your iPad
verify the custom server URL and test direct update: all is working fine (OK)
update the ip on your development machine
remove the app from the device and reinstall it
verify the custom server URL: the old IP is present (NOK)
start the app with the use custom server url unchecked => 'connect success'
start the app with the use custom server url checked (don't change ip) => 'connect success'
try to access the app in your browser with this ip => doesn't work
change the ip and remove the last front slash from the custom server url
start the app with the new correct IP (which works in the browser) => 'connect success'
change the ip back to the incorrect IP, add the slash and retry => NO 'connect success'
The exact same custom server URL which worked before fails now. When I try a random IP address I also don't get the 'connect success'.
EDIT
result of ifconfig:
When you add a project in Worklight Studio, the following warning message is outputted:
FWLPL0010W: The current server configuration is set to "localhost".
Therefore the Worklight build uses the primary IP address of this
computer (192.168.1.100) instead. It is recommended to set the server
configuration to use the fully qualified hostname or IP address of
this computer. To configure the setting, in the "Servers" view
double-click the Worklight Development Server entry and edit the "Host
name" field.
In the comments you say the wrong IP address is used, so try and change the default IP address that Worklight Studio selects by following the above instructions. The address you will set will be used as the server address, as well as be used in the application (the address that you see in the app settings page).
To make sure the settings page is fully 'refreshed':
Delete the app from the device/simulator
When opening the project in Xcode, first select Clean and then Run (because Xcode tends to keep the Settings.bundle file cached)
I'm having a problem with getting the tutorial to work on the device
it works fine in the simulator, but when I try to run it on the device it doesn't work.
I put some logs and it seems to come from the login function
===JASONROGERS292C 2480 supAdmin s3pAdmin
[0.0] TAC:TAI.handleRegRsp : ALREADY_REGISTERED
[0.0] TAC:TAI.handleRegRsp : (ALREADY_REGISTERED), registered entry found:{{APN=,id=2,state=CLOSED,waf=WAF[0.0] _3GPP,keepAlive=300,IP=0.0.0.0,dnsSrv=0.0.0.0}}
[0.0] [TMM.TunnelAllocator]:runNotReadyListeners: registered listeners found
[0.0] TAC:TAI.handleListenerDeRegRsp: not existent tunnel in TAC, tid=2
[0.0] SIM cache not loaded
has anybody got an idea what I forgot to do when running the code on a device?
Cheers
Jason
edit:
a couple of links towards what I'm doing (I can post all the code people want but its the standard generated code form SUP, which mean a lot of code lol)
The tutorial
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01214.0200/doc/html/title.html
the zip to the already done tutorial :
http://www.sdn.sap.com/irj/bpx/index?rid=/webcontent/uuid/40ea4956-b95c-2e10-11b3-e68c73b2280e
Solution:
I was missing a couple of things:
1) Specify that the app should use Wifi
SUP101DB.getSynchronizationProfile().setString("transport", "WIFI");
2) Check that the DNS: in my case the server was local to my windows (through parallels) so I had to specify the ip and not the namespace
getSynchronizationProfile().setServerName("10.50.30.108");//"JASONSERVER");
I downloaded the SUP 101 - BlackBerry Project and checked the sources.
It does not contain networking code in the form a usual BB app would do.
However I see the SUP101.SUP101DB class has the following method:
private static String getSyncTransportSuffix() {
com.sybase.persistence.ConnectionProfile syncProfile =
getSynchronizationProfile();
return com.sybase.afx.util.NetworkUtil.getTransportUrlSuffix(syncProfile);
}
So the code uses com.sybase.afx.util.NetworkUtil to get url suffix. By appending such suffix to a url we say to the underlaying BB API what network transport to use. Unfortunatelly sources do not contain com.sybase.afx.util.NetworkUtil to look how exactly it works.
I should say that even with native Java BB development detecting a proper network transport may turn to be a very tricky part. OS 5+ provides a new networking API that is much better, but for the older OS it is hard. This SUP project is built with BlackBerry JRE 4.6.1, so it can not use new OS 5+ networking API. Who knows maybe SUP simply fails to detect proper network transport?
Any way, just a few ideas to try:
check for APN settings on the device, sometimes they have to be populated in order to use Direct TCP transport (it depends on wireless provider requirements). APN name/pass are wireless provider specific. Usually googling allows to find proper APN settings for a provider.
if your device has WiFi try enabling it. SUP should be smart enough to prefer WiFi if available. In this case I assume networking should have no issues.