[missing-sync-palmos-talk] Re: can't get network sync to work :-/

[Timothy Luoma]

On Aug 26, 2005, at 10:12 AM, Scott Gruby wrote:

> On Aug 25, 2005, at 11:27 PM, Timothy Luoma wrote:
>
>> On Aug 26, 2005, at 12:21 AM, Scott Gruby wrote:
>>
>>> Missing Sync's Internet Sharing assigns an IP address of  
>>> 192.168.206.206 to the handheld as most home networks default to  
>>> 192.168.x.x. This is probably part of your issue.
>>
>> Ah.  Well, that's generally true *except* with Airport, which  
>> defaults to 10.x.x.x
>
> Thanks for pointing this out; what we'll try to do is be  
> intelligent about the address we use and base it on the same subnet  
> as your Mac.

Well let's see, when I'm dialed in to the office, my modem connection  
IP is 192.168.x.x and Airport is 10.0.1.x, so how will you decide  
which one to use?  (Hint: do your best to guess, but let me set it if  
I want)


>>> Second, you need to specify Local HotSync and not LANSync as you  
>>> should just pretend that when Missing Sync is in sharing mode, it  
>>> is just a network connection.
>>
>> Changing that worked once... then the stupid Primary PC Name got  
>> changed from the IP back to the hostname .... gawd I would love to  
>> find a way around that bug besides having to switch it back every  
>> time.
>
> I realize you probably have a reason, but why not just hook up your  
> device to your PC and sync?

Couple reasons:

     1) when at the office, I have my Mac and my PC on the same LAN,  
but the Palm is hooked to the Mac, using MissingSync to update  
SnapperMail on an hourly basis via Internet Sharing


     2) when I'm on the road, I can sync my Palm wirelessly to my PC
     http://tntluoma.com/beyond30/2005/03/act_wireless_hotsync

     3) My ideal situation is to be able to sync my Palm to  
VirtualPC, but I can't get it to work doing a regular USB sync  
(HotSync never connects).  So if I thought I'd try a *network* sync  
(assign VirtualPC its own IP address)

>>> In the future, it is possible that we'd allow you to change the  
>>> subnet that is assigned to the handheld, but at this point it is  
>>> not user configurable.
>>
>> Given that Apple's Airport uses 10.x.x.x, that seems to be a good  
>> idea.
>
> I can't give you an estimate on when a change will be made for  
> this, but in your case, switching to the 192.168 subnet may be the  
> easiest solution.

It actually did work with the real PC, but still not with the Virtual  
one :-/


TjL