Home

Action
Log In

Site Contents
Classified Ads
Developer's Corner
Download Software
Links
Mobile Channels
News
Pocket PC Forums
Reviews
Technical Support
Tips and Tricks
Vendors and Products

Administration
Webmaster

Search

All Software
HPC.net for PocketPC : Tips and Tricks : Remote Networking
Search:

Remote Networking




Bugs found in WinCE Remote Networking.
Basil Hussain
When using Remote Networking on an HP320LX, the configuration windows will not acknowledge the Manual Dial or Show Terminal Window Before/After Dialling. A workaround for this bug is to set these options in a Terminal profile, and then they should work in a Remote Networking profile.

Compaq PCCompanion Remote Networking:PPP Setup
Bhaskar Purimetla
1. PPP and RS232C cannot run together. 2. In TCP/IP properties one has to manually set the DNS entries. Otherwise the modem connects fine but POP3 email client and PocketIE will not resolve any of the addresses.

Direct serial connection to Cisco Router/Access Server
Direct serial connection to Cisco Router/Access Server When using Direct Connection in Remote Networking, CE does a ASCII CLIENT/SERVER handshaking, and won't connect to an access server with a serial cable. To make a direct serial connection, configure a Dial-Up Connection on the HPC using Hayes-compatible modem on COM port. The Access Server has to emulate this modem to the HPC. On the Cisco access server add the following commands to the configuration used for dial-up PCs:
chat-script HPC TIMEOUT 20 ATZ OK AT OK ATE0 OK ATS7 OK ATX OK ATD CONNECT
interface ... async mode interactive
line ... script activation HPC modem InOut autocommand ppp

Problems Connecting with Windows CE Dialup Networking Product:  LanRover Access Switch /E/T v4.3.2, LanRover and NetModem v4.02
Elizabeth Gessler
3rd Party Product(s):  Windows CE dialup networking Release Date:  07/03/97 Problem: When dialing in from a palmtop computer with the Windows CE operating system, users may experience the following problems LCP negotiation problems when connecting to a Shiva remote access server.  The user may appear to be connected to the remote access server, but they are not allowed to perform any IP functions.  The connection drops after two minutes.  The remote access server log does not record the expected "protocol reject" messages for protocols other than IP. Solution: One of the following solutions can be used. 1.  Use 'Terminal Window' settings in the dialer.  The default for the CE palmtop is to use no username or password.   However, the account name being used to dial-in must have "shell access" privileges enabled in the remote access server.   On the Windows CE palmtop, edit the properties for the dialup connection document, click the modem 'Configure...' button and enable the option for "Use terminal window after dialing".  After connecting to the remote access server, press RETURN until the command prompt appears.  Enter username, password and dialback number if necessary.  When the remote access server name prompt appears, enter PPP and the screen will begin filling up with random characters.  Select 'continue' from the File menu, PPP will be negotiated and the connection will be complete. 2.  Change the default authorization protocol to PAP.  The Windows CE dialer does not negotiate SPAP.  Note that changing the default authorization protocol may prevent other PPP dialers from connecting successfully.  To change the default authorization protocol to PAP, enter the following exactly as shown into the Additional Configuration:     [PPP]     DefaultAuthProto=0xC023


All Contents Copyright (c) 2017 Bongiovanni Research & Technology, Inc.