1) 11:10-9/13/2010

2) 3-day

3) CRD9000-4001ER

4) WM5.0

5) 2215967

Customer poses the following question below...I believe the mechanism which controls whether the devices receive their own DHCP IP addresses has something to do with Option 61 on their DHCP server. Can anyone confirm or advise on this scenario? Support Question: WE ARE ATTEMPTING TO USE THE 4-BAY ETHERNET CRADLE TO GET CONNECTIVITY FOR AN APPLICATION RUNNING ON THE MC9090 WM5.0 USING IDOCKIT. THE LOCATIONS WHERE WE WILL BE DEPLOYING THESE DO NOT HAVE ANY WIRELESS. THE APPLICATION WILL CONNECT TO OUR NETWORK THROUGH A VPN CIRCUIT.

THE ISSUE WE ARE SEEING IS WITH SETTING THE CRADLE TO RECEIVE ITS IP ADDRESS, AS WELL AS THE PORT IP ADDRESSES USING DHCP. THE CRADLE GETS ITS IP ADDRESS JUST FINE, BUT DOES NOT GET IP ADDRESSES FOR THE PORTS. WHEN MORE THAN ONE MC9090 IS PLACED IN THE CRADLE, THEY EACH SHOW THE SAME IP ADDRESS AS THE CRADLE IN IDOCKIT. WHEN I CONNECT THE CRADLE TO THE INTERNAL COMPANY NETWORK FOR TESTING, THE CRADLE GETS ONE IP ADDRESS AND EACH PORT GETS A SEPERATE IP ADDRESS.

I TOOK THE CRADLE HOME AND CONNECTED IT TO MY HOME NETWORK, WHERE I HAD 20 IP ADDRESSES STILL AVAILABLE AND SAW THE SAME RESULTS AS WHEN IT IS CONNECTED TO THE STORE VPN CIRCUIT. THE CRADLE GOT AN IP ADDRESS AND EACH PORT THE 3 MC9090S WERE IN WERE ALSO ASSIGNED THAT SAME IP ADDRESS.

WE CAN WORK AROUND THIS BY LEAVING THE PORTS ASSIGNED A MANUAL IP ADDRESS (THE FACTORY DEFAULT), BUT THEN WE HAVE AN ISSUE WITH OUR MANAGEMENT SOFTWARE SHOWING ALL OF THE MC9090S CONNECTED THROUGH THE CRADLES AS USING THE SAME IP ADDRESSES OVER AND OVER. IT IS MANAGEABLE THROUGH THE MANAGEMENT SOFTWARE WE USE, BUT IT CERTAINLY LESS THAN DESIRABLE. WHAT COULD BE CAUSING THE DHCP ISSUE WE ARE SEEING?