Unable to access a netwrok share via the CRD9000-4001E

12/05/2008 12:10pm
CRD9000-4001E
Firmware 07022400
Clarify case 1774371
Customer reported inability to access network share , (which is on the same subnet) via MC9090's docked in the CRD9000-4001E Ethernet cradle. Customer can access the network share via his WLAN on the MC9090's. These methods go through same DNS.
I have reproduced this problem using same type cradle, same firmware, same IDockit version. I have traces from customer and from my testing including failed attempts from the cradle and succesful attempts from the WLAN.
George Dellaratta
What question are you asking?

What question are you asking?
Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Howard Laser
Before opening an SPR, I

Before opening an SPR, I wanted to know if anyone has any previous experience with this issue. Should the CRD9000-4001E support this feature? The CRD7000-4000E cradle does support this. Is there anyone who has experience configuring these cradles via MobileDox and IDockit that may have a workaround.
Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


David Meyer
What was the name of the

What was the name of the server would were trying to access in these netlogs?  It looks like your WiFi case is trying to access a different server than your Ethernet Cradle trace.
Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Howard Laser
Sorry, Dave. Please check the

Sorry, Dave. Please check the attached file. It includes 3 trace files. The netlog is from the MC9090 showing a failed attempt from the E-cradle. The laserwireless trace is from a sniffer on the WLAN showing a succesfull connection to the share. The Ethernetissue is a trace on the network from the switch showing a failed attempt.  All connections asre trying to access 10.150.73.253
Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


David Meyer
Your ethernet related traces

Your ethernet related traces show that the terminal is not even trying to connect to the network share.  My guess is that Connection Manager is setup in a way that it does not believe that it has a viable path to connect.  I would suggest testing with the setup that Both internet and private networks connect though My Work Network.  This is in the Connections control panel applet, under Advanced > Select Networks.  This is the 'easiest' setting that would most often work.
Vote: 
Vote up!
Vote down!

Points: 1

You voted ‘up’


Howard Laser
Testing was done with 

Testing was done with  settings in Connection Manager set for My Work network and My ISP with same results.
Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


David Meyer
Can you browse the web using

Can you browse the web using IP addresses and also via named websites from this same device while in the ethernet cradle?
Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Howard Laser
Tried connecting

Tried connecting unsuccesfully to google and motorola web pages via IP address and name. In both cases received error "The page cannot be found. Check the name and try again". Testes with and without proxy set in connection manager.
We have tested MC70 in its ethernet cradle and can connect to google, motorola and the network share succesfully.
Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Howard Laser
If there are no other options

If there are no other options, I will open the SPR on this issue.
Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


David Meyer
Howard,  I have a hard time

Howard,  I have a hard time believing that the Ethernet cradle doesn't work to this extent, and customers haven't complained until now.  Are you sure that EVERYTHING is setup properly?  Have you tried a WinCE MC9060, WinCE9090, WM 9060, WM9090 and find that everything fails or everything expect one works, etc?
Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Howard Laser
I will attempt testing with

I will attempt testing with these other terminals. Maybe that can isolate the issue to Idockit or the Operating System. I will post my results. Thanks .
Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Howard Laser
I have now tested MC9090/CE5

I have now tested MC9090/CE5.0, latest Idockit, MC9090/WM5.0 latest Idockit, MC9060/CE4.2 latest E-connect, MC9060/PPC03, latest E-connect. All terminals exhibit the same behavior. Via the WLAN we can access the network share. Via the 9000 ethernet cradle we get 'network path not found'. We also downgraded the version of the cradle, and received the same results. Dave, if you are able, and would like to see the setup we have it here in the Support center, 2 cubes from mine. Please let me know if you would like to come by.
Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Log in to post comments