Dear Greg and Sven,
I was quite anxious to see if this was gonna work with an ad-hoc network, so I just quickly set up an ad-hoc network and that was succesful! After that, I made some changes on the desktop and synced again. No problem!
Since I have both the desktop version and the iPhone app for less than a month now, my log is not completely filled out yet. Since setting up the ad-hoc network takes only 2 minutes I can easily overcome the network problem with my router.
Many thanks to you both, great support!
Martin
PS Just for your information: The WiFi icon does not show up on the iPhone screen during the ad-hoc connection, it shows the 3G icon instead...
Syncing with iPhone: TCP error
Re: Syncing with iPhone: TCP error
Last edited by DeReuf on Tue Dec 29, 2009 07:34, edited 1 time in total.
Re: Syncing with iPhone: TCP error
I did have a nice trip, thanks!
It does look like the WiFi connection is going away on you. This can also happen if the iPhone screen goes blank (i.e. the iPhone goes to sleep) as it will drop the WiFi connection at that time as a power saving mechanism. So it is possible that the phone went to sleep during your test if it took a while and that is why the WiFi dropped. It will be interesting to see what results you get with the AdHoc network as that will also be a new WiFi connection. The default timeout for the iPhone to shut off the screen is 1 minute. You can make this longer in Settings->General->Auto-Lock if you need to during testing.
One other note, I don't believe the iPhone support IPv6 addressing. In any case, Dive Log's sync protocol only publishes it's service on interfaces with IPv4 address (i.e 32 bit addresses in the form 192.168.0.103) and it ignores any IPv6 interfaces that are configured on the iPhone. IPv6 addresses typically look like: 3ffe:1900:4545:3:200:f8ff:fe21:67cf (i.e 128 bits long vs 32 bit long IPv4 addresses). I'm not sure exactly what it means to force ping into IPv6 mode and give it an IPv4 address on Vista (I'm not much of a Windows guy I'm afraid and the Unix version of ping does not support the "-6" option) but that might explain the "Ping request could not find host 192.168.0.100. Please check the name and try again." message. However, it is entirely possible that it just represents the IPv4 address in IPv6 form as an IPv4-mapped address in Vista (IPv4-mapped addresses are not supported in Windows XP, but I don't know about Vista).
Have a nice holiday season. I'll look forward to hearing what you find out when you get back to this.
Cheers,
Greg
It does look like the WiFi connection is going away on you. This can also happen if the iPhone screen goes blank (i.e. the iPhone goes to sleep) as it will drop the WiFi connection at that time as a power saving mechanism. So it is possible that the phone went to sleep during your test if it took a while and that is why the WiFi dropped. It will be interesting to see what results you get with the AdHoc network as that will also be a new WiFi connection. The default timeout for the iPhone to shut off the screen is 1 minute. You can make this longer in Settings->General->Auto-Lock if you need to during testing.
One other note, I don't believe the iPhone support IPv6 addressing. In any case, Dive Log's sync protocol only publishes it's service on interfaces with IPv4 address (i.e 32 bit addresses in the form 192.168.0.103) and it ignores any IPv6 interfaces that are configured on the iPhone. IPv6 addresses typically look like: 3ffe:1900:4545:3:200:f8ff:fe21:67cf (i.e 128 bits long vs 32 bit long IPv4 addresses). I'm not sure exactly what it means to force ping into IPv6 mode and give it an IPv4 address on Vista (I'm not much of a Windows guy I'm afraid and the Unix version of ping does not support the "-6" option) but that might explain the "Ping request could not find host 192.168.0.100. Please check the name and try again." message. However, it is entirely possible that it just represents the IPv4 address in IPv6 form as an IPv4-mapped address in Vista (IPv4-mapped addresses are not supported in Windows XP, but I don't know about Vista).
Have a nice holiday season. I'll look forward to hearing what you find out when you get back to this.
Cheers,
Greg
Re: Syncing with iPhone: TCP error
Hi Martin,
I'm glad to hear that the AdHoc setup worked okay. Sorry I missed your most recent post before I wrote my last post ... so you can pretty much ignore that one
!
I imagine that your router probably has some security setting that is causing the difficulty. There are certainly lots of different routers with many different options including blocking certain port ranges. Feel free to contact me (support "at" moremobilesoftware "dot" com) if I can provide any information to help sort though the configuration options.
Cheers,
Greg
I'm glad to hear that the AdHoc setup worked okay. Sorry I missed your most recent post before I wrote my last post ... so you can pretty much ignore that one
!I imagine that your router probably has some security setting that is causing the difficulty. There are certainly lots of different routers with many different options including blocking certain port ranges. Feel free to contact me (support "at" moremobilesoftware "dot" com) if I can provide any information to help sort though the configuration options.
Cheers,
Greg
Re: Syncing with iPhone: TCP error
Oh, regarding your P.S. ... you're right that the 3G indication will stay on when you are using an AdHoc WiFi network ... you'll probably notice that the WiFi icon does eventually show up sometimes. It doesn't always show up, but when it does it can often take quite a while. I have no idea why this is though.
Cheers,
Greg
Cheers,
Greg
Re: Syncing with iPhone: TCP error
Yes, I also missed my post just after publishing it. Because it was posted on a new page in the forum. Regarding router settings: it is just a simple Sitecom router and I have already tried to play around with security settings and port forwarding to solve this problem. I really can't get clear what is exactly causing the network error, but since I am not an IT specialist (rather an autodidact) I am not going further into this. The ad-hoc netwerk will be fine with me.gregm wrote:Hi Martin,
I'm glad to hear that the AdHoc setup worked okay. Sorry I missed your most recent post before I wrote my last post ... so you can pretty much ignore that one
...
By the way, I have not ran into any WiFi network problems during gaming. (I'm not a die-hard gamer but like to play left 4 Dead and Trackmania once in a while). I will use the oncoming holidays to get my logbook all filled out and transfered to my iPhone
Cheers,
Martin
Re: Syncing with iPhone: TCP error
Hi Martin
I'm glad it works now, hopefully this time a bit longer
Networks can be sometimes tricky, unfortunately WiFi is the only way to transfer the data.
Cheers,
Sven
I'm glad it works now, hopefully this time a bit longer
Networks can be sometimes tricky, unfortunately WiFi is the only way to transfer the data.Cheers,
Sven