dougp1122

Since I upgraded my X50v to WM5 and Activesync 4.1, I have not been able to connect via USB. I get the following message:
"Pocket PC Networking, Unable to obtain a server-assigned IP address. Try again later or enter an IP address in Network settings."

I get this after several minutes, where the status reads "Connecting". I am able to connect via Activesync through IR. I am also able to connect via 802.11 to the Internet thorugh my home network. In this instance the X50v is able to acquire an IP.

I have searched the forums and have not found this issue elsewhere. Any ideas?

ikehiker

Turn off Powersave mode in the Dell WLAN

Make sure both dropdown lists on the Network Management page are set to "My Work Network"

Any security set on your router? Regardless, I'd try resetting the router and setting it up from scratch, trying to connect initially without any security. You might also check the router manufacturer's website to see if they have and firmware upgrade.

BTW, you had this posted in the ActiveSync forums. I've moved it to the wireless forums where it should get more appropriate attention.

__________________
-Ike-

dougp1122

I greatly appreciate the suggestions. I tried both to no avail. I am a bit confused, though, as to why this subject is best suited for the wireless forums. My issue is in establishing an Activesync connection via a wired USB link.

ikehiker

Oh :crooked: I misread your message. I thought you were getting this problem when trying to establish a wireless connection. I'll move it back.

In this case, the problem probably relates to a firewall on your PC. I'm on my PPC so I cannot easily do a search but there are some links on the site for an M$ web page describing the issue with AS4.x.

__________________
-Ike-

Facom

I had this problem and found a fix.

I solved it by going to Settings|Connections|Configure Network adapters. Set
the 'Remote-NDIS Host' settings to use a specific IP address of 169.254.2.1,
subnet 255.255.0.0, default gateway 169.254.2.2


This is what they should be anyway, everything should work now and no
annoying message.

dougp1122

I appreciate the reply. I have had this working for some time. Although I continue to limp along in general on WM 5. I have been running WM 5 since December and starting to think about downgrading to WM 2003.