 |
Chris De Herrera's Windows CE Website |
|---|---|
About |
|
| By Chris De Herrera Copyright 1998-2007 All Rights Reserved A member of the Talksites Family of Websites Windows and
Windows CE are trademarks of
Microsoft All Trademarks are owned |
Configuring Proxim Symphony w/Windows CE
2.x
By Chris De Herrera,
Copyright 1999
Version 1.01 Revised 3/31/99
[an error occurred while processing this directive]
Connecting via Wireless with Proxim Symphony
Being untethered while connected to your LAN while using your Handheld PC 2.0 or Handheld PC, Professional Edition allows you to keep up to date where ever you are - in meetings, at your desk or in the lunch room. Proxim's Symphony offers LAN speeds (1.6 megabits per second) for a home or a small office (usually 150 feet indoors). It costs about $200 per node or less based on the type of hardware you need. You can perform ActiveSync, pickup your e-mail or surf the internet all via the wireless connection. Right now Proxim does not offer a Symphony CF+ card for the Palm-size PC. This article focuses on configuring a Handheld PC to use a Symphony card. Configuration of additional equipment may be required to complete the connection.
Configuring the Symphony PC Card
The Symphony PC Card is compatible with the Proxim RangeLAN2 PC Card. The RangeLAN2 driver is preinstalled on all Handheld PC, Professional Edition units. For the Handheld PC 2.0 systems you need to download the driver from Proxim and then copy the driver via Windows CE Services to your PC Companion. If you want to use ActiveSync, don't forget to synchronize with the desktop via the serial cable before using the Symphony card and you must install the Client for Microsoft Networks as well. Also, you need to know the following to continue the configuration:
- A static IP address for the Symphony PC Card or that your network uses DHCP (Dynamic Host Configuration Protocol). The Symphony system requires you to set the IP address between 10.0.0.2 through 10.0.0.254 with a subnet of 255.0.0.0.
- Subnet of the IP address if you entered it manually.
- WINS (Windows Internet Naming Service) Server IP address or the IP address of the desktop PC to use ActiveSync or the network client. Make sure you check the network settings on the desktop to find out the IP address for the Symphony connection.
When you insert the Symphony PC Card the first time, you will be prompted to enter a driver name to use it. The driver name is proxim. Once you have inserted the card once and entered the driver name, you will no longer be prompted to enter the driver name in the future.
On the H/PC you need to click on Start - Settings - Control Panel - Network and select the Proxim driver. Then configure the card with the information you gathered above. Once this is complete you are ready to access your network.
Configuring the Properties
To edit the properties you must click on the Proxim icon on the task bar.
Then you will see the node address, master address and network domain.
This is where you set the Domain (the channel number) and Security ID. All stations must use the same Domain and Security ID in order to communicate. Symphony only supports Domain 0.
The Site Survey tab allows you to search for all Master access points and then test the link quality. This allows you to identify dead zones in your location.
The Advanced tab allows you to adjust roaming information as well as inactivity timeouts in seconds and minutes.
Your Symphony PC Card is now configured.
Connecting with Wireless
It's effortless to use the Symphony PC Card with Windows CE. Just insert the PC Card and you are connected to the LAN. To use ActiveSync, click start -programs - communications - ActiveSync. then select network connection and click ok. The network client works without requiring an ActiveSync connection
With a Symphony PC Card you can keep up to date wherever you are around the office. For further information on the Symphony PC Card visit Proxim's website.
Troubleshooting
For troubleshooting tips on your Proxim netowrk, see the Network Troubleshooting FAQ.
[an error occurred while processing this directive]