Wifi file transfer

I typically use Idoceo's wifi file transfer to upload files to the programme. It's been working well for me until the past week, when some of the computers on my network have been unable to connect to the required url for the server (the connection attempt times out). I have not been able to figure out a pattern. The computers that can connect to it are running the same operating system and web browser as others that can't connect. And the computers that can't connect have always been able to connect in the past.

My feeling is that it's a local network issue - my school's network is pretty shakey - but I'm just wondering if you have any suggestions that might help me isolate the cause of the problem.

Cheers

Joel

Hello Joel,
Yes, it seems like a network issue. It probably has to do with iDoceo working on port 8080 (the default port for webs is 80) which may be disabled or 'firewalled' in some networks.

Here is what you should do on the computer that is experiencing this issue:

- If there is internet connectivity in that computer try to open this page portquiz.net:8080/
This is a generic web that works on port 8080 like iDoceo.
With this you will now if those ports are blocked outside your network. They could still be blocked
inside though.

- If you have access to the computer's command line, type ping IP.IP.IP.IP
(IP being the actual IP address of your iPad. You will see that address when iDoceo enables its WiFi mode).
For example, if iDoceo shows http://192.168.1.7:8080 you should type

- If everything succeeds, the final test: type telnet IP.IP.IP.IP 8080
again, IP is the current address of your iPad.

Let me know how that worked for you.

Regards

Portquiz says 'Your network allows you to use this port.'

But pinging the ipad times out: 'Request timed out'.

And telnet 'could not open connection to the host, on port 8080'.



Joel

Ok, you should now focus on that ping test. This should provide the pattern you are looking for.

From the computer that is able to connect to iDoceo, make sure the ping succeeds.
If it does, you should check the IP address of that particular computer:
- if on windows, type ipconfig on the command line
- if on Mac OSX or linux type ifconfig

Repeat the same ping on the machine that is not connecting and check the computer's IP address as well.

My guess is that each computer belongs to a different subnet. The ones that work share the same subnet as your iPad or its netmask is properly configured.
Depending on how complex your network is, you may solve this by just changing the netmask of that particular computer.

If you have permission to change it, set it to 255.255.0.0 and give the ping a try

I'm very grateful for your assistance with this.

Ipad details:
IP: 10.200.0.50
Mask: 255.255.252.0

I can ping the ipad from one of the computers that connects to Idoceo (and presumably others too). Eg
IP: 10.108.2.17
Same mask as ipad.

But not from the computers that don't connect. Eg
IP: 10.200.3.53
Same mask as ipad.

Changing the mask to 255.255.0.0 had no effect.

Thanks again.

Joel

Seems like the opposite problem then.
As a simple test, change the netmask of a computer that is unable to connect to 255.255.255.0

Changing to 255.255.255.0 has no effect.

If I plug one of the non-connecting computers into the ethernet port of one that's working, it still doesn't connect.

If I run a different operating system (Linux) on one of the connecting computers, it still pings and connects to Idoceo.

So far, I think we've worked out that the ones that can connect are 10.108.x.x and the ones that can't are 10.200.x.x

Joel

Hello Joel,
I'm afraid I can't provide more assistance without the details or access to your network!
With all this info your IT department should know what to do. A traceroute from the computers that work and the ones that don't should shed some light on the routers/broadcast IP/netmask that needs some tweaking.
The ping does not depend on iDoceo so as long as the iPad is connected to your network, it should reply.
If you solve the issue, please do post!

No worries. Thanks very much for your help. I'll keep trying things and let you know if I find a solution.

Joel

The problem seems to have finally resolved itself. No one's quite sure why, but it works well now.