Mobility Site - View Single Post

rroberts161 · 06-03-06, 11:55 PM

I probably don't have the answer here, but I have a couple thoughts.

Have you taken a look in the hardware manager for your PC and checked to see if the USB ports are all kosher? Do other USB devices function normally? If not, debug the USB connection at your PC and then delete your sync targets and try again with AS.

Also, does your PC run XP Home Edition or the Pro version? I have never used the Home Edition, so I cannot speak to this. On XP Pro however, you can examine the system logs using the MMC snap-in eventvwr.msc. If you have the Pro version, you can enable even greater levels of auditiing by fiddling with Local Policies...unless your XP box lives in a domain where administrators have a domain based policy that is enforced. In this case, security may prevent you from changing the options in your Local Policy.

If you take a close look at the SYSTEM as well as APPLICATION logs, there may very well be error messages there that will help elucidate the foundation of your AS troubles. If the errors are security related, you may also find telltale signs in the SECURITY log, although to really flesh this log out you must be able to set policy.

When you say that your AXIM will connect, then there is a sound of demise from your AXIM. What does AS say at this time? Does AS display your AXIM's name when you are connected? Does the name stay in the AS display AFTER the "plonk of death"? This will indiciate to a pretty meaningful degree the status of your USB bus and the basic connection itself.

I hope my next question will not insult you. Can you tell me, are you sure that tcp/ip is installed on your XP machine, and that the tcp/ip stack is bound to your AS cradle? This means making sure that tcp/ip is loaded for the AS connection and that file and print sharing is also enabled for that connection. You do have a new network connection if you look in the XP machine's 'Start-->Settings-->Network Connections' and looking to see if the AS cradle has a separate network connection here.

The only other thing I can think to have you check is the ip addresses that AS likes to use. The AS program likes to use 192.254.2.1 and 192.254.2.2 for the cradle and AXIM respectively. If you are using these addresses in your LAN someplace this could muck up the synchronization. These addresses can sometimes be unavailable because they are being used for something like ICS (Internet Connection Sharing), or they can be removed from service because they are in a list of reserved addresses being held by a DHCP server. If you have ICS, NAT, DHCP server or the like that has ownership of the addresses, this could mess things up.

I think that the AS software contains it's own DHCP server, and this is reflected in the information one sees if you run ipconfig/all while AS is connected successfully. If I recall correctly, DHCP starts with a client broadcasting a query trying to find a DHCP server. This could give you the impression that the AXIM connects. If the AXIM cannot then get a response from the AS embedded DHCP server, I would expect exactly the sort of ABEND you discribe.

One last thought....even though you have turned off your firewall, is it possible that you enabled IP Filtering in the network conncetion tcp/ip advanced configuration settings? If you turn on IP Filtering for one adapter, you are turning it on for all of them since the setting is adapter global. If you somehow have IP Filtering active, this could yentz you just as you describe.

I am not sure this will help, but I thought about your problem lots and hope that I came up with at least one avenue of debugging that you have not yet been down. Good luck!

06-03-06, 11:55 PM	#11 (permalink)
rroberts161 Aximsite Rookie Join Date: May 2006 Location: Fullerton, California; North Orange County, just south of L.A. Posts: 27 Device: V220 Carrier: Cingular Thanked 0 Times in 0 Posts	Have you tried this? I probably don't have the answer here, but I have a couple thoughts. Have you taken a look in the hardware manager for your PC and checked to see if the USB ports are all kosher? Do other USB devices function normally? If not, debug the USB connection at your PC and then delete your sync targets and try again with AS. Also, does your PC run XP Home Edition or the Pro version? I have never used the Home Edition, so I cannot speak to this. On XP Pro however, you can examine the system logs using the MMC snap-in eventvwr.msc. If you have the Pro version, you can enable even greater levels of auditiing by fiddling with Local Policies...unless your XP box lives in a domain where administrators have a domain based policy that is enforced. In this case, security may prevent you from changing the options in your Local Policy. If you take a close look at the SYSTEM as well as APPLICATION logs, there may very well be error messages there that will help elucidate the foundation of your AS troubles. If the errors are security related, you may also find telltale signs in the SECURITY log, although to really flesh this log out you must be able to set policy. When you say that your AXIM will connect, then there is a sound of demise from your AXIM. What does AS say at this time? Does AS display your AXIM's name when you are connected? Does the name stay in the AS display AFTER the "plonk of death"? This will indiciate to a pretty meaningful degree the status of your USB bus and the basic connection itself. I hope my next question will not insult you. Can you tell me, are you sure that tcp/ip is installed on your XP machine, and that the tcp/ip stack is bound to your AS cradle? This means making sure that tcp/ip is loaded for the AS connection and that file and print sharing is also enabled for that connection. You do have a new network connection if you look in the XP machine's 'Start-->Settings-->Network Connections' and looking to see if the AS cradle has a separate network connection here. The only other thing I can think to have you check is the ip addresses that AS likes to use. The AS program likes to use 192.254.2.1 and 192.254.2.2 for the cradle and AXIM respectively. If you are using these addresses in your LAN someplace this could muck up the synchronization. These addresses can sometimes be unavailable because they are being used for something like ICS (Internet Connection Sharing), or they can be removed from service because they are in a list of reserved addresses being held by a DHCP server. If you have ICS, NAT, DHCP server or the like that has ownership of the addresses, this could mess things up. I think that the AS software contains it's own DHCP server, and this is reflected in the information one sees if you run ipconfig/all while AS is connected successfully. If I recall correctly, DHCP starts with a client broadcasting a query trying to find a DHCP server. This could give you the impression that the AXIM connects. If the AXIM cannot then get a response from the AS embedded DHCP server, I would expect exactly the sort of ABEND you discribe. One last thought....even though you have turned off your firewall, is it possible that you enabled IP Filtering in the network conncetion tcp/ip advanced configuration settings? If you turn on IP Filtering for one adapter, you are turning it on for all of them since the setting is adapter global. If you somehow have IP Filtering active, this could yentz you just as you describe. I am not sure this will help, but I thought about your problem lots and hope that I came up with at least one avenue of debugging that you have not yet been down. Good luck! __________________ ============================== Robyn Robertson Ent. Eng./ Proj. Mngr. Eos Consulting/Concannon Systems To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. ==============================