Pocket PC Networking Error Message

[l0l]

Originally Posted by rael42

This fix did not work for me on my X51v.

I looked around the registry a bit near that RNDISFN1 key and saw that it had a binding for AnthaVPN and since I installed the full version around the time I started to get the error message, I uninstalled AnthaVPN and now the error seems to be gone.

AnthaVPN has issues with the radio in the X51v and they are working on it.

So if you're still having this issue or looking for other possible causes of the error, I think AnthaVPM may be a possible culprit. I hope when they have the software working with the AXIM I don't find I have to live with this error, but if so, I guess I'll make do.
jon

Your are correct, the AnthaVPM is a culprit in your case.

The fix is specifically for ActiveSync only.

It will not work when a second element, AnthaVPN or any third party software which uses the RNDISFN1, is introduced. Unlike your Palm, the X51v isn't on the AnthaVPN supported device list.

Your issue is "Why didn't AnthaVPN unbind when its session terminates?"

Wrt I hope when they have the software working with the AXIM I don't find I have to live with this error, but if so, I guess I'll make do.
Try posting the following registry subkey. Export the branch from your X51v registry subkey HKEY_LOCAL_MACHINE\Comm\RNDISFN1. Save it as a ".reg" file. You might have to rename it to ".txt" when uploading.

[rael42]

I actually used Mergic on the Palm and also, the Dell Axim X51v is listed as a "Tested Device" with the Windows Mobile 2005 version of AnthaVPN (as are PIX firewalls). I checked this before I bought but one of their support techs let me know they were detecting some problems with how the wifi adapter interacts with AnthaVPN on an X51 device.

I appreciate all the helpful information. Actually I did my first hard reset on my Axim today to start with a clean slate (too much experimenting with various network pieces attempting to get VPN working) so I won't be reinstalling AnthaVPN or even messing with VPN for a bit. I have bookmarked this thread in case I have more issues like this when I get brave enough to take another run at it.

Thanks again.

jon

[easterbird]

Originally Posted by l0l

The challenge is on. I saw your message today and began working on it right away ... started late (2 am Mountain time).

I didn't Google, since you mentioned the solution isn't there. Based on the information you provided, I was able to duplicate your error.

THE SOLUTION:

1. Remove the Axim X51V from the cradle.
2. Edit the X51V registry. I used PHM Registry Editor Version 0.7.
3. Look for the registry key:
HKEY_LOCAL_MACHINE\Comm\RNDISFN1\Parms\TcpIp
Change
EnableDHCP=1
to
EnableDHCP=0
4. Quit the registry editor using Tools > Exit. I did not soft reset the X51V.
5. After making the above registry change, dock the X51V. I waited more than 30 minutes and still no error. Before the registry change, the error appeared between 1 to 3 minutes after docking the X51V.

That's it.

You can keep the GeForce 5200 128 MB AGP video card. It's against my rule to take things from friends. Ask AximUsers.com to give me a promotion ... with the title Moderator.

I'll catch you later today. It's way past my bedtime now - 3.45 am Mountain time.

I've attached the wrong error message file. The correct file is attached in the post (#3) below.

Okay, this may help me since I am getting these messages. How does one find registry info to edit?? please any help appreciated from this newbie.

[Mahstah]

Try PHM registry editor. Using it, you can browse down through the branches of your registry hives and perform the necessary edits.

[Sidney]

in fact, I had the same problem on a Qtek S200 : "Unable to obtain a server-assigned IP address" although everything was working fine. I also have Anthavpn. After reading this thread, instead of uninstalling it, I put a static IP on the interface Anthavpn remote NDIS host :
169.254.2.1
255.255.255.0

And problem solved.
I tried back in DHCP, the problem occured. So this is clearly the root of the problem.
And of course, you can still establish VPN connections with this setting.

[cmwin]

I am not sure whether this will apply to everyone with this problem but I believe that I have found a much simpler solution for this problem on my Axim 51v.

I had the "Unable to obtain a server-assigned IP address" message and immediately went Google - I had no idea what to do. One suggested solution was to edit the registry - I tried downloading some registry editors but gave up because the software was not idiot-proof and I lost my nerve!

Back to Google and the suggestion to change the IP address to a static one under Settings-Connections-WLAN adaptors-NDIS etc. Some posts had prescribed a static address - I tried these suggestions with no success. I then tried leaving the static address details blank - and the machine politely told be that I neded to identify my Axim on the network.

Light dawned! I checked the network addressed assigned by my wireless router, entered this address and that of the router as the gateway - and it all works. No messy message. No sync failed alarm. Emails go from my Axim - files transfer to it. Software (Epocrates) that accesses an internet server works fine. And no need to switch off DCHP deep in the bowels of my machine!!

Hope this helps. Interested to know if there are issues with this for others?

[Mahstah]

Are you saying that you entered your router's DHCP settings in the Remote NDIS Host adapter or that you entered a static address that would be given to your wireless adapter from your wireless router?

The Axim should never be able to sync on the cradle with any address applied to the NDIS adapter other than the DHCP settings of IP: 169.254.2.1 Subnet Mask: 255.255.0.0 Gateway: 169.254.2.2. These settings are handed to the adapter through ActiveSync on the desktop, not by a router.

But hey, if it works for you that's good.

[cmwin]

Having read the posts I was as surprised as you. Is gnorance bliss?

In Remote-NDIS settings I entered the address assigned to the Axim by the DCHP server in my wireless router [192.168.1.3 - set while using WIFI access] and the router's own network address [192.168.1.1] as Default Gateway.

Having just tested Activesync again (for the 5th or 6th time tonight) it all seems to work, and the Axim's sync log confirms a successful sync 10 minutes ago.

I am not knowingly using any other independent networking software on my Axim.

Should I be expecting problems with this set-up? I was perfectly happy syncing by Bluetooth but media files cannot be transferred simply via BT.

[Mahstah]

Let me correct myself, I was wrong in that the desktop gives the PPC a DHCP address. It's the other way around. Either way, a static address should not work for your NDIS adapter. I'll try it out on my own and see what happens...

These quotes are where I learned the true nature of the ActiveSync 4.x connectivity regarding the virtual network adapter and DHCP for it. This Chris De Herrera guy is brilliant, check his pocketpcfaq site.

from: http://support.microsoft.com/newsgro...d4a1e92627&p=1

"Hi,
ActiveSync 4.x uses the RNDIS interface for USB sync. The PC is assigned an IP address from the Pocket PC. The IP address is 169.254.2.1 for the Pocket PC and 169.254.2.2 for the PC.
Check to see that the RNDIS interface is coming up when you start to sync
via USB.
--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com"

From another very smart individual at http://www.futurehardware.in/430499.htm :

"The device is set for DHCP, but it's actually supposed to be the DHCP
server, not a client, in this connection.
Paul T."

[mbloof]

For me setting the "Alternate configuration" for the "Windows Mobile-based Device" IP: 169.254.2.2 Mask: 255.255.0.0 fixed the forever animated icon in my system tray.