Author Topic: Sync problems with TCP/IP  (Read 11966 times)

Anonymous

  • Guest
Sync problems with TCP/IP
« Reply #15 on: October 09, 2003, 11:32:25 pm »
Quote
Well I finally did it! It was a combination of several techniques in several documents.  I really couldn\'t tell what the magic bullet was except that it had something to do with making sure you have the right version of intellisync or qtopia desktop installed.

i was even able to nat so that i could browse the web (this was done using network connection sharing in win2k).
Hi, I am experiencing the same problem. I am able to ping, ssh ftp etc... but not able to sync. Qtopiadesktop does not recognize the link??
Any clues or answers??

Thanks

novakane

  • Newbie
  • *
  • Posts: 19
    • View Profile
Sync problems with TCP/IP
« Reply #16 on: October 14, 2003, 10:54:23 pm »
I have a SL5500. I have updated to ROM 2.39. The sync has been sporatic from the start. Now it doesn\'t work at all.  The NDIS device is disabled and when I try to enable it, it says connection failed. I\'ve tried shuffling drivers around and no joy. If I remove intellisync and reinstall the drivers I can enable the NDIS NIC, but if I install intellisync again or disable it, the device goes disabled and can\'t be re-enabled.

novakane

  • Newbie
  • *
  • Posts: 19
    • View Profile
Sync problems with TCP/IP
« Reply #17 on: October 15, 2003, 01:13:08 am »
YAAAA!!! I was able to get ip connectivity by using another machine. I used that machine to back date the ROM to 2.8. I tried updating it to 3.13 from 2.8, but I get a fatal exception error while it\'s loading the ROM on to the PDA.  This is the same problem I was having before. Syncing works from the original machine now. I noted that the ROM update on the sharp site says that it\'s only for US.  I ordered mine from a guy in singapore on ebay.  It\'s an english version, but the box says SL-5500, but made in Japan. Does this mean it\'s different than one I would have gotten from someone in the US?
If it\'s different is there anyway I can update to V3 ROM?

undrwater

  • Full Member
  • ***
  • Posts: 232
    • View Profile
    • http://
Sync problems with TCP/IP
« Reply #18 on: October 16, 2003, 01:22:56 pm »
Quote
Qtopiadesktop does not recognize the link??  
Any clues or answers??  

Once again...be VERY SURE of which version of Qtopia/Intellisync and ROM you are using!!  This is absolutely the key!  

If you have the latest (3.13) Sharp ROM get the latest desktop with it (it also works with latest tkcrom too).

I haven\'t gotten OpenZaurus to sync yet, so i\'m not sure which version it needs to sync with.

Also, i don\'t need to use the USB networking to sync, it works without it...just plug in the Z press the sync button and everything happens.

If it still doesn\'t work, post your version #\'s and errors so we can troubleshoot.

lardman

  • Hero Member
  • *****
  • Posts: 4512
    • View Profile
    • http://people.bath.ac.uk/enpsgp/Zaurus/
Sync problems with TCP/IP
« Reply #19 on: October 25, 2003, 09:22:55 am »
When I was running Sharp ROM 3.08 I was also unable to sync using TCP/IP, though Serial and USB-I/O worked fine. I tried pretty hard to work out what was wrong (packet grabbing, port scanning, etc.) but never came up with an explanation. So don\'t worry you\'re not alone. Of course you may be running a different, non Sharp 3.xx ROM, if so just ignore me.


Si
C750 OZ3.5.4 (GPE, 2.6.x kernel)
SL5500 OZ3.5.4 (Opie)
Nokia 770
Serial GPS, WCF-12, Socket Ethernet & BT, Ratoc USB
WinXP, Mandriva

corky

  • Newbie
  • *
  • Posts: 47
    • View Profile
    • http://mysite.verizon.net/corky8332/
Sync problems with TCP/IP
« Reply #20 on: October 25, 2003, 11:04:10 am »
Have you changed IP addresses? Dont forget the last octet on the PC has to be 1 (xxx.xxx.xxx.1)  the default is 192.168.129.201 on the Z and 192.168.129.1

corky
SL5500 3.13 Rom
Lexar 256 CF (FAT)
PNY 256 SD (EXT2)
Ambicom CF modem
Sharp Serial cable
AIR Cable

Tim

  • Newbie
  • *
  • Posts: 2
    • View Profile
    • http://
Sync problems with TCP/IP
« Reply #21 on: October 27, 2003, 02:30:13 pm »
I just purchased a 5500 and also have problems synching at first.  While I don\'t write code I consider myself more of a moderate to advanced linux user, been in it for a few years now.  I found a combo of things can go wrong with the syncing.  When I got it I spent the first 3 days flashing my rom and working with the syncing to both try new roms and to learn how the synching works...(I think I must have flashed at least 10 times within 2 days).    

Here are the problems I discovered:

Intellisync
1.   Newer roms like thekompany.rom and the new sharp rom require the new version of intellisync to work.  If  the versions are a mismatch then it won’t work.  You can download it for free from myzaurus.com
2.   New versions of intellisync and newer roms offer a USB I/O option to sync.  This is junk for the most part and while it will work other things won’t.  If  you change this you have to change it on the Zaurus and on Intellisync through the “zaurus manager”.
3.   The new roms come with USB I/O Defaulted in the pclink program.  When you switch it takes an ungodly amount of time to configure after you click ok and can seem like it is hung up.  Resist the temptation to soft reset the z.  It will eventually get configured.  Rebooting the z after is a good idea.
Windows
1.   When you sync and it installs the NDIS5 adapter it will assign the network connection a Dynamic ip address.  Sometimes this will cause conflicts as it won’t be the right range.  I found that changing the ip address to the right range will work, otherwise assigning an ip address of 192.168.129.1 (that one works for me).
2.   If you can’t sync drop to command line in windows (start]]run]]type cmd) and ping the zaurus ip address 192.168.129.201 by default.  If you get no response it’s configured incorrectly or the windows system may need a reboot.
3.   Typically win xp/2000 doesn’t require a reboot after installing new network cards but when it first detects the zaurus it needs a reboot before the network adapter will see the zaurus networking wise.
4.   When you flash the rom with a different rom (i.e. Stock sharp to thekompany.rom) then it will install a new adapter and you.  You’ll have to fix the ip address again, and reboot to ensure.  

Sometimes the Rom just doesn’t get put on correctly.  I had an issue synching when I switched to thekompany.rom and couldn’t resolve it.  It appeared to work but nothing was seen.  I reflashed the rom with a redownloaded image and was able to get it to work.  

Getting the synching to work under the stock rom can be painful.  I highly suggest updating it.

The openzaurus rom I don’t really remember what I did with it or which version of intellisync I used, I believe it was the older version.  I didn’t really like it aside from its visually pleasing benefits.   Hope this helps.

Tim

jjones3

  • Newbie
  • *
  • Posts: 2
    • View Profile
Sync problems with TCP/IP
« Reply #22 on: February 16, 2004, 01:46:55 pm »
Quote
Well, in my case the TCP/IP connection seems to be fine - I can keep an ssh connection up to the zaurus even while the sync fails..

I\'m aware that the Zaurus is a different beast from, say, a palmpilot, but I\'m fairly experienced with Linux and can get my hands dirty if necessary.. it\'s just a pain that the syncing seems to have failed without apparent reason - I don\'t currently have any WIFI stuff, and unfortunately I doubt the IT department where I work would be too keen on my hooking up a wireless connection, anyhow.  So.. any suggestions as to how to fix this issue would be very much appreciated!

Thanks!

Kafka, Did you ever get this resolved?  I am having the exact same problem.