New F550 - Problem registering with the Wookong Assistant software

[brownmonkey]

Hi - Have just completed the build of my new F550 with WKM. Have installed the Driver and Wookong Assistant Software (on 2 different PCs - one Vista, one XP). The Wookong Assistant Software launches on both & seems to recognise the WKM as it closes the splash screen & displays a 'Sign In' dialog.

I haven't registered with DJI previously, so I've been trying to register a new account. Each time I click the 'Register' button, I get prompted to enter my details (email & set a password, etc), which I do & click 'Register' again, after about 5 seconds I get a dialog box pop up called 'timeout' which says; 'The network is abnormal, check the network status.'. Have tried all usual troubleshooting steps (rebooting, trying on a different PC, etc) to no avail.

Is there a problem with registering on the DJI network at present - is there someway of checking, or getting someone else to verify if I'm doing something wrong?


I just want to get my F550 flying - arghhhH!!!
Thanks!

 

[Bella7821]

Mine too would not register, but I've been flying mine for almost 2 weeks.
I can't plug it i as much as I like to, my Fiance was getting tired of the loud beeps whenever I power up the F550 to the computer

 

[Elliott000]

My wkm has been registered for a couple weeks, but i just installed the software and had to sign in again on my new laptop.... all works fine. My fiance just shakes her head everytime i plug in lol, I just spent an hour setting up my trex 5503gx with new software lol, At least i have my own portable programming station now and she can mess around on the PC

 

[brownmonkey]

So, I've managed to work around the issue - it seems to be something to do with my ComCast cable service.. I plugged my laptop into the able modem & that didn't help, so I took it to work & connected via our public wifi (which is behind a firewall) & was then able to register & login without a problem.

Just need to work out how to get it working on my home network now (as bringing the 550 into my office isn't really an option!), but at least I know where the issue lies now.

Thanks to all for advice & help!

 

[brownmonkey]

PS: Although at least using it at work would stop the disapproving head shakes I get from my wife at home (is that a universal response from our hobby intolerant better halves? ;-)

 

[kloner]

mine suddenly came up too. i hit cancel and the software still worked. should we let them know

 

[Andjons]

Have you managed to resolve this? I am having just this problem, and until I can regsiter and get the software working, I cannot configure the copter, and so I cannot bloody fly it!

 

[brownmonkey]

Not 'resolve', no - but I have found a workaround. It doesn't work via my Comcast network, but it works fine on my mobile network from Verizon, so I've been sing that instead whenever I need to configure my WKM. I'm assuming the port that the DJI software uses is blocked by my ISP, but as I'm moving in a month, I haven't bothered to find out which one & complain to Comcast (usually an excerise in futility!).

What ISP are you using? It may be worth trying from a friends house to see of that works..

 

[Andjons]

That is a big pain in the backside, isn't it?! I use Virgin Media.

 

[quadcopters]

This sounds like a firewall issue with your Home pc's or the way your network is configured.
I am on Both Virgin media and Sky broadband which is BT and no problem on either .
Also I have registered many WKM's and Nazas from here and only once had a problem which was the DJI server .
I would suggest disable any firewalls and try it , then once registered switch it back on again hopefully this will cure it .

Geoff - Quadcopters Uk

 

[Andjons]

Thank you everyone. I have now got it working. I spoke to BVirgin, and they said it would be a problem at the DJI end. DJI e,ialed me and said I should try to use a VPN(US) (?!). In the end, I turned off every firewall and blocker that I could find, and then some time this morning as I was idly entering my registration details - for about the 100th time - I got the message "registration successful..." Not sure if it was because I turned off all the protection, or what, but neigh mind. I'm flying (and breaking propellers)!

 

[Muttley1971]

Getting a bit annoyed at the NAZA assistant keep popping up the network is abnormal box I attached a packet sniffer to see what was going on. What happens is that the assistant program tries to connect to an IP address in China (113.105.65.180) on port 8080 but the connection gets rejected because the server is either off / firewalled or IP restrictions are in place to disallow connections?! WTF.

 

[brownmonkey]

Thanks chaps - I've decided to persist and try and get to the bottom of this, as it's annoying to keep firing up my MiFi router every time I want to connect! For info - my home network configuration is Wifi to an Apple Time Capsule router, connected to a Motorola Cable modem - my ISP is Comcast / Xfinity from Wilmington, Delaware.

- I've tried connecting my laptop directly via ethernet into the cable modem (to eliminate the question of the home network configuration) - from here I can access the internet OK, however the WKM software still doesn't work.
- I can see that the software is trying to connect to the IP address: 113.105.65.180 on port 8080 (pretty standard) using the 'netstat -aon' command - I've looked up the IP address & although it's not registered explicitly in DJIs name, it's in the right physical location in China, so I'm confident this is the correct address & port).
- You cannot ping the IP address (as ping only uses port 80 & it appears that is not open on the server (I've verified this from 3 different networks) - so I am using the command 'telnet 113.105.65.180 8080' to force telnet to connect on port 8080 (telnet isn't running on that port, so I am not expecting to complete a telnet connection, but you can tell from the prompt you receive / don't receive whether the port is open or not).
- Telneting to the IP address & port works from my Verizon Mifi device, likewise from my employers office network, but will not connect from my home Comcast network (even plugged in directly to the cable modem).
- I've logged a ticket with Comcast - this has now been passed to their Level 2 team, who are due to get back to me (hopefully with an answer!) in 1-2 days.

I can't believe that this is a Comcast-wide issue, nor a Virgin Media-wide issue, given the large size of their respective customer bases - there would be more people complaining about this I think! However - it seems to me that there is a routing issue external of my home network which is preventing me from communicating with the DJI servers (possibly a corrupt routing table since it's not affecting everyone - if if were a firewall either in the Comcast network or beyond, I'd expect more people to be affected?).

I will keep this thread posted as & when I make any progress with them, in the meantime any further troubleshooting suggestions gratefully received!


Thanks,
Simon

 

[kloner]

not working from an att server here in cali either, annoying

how can you make something fly so good but the security be so weak. It's been going on for months

 

[Tahoe Ed]

Works on my ATT wifi hot spot using a Sierra Wireless modem.

 

[BorisS]

Hi Simon ICMP/ Network ping is port independent try pinging your machines in your home network and you will get a ping response even if your port 80 isn't open, thus having a service running.

The only work around that could work for you at moment if your ISP doesn't change anything, is using a ssh tunnel. For example if you have a linux/unix/os2/ machine in your office or somewhere else that you can access via ssh, you can create a ssh tunnel. Letting your machine listen on the DJI ip/host port 8080 with a putty client for example ( port 8080 not sure if its it, but you checked it via netstat) and also tell the tunnel hosting machine in your office to forward connections to the external DJI server.

The question is only if the DJI client is resolving or connecting directly to an IP. If its resolving an domain for example you can help your self locally on your machine by changing your localhost file that the DJI domain gets rerouted to your local machine with the open ssh client port hosting the tunnel for. If its connecting to an IP i am not sure has been a long time since I was dealing with networking stuff.

http://chamibuddhika.wordpress.com/2012/03/21/ssh-tunnelling-explained/

View attachment 3632

Boris

 

[brownmonkey]

Thanks Boris - I understand, but would rather understand (& fix!) the root cause, rather than tunnel via a proxy / alternate host (also, not an option for me as my employers network - a bank - is locked down for remote inbound access inbound!). I have a workaround, for me, in that I can use my Verizon Mifi router when I need to (4G LTE) - but it's annoying to power that up & switch my laptops Wifi over just to use the WKM software & I don't like it when things don't work properly.

I used a packet analyser to look at the trace & the application is going explicitly to an IP address, not via a DNS name.

It's also been a few years for me (I used to be a LAN engineer / architect - but it was in the token ring / early days of widespread ethernet adoption, so I'm the first to admit how rusty I am!!) - but I'm quite positive the issue is external to my home network - I suspect a corrupt routing table, as a tracert transcends 25 routers within the Comcast network before dying (i.e.: I can see it doesn't even get routed to the destination servers ISP), but don't have the access within my ISP to troubleshoot any further.

To be honest, I'm not that confident my ISP will care enough to diagnose the issue, as it's only one specific subnet that I seem to be having issues with - but I'm trying to confirm it, as it seems there might be other sporadic instances of a similar nature.

Any other ideas of things to check while I wait for the ISP to come back to me?


Thanks!
Simon

 

[Muttley1971]

This is just really weird, I have two broadband lines at home, 1 BT business and 1 BT consumer, if I check from home port 8080 on 113.105.65.180 is filtered and the connection gets dropped. However, I've also got some BSD and Linux servers in a UK data centre and from those I can get to the port no problem?!

From home BB:

PORT STATE SERVICE
8080/tcp filtered http-proxy

From server in UK IDC:

PORT STATE SERVICE
8080/tcp open http-proxy

Netcat to the port confirms it's open:

[root@localhost html]# nc 113.105.65.180 8080
HEAD / HTTP/1.1
HTTP/1.1 400 Bad Request
Date: Mon, 02 Apr 2012 09:53:08 GMT
Server: Apache/2.0.63 (Win32) PHP/5.2.14
Connection: close
Content-Type: text/html; charset=iso-8859-1


Also, ICMP gets dropped from both places after the packets get to 119.145.40.29 so even if the host is up you wouldn't be able to ping it.

As brownmonkey says, the client doesn't do a DNS lookup, it would appear that the IP address is hard coded in the binary so messing around with the hosts file isn't going to help.

 

[brownmonkey]

Hmm - ICMP from my home network also gets as far as the same IP range - albeit to 119.145.40.29. This subnet range is evidently owned by China Telecom, but as you can see from the trace route below, it gets into the China telecom network some 10 hops earlier @ 202.97.49.117 (note I've removed my own IP address for privacy);

Traceroute has started…


traceroute to 113.105.65.180 (113.105.65.180), 64 hops max, 72 byte packets
1 10.0.1.1 (10.0.1.1) 4.508 ms 0.896 ms 0.860 ms
2 c-68-80-168-1.hsd1.nj.comcast.net (x.x.x.x) 33.776 ms 21.485 ms 19.947 ms
3 te-1-2-ur02.limestonedr.de.panjde.comcast.net (68.86.193.177) 8.048 ms 7.753 ms 9.903 ms
4 te-9-1-ur01.limestonedr.de.panjde.comcast.net (68.85.35.33) 9.763 ms 8.694 ms 9.693 ms
5 te-3-8-ar01.coatesville.pa.panjde.comcast.net (68.86.153.230) 10.243 ms 10.012 ms 9.192 ms
6 te-3-1-ar02.newcastle.de.panjde.comcast.net (68.85.34.237) 10.687 ms 10.393 ms 12.276 ms
7 te-0-0-0-5-ar01.newcastle.de.panjde.comcast.net (68.85.159.193) 15.169 ms 11.262 ms 13.040 ms
8 xe-6-1-1-0-ar03.newcastle.de.panjde.comcast.net (69.139.193.142) 24.734 ms 24.958 ms 9.710 ms
9 pos-5-13-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.95.141) 17.833 ms 17.467 ms 16.256 ms
10 pos-4-9-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.87.194) 28.627 ms 28.160 ms 29.041 ms
11 pos-1-8-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.88.61) 51.619 ms 53.124 ms 51.594 ms
12 pos-0-14-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.85.141) 87.474 ms 93.155 ms 84.350 ms
13 pos-0-2-0-0-pe01.600wseventh.ca.ibone.comcast.net (68.86.87.154) 84.109 ms 82.454 ms 83.000 ms
14 as4134-pe01.600wseventh.ca.ibone.comcast.net (75.149.229.198) 81.253 ms 82.346 ms 81.666 ms
15 202.97.49.117 (202.97.49.117) 181.939 ms 210.892 ms 185.448 ms
16 202.97.51.89 (202.97.51.89) 351.861 ms 366.925 ms 464.893 ms
17 202.97.61.237 (202.97.61.237) 335.844 ms 341.187 ms 340.506 ms
18 202.97.33.225 (202.97.33.225) 338.346 ms 355.314 ms 349.339 ms
19 119.145.47.93 (119.145.47.93) 343.147 ms 355.392 ms 358.753 ms
20 121.15.179.17 (121.15.179.17) 359.169 ms 352.942 ms 341.477 ms
21 58.60.24.137 (58.60.24.137) 338.301 ms 349.406 ms 356.505 ms
22 219.134.241.249 (219.134.241.249) 363.196 ms 352.480 ms 356.865 ms
23 61.145.163.54 (61.145.163.54) 354.926 ms 356.274 ms 358.925 ms
24 202.105.135.2 (202.105.135.2) 353.008 ms 347.351 ms 348.986 ms
25 * * *
26 119.145.40.29 (119.145.40.29) 361.046 ms 354.343 ms 350.460 ms
27 * * *
28 * * *
29 * * *

 

[BorisS]

hmm strange

same results from my side, austria Vienna:

But i can certainly connect with the DJI client

traceroute to 113.105.65.180 (113.105.65.180), 64 hops max, 52 byte packets
1 dsldevice.lan (10.0.0.138) 48.546 ms 95.498 ms 100.183 ms
2 xxxxxxxxxxxx (xxxxxxxx) 10.741 ms 10.036 ms 9.761 ms
3 84.116.229.109 (84.116.229.109) 174.795 ms 174.806 ms 175.041 ms
4 at-vie15a-rd1-vl-2051.aorta.net (84.116.229.1) 204.573 ms 177.755 ms 213.813 ms
5 uk-lon01b-rd1-xe-7-1-2.aorta.net (84.116.134.229) 174.779 ms
uk-lon01b-rd1-xe-1-0-2.aorta.net (84.116.130.253) 174.693 ms
uk-lon01b-rd1-xe-7-2-2.aorta.net (84.116.134.233) 174.619 ms
6 84-116-130-141.aorta.net (84.116.130.141) 175.092 ms 174.949 ms
84-116-130-149.aorta.net (84.116.130.149) 174.854 ms
7 us-sjo01a-ri2-gi-3-0-0.aorta.net (213.46.190.102) 175.082 ms 173.919 ms 174.317 ms
8 213-46-190-218.aorta.net (213.46.190.218) 175.371 ms 175.598 ms 174.058 ms
9 202.97.52.225 (202.97.52.225) 174.099 ms 176.219 ms 186.264 ms
10 202.97.50.129 (202.97.50.129) 339.549 ms 338.712 ms 341.252 ms
11 202.97.60.69 (202.97.60.69) 344.306 ms 345.180 ms 364.011 ms
12 202.97.33.117 (202.97.33.117) 357.282 ms 355.466 ms 354.631 ms
13 119.145.45.190 (119.145.45.190) 343.198 ms 343.613 ms 344.919 ms
14 121.15.179.17 (121.15.179.17) 346.933 ms 344.663 ms 343.947 ms
15 119.145.55.130 (119.145.55.130) 357.103 ms 357.059 ms 357.547 ms
16 219.134.241.249 (219.134.241.249) 348.023 ms 347.601 ms 347.989 ms
17 61.145.163.54 (61.145.163.54) 344.371 ms 343.766 ms 344.009 ms
18 202.105.135.26 (202.105.135.26) 353.837 ms 353.420 ms 353.977 ms
19 * * *
20 119.145.40.29 (119.145.40.29) 345.419 ms 345.010 ms 344.918 ms
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *