Author |
Topic |
|
wiblake@tycoint.com
17 Posts |
Posted - 30 Mar 2004 : 15:58:41
|
What would cause ActiveSync on Ethernet to fail to recognize an existing partnership? WINS?
Despite the partnership, attempting to connect with ActiveSync over Ethernet seems to fail after a brief period of "Guest" on the PC Host. Once "repllog.exe /remote" is invoked on the Graphics Client, the "Guest" connection appears in ActiveSync on the PC, and then the Graphics Client proceeds through "Checking for partnership with this computer. Please wait..." ultimately leading to "ActiveSync not responding on the desktop computer" which also ends the "Guest" connection in ActiveSync on the host PC. The TCP/IP configuration is static, with WINS set to the static IP address of the host PC, which has a 2nd NIC card to connect to a corporate Network.
When a serial link replaces Ethernet, the partnership works well.
Thank you, Wil Blake
|
|
akidder
1519 Posts |
Posted - 30 Mar 2004 : 16:09:23
|
Are you sure the Ethernet connection is stable? You might try connecting the GC Plus to the corporate network to confirm that it can browse reliably. Then use that same network to connect to the host PC for ActiveSync. |
|
|
wiblake@tycoint.com
17 Posts |
Posted - 31 Mar 2004 : 07:58:50
|
Thanks yet again for your reply.
The Static IP Ethernet Connection hardware is stable. Indeed, when I change to use Dynamic addressing it works. With the GC+ TCP/IP setup for Dynamic Addressing and DHCP the Ethernet Activesync recognizes the partnership with a Windows XP host.
When setup with static addressing, the Windows XP host ActiveSync partnership acts as previously described, however the ActiveSync Ethernet partnership with an old Windows98 system does work.
I have not yet tried dynamic addressing with the Windows98 system. ActiveSync Ethernet with Static IP remains preferable for the current project, ideally using the WindowsXP development host.
Thanks again, Wil Blake
|
|
|
|
Topic |
|
|
|