7 Nokia Corporation - initial contribution. |
7 Nokia Corporation - initial contribution. |
8 Contributors: |
8 Contributors: |
9 --> |
9 --> |
10 <!DOCTYPE concept |
10 <!DOCTYPE concept |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
12 <concept id="GUID-A5C95115-2083-589C-BC82-906AB0DE5A38" xml:lang="en"><title>Troubleshooting |
12 <concept id="GUID-A5C95115-2083-589C-BC82-906AB0DE5A38" xml:lang="en"><title>Troubleshooting guide</title><shortdesc>Common errors and solutions to avoid whilst using ethernet.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
13 guide</title><shortdesc>Common errors and solutions to avoid whilst using ethernet.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
14 <p>The following may help if you have trouble connecting the emulator: </p> |
13 <p>The following may help if you have trouble connecting the emulator: </p> |
15 <section id="GUID-E576CB5D-B796-49E9-A510-5F498674B7E0"><title>Specific errors</title> <dl> |
14 <section id="GUID-E576CB5D-B796-49E9-A510-5F498674B7E0"><title>Specific |
|
15 errors</title> <dl> |
16 <dlentry> |
16 <dlentry> |
17 <dt><b>HttpExampleClient.exe reports error -1</b> </dt> |
17 <dt><b>HttpExampleClient.exe reports error -1</b> </dt> |
18 <dd><p>In most cases <systemoutput>-1</systemoutput> indicates that the current |
18 <dd><p>In most cases <systemoutput>-1</systemoutput> indicates that |
19 comms database is not compatible with the emulator. </p> <p>The best way to |
19 the current comms database is not compatible with the emulator. </p> <p>The best way to avoid trouble is to use the <xref href="GUID-3C6935E1-66C9-5115-901E-D3B1D0C2E783.dita">Quick ethernet configuration</xref>. Ensure that the <codeph>IAP</codeph>, <codeph>LANBearer</codeph> and <codeph>LANService</codeph> tables are set up exactly as indicated. </p> </dd> |
20 avoid trouble is to use the <xref href="GUID-3C6935E1-66C9-5115-901E-D3B1D0C2E783.dita">Quick |
|
21 ethernet configuration</xref>. Ensure that the <codeph>IAP</codeph>, <codeph>LANBearer</codeph> and <codeph>LANService</codeph> tables |
|
22 are set up exactly as indicated. </p> </dd> |
|
23 </dlentry> |
20 </dlentry> |
24 <dlentry> |
21 <dlentry> |
25 <dt><b>HttpExampleClient.exe reports error -5120</b> </dt> |
22 <dt><b>HttpExampleClient.exe reports error -5120</b> </dt> |
26 <dd><p>This error indicates that the URL cannot be resolved to an IP address. |
23 <dd><p>This error indicates that the URL cannot be resolved to an |
27 This is usually caused by a problem with DNS; either the location of the DNS |
24 IP address. This is usually caused by a problem with DNS; either the |
28 server is incorrectly specified or there is no DNS server. </p> <p>If using |
25 location of the DNS server is incorrectly specified or there is no |
29 a statically allocated DNS address, check that the value in your comms database's <codeph>LANService</codeph> table |
26 DNS server. </p> <p>If using a statically allocated DNS address, check |
30 is correct for your network. </p> </dd> |
27 that the value in your comms database's <codeph>LANService</codeph> table is correct for your network. </p> </dd> |
31 </dlentry> |
28 </dlentry> |
32 <dlentry> |
29 <dlentry> |
33 <dt><b>Windows reports that there is an IP address conflict</b> </dt> |
30 <dt><b>Windows reports that there is an IP address conflict</b> </dt> |
34 <dd><p>The likely cause is that the (static) IP address of your emulator is |
31 <dd><p>The likely cause is that the (static) IP address of your emulator |
35 the same as that of your computer. This will not occur if your IP addresses |
32 is the same as that of your computer. This will not occur if your |
36 are dynamically allocated. </p> <p>The solution is to ensure that the emulator |
33 IP addresses are dynamically allocated. </p> <p>The solution is to |
37 is allocated a unique IP address in the <codeph>LANService</codeph> table |
34 ensure that the emulator is allocated a unique IP address in the <codeph>LANService</codeph> table of the comms database configuration file. </p> </dd> |
38 of the comms database configuration file. </p> </dd> |
|
39 </dlentry> |
35 </dlentry> |
40 </dl> </section> |
36 </dl> </section> |
41 <section id="GUID-03CA9CE3-2262-406F-949A-83611A89F91E"><title>Checklist</title> <ul> |
37 <section id="GUID-03CA9CE3-2262-406F-949A-83611A89F91E"><title>Checklist</title> <ul> |
42 <li id="GUID-2CAEC3B6-C3A4-5AF7-A72C-2EFE217C8E6A"><p>Ensure only one copy |
38 <li id="GUID-2CAEC3B6-C3A4-5AF7-A72C-2EFE217C8E6A"><p>Ensure only |
43 of <i>WinPcap</i> is installed. Version 4.0 is known to work with Symbian |
39 one copy of <i>WinPcap</i> is installed. Version 4.0 is known to work |
44 platform </p> </li> |
40 with Symbian platform </p> </li> |
45 <li id="GUID-0425F662-A42E-52D2-BA1A-A60D54C5FD6F"><p>For EKA1 kernel, ensure <filepath>etherdriver.dat</filepath> and <filepath>ethermac.dat</filepath> are in <filepath>\epoc32\<wins or winscw>\c\system\data\</filepath> </p> <p>For |
41 <li id="GUID-0425F662-A42E-52D2-BA1A-A60D54C5FD6F"><p>For EKA1 kernel, |
46 EKA2 kernel, ensure that the file <filepath>\epoc32\data\epoc.ini</filepath> exists </p> </li> |
42 ensure <filepath>etherdriver.dat</filepath> and <filepath>ethermac.dat</filepath> are in <filepath>\epoc32\<wins or winscw>\c\system\data\</filepath> </p> <p>For EKA2 kernel, ensure that the file <filepath>\epoc32\data\epoc.ini</filepath> exists </p> </li> |
47 <li id="GUID-F708C504-C4CF-5877-91CA-86ECF08718ED"><p>For EKA 1, verify the |
43 <li id="GUID-F708C504-C4CF-5877-91CA-86ECF08718ED"><p>For EKA 1, verify |
48 contents of <filepath>etherdriver.dat</filepath>. The file should contain |
44 the contents of <filepath>etherdriver.dat</filepath>. The file should |
49 a string that resembles a Windows registry key. For example: </p> <codeblock id="GUID-CBBF49DA-7FC8-5371-A523-A1DD15607859" xml:space="preserve">\Device\NPF_{A2E3CC5B-AD54-4F47-BE93-2C3E06}</codeblock> </li> |
45 contain a string that resembles a Windows registry key. For example: </p> <codeblock id="GUID-CBBF49DA-7FC8-5371-A523-A1DD15607859" xml:space="preserve">\Device\NPF_{A2E3CC5B-AD54-4F47-BE93-2C3E06}</codeblock> </li> |
50 <li id="GUID-8EC69637-EAF5-5A69-8B88-42C7106FF3E2"><p>For EKA 1, ensure <filepath>ethermac.dat</filepath> contains |
46 <li id="GUID-8EC69637-EAF5-5A69-8B88-42C7106FF3E2"><p>For EKA 1, ensure <filepath>ethermac.dat</filepath> contains a valid MAC address and there is |
51 a valid MAC address and there is no line-break at the end of the file. The |
47 no line-break at the end of the file. The MAC address should only |
52 MAC address should only contain numbers and letters, no hyphens </p> </li> |
48 contain numbers and letters, no hyphens </p> </li> |
53 <li id="GUID-97F7074E-066D-5680-ADFF-36D0D15247AB"><p>Be careful not to confuse <filepath>etherdriver.dat</filepath> with <filepath>ethermac.dat</filepath> </p> </li> |
49 <li id="GUID-97F7074E-066D-5680-ADFF-36D0D15247AB"><p>Be careful not |
54 <li id="GUID-269F2760-A117-54B8-BE02-DC7D32CB6339"><p>For EKA2, ensure that <filepath>\epoc32\data\epoc.ini</filepath> contains |
50 to confuse <filepath>etherdriver.dat</filepath> with <filepath>ethermac.dat</filepath> </p> </li> |
55 something similar to: </p> <codeblock id="GUID-0852E30B-C0C3-56D6-8B8A-68D35B3F8ABB" xml:space="preserve">ETHER_NIF=\Device\NPF_{8A2D1EEF-A264-49CF-A681-6BFFB7608F48} |
51 <li id="GUID-269F2760-A117-54B8-BE02-DC7D32CB6339"><p>For EKA2, ensure |
|
52 that <filepath>\epoc32\data\epoc.ini</filepath> contains something |
|
53 similar to: </p> <codeblock id="GUID-0852E30B-C0C3-56D6-8B8A-68D35B3F8ABB" xml:space="preserve">ETHER_NIF=\Device\NPF_{8A2D1EEF-A264-49CF-A681-6BFFB7608F48} |
56 ETHER_MAC=0202a5b856c9 |
54 ETHER_MAC=0202a5b856c9 |
57 ETHER_SPEED=10Mbps</codeblock> </li> |
55 ETHER_SPEED=10Mbps</codeblock> </li> |
58 </ul> </section> |
56 </ul> </section> |
59 <section id="GUID-B2F39D70-044C-4012-A148-4ED912CA15F1"><title>Debug information</title> <ul> |
57 <section id="GUID-B2F39D70-044C-4012-A148-4ED912CA15F1"><title>Debug |
60 <li id="GUID-6F534892-4770-5E64-8B93-36C1315F05B6"><p>When using a debug build, |
58 information</title> <ul> |
61 the Symbian platform ethernet software writes log files to the <filepath>c:\logs\log.txt</filepath> file. |
59 <li id="GUID-6F534892-4770-5E64-8B93-36C1315F05B6"><p>When using a |
62 This file is in your Symbian platform platform's C drive, such as <filepath>\epoc32\winscw\c</filepath> </p> </li> |
60 debug build, the Symbian platform ethernet software writes log files |
63 <li id="GUID-F83012C2-9303-5CE6-8CAB-6DE5D36ECF51"><p> <i>Ethereal</i> is |
61 to the <filepath>c:\logs\log.txt</filepath> file. This file is in |
64 an open-source protocol analyser that can be used to capture traffic from |
62 your Symbian platform platform's C drive, such as <filepath>\epoc32\winscw\c</filepath> </p> </li> |
65 the adapter; see <xref href="www.ethereal.com" scope="external">www.ethereal.com</xref>. |
63 <li id="GUID-F83012C2-9303-5CE6-8CAB-6DE5D36ECF51"><p> <i>Ethereal</i> is an open-source protocol analyser that can be used to capture |
66 It can be especially useful in tracking down problems with the DHCP negotiation </p> </li> |
64 traffic from the adapter; see <xref href="http://www.ethereal.com/" scope="external">www.ethereal.com</xref>. It can be especially useful in tracking down problems with the |
67 <li id="GUID-2ADD828B-0EA9-5F74-8008-F50F6B6DFBAB"><p>When developing with |
65 DHCP negotiation </p> </li> |
68 Microsoft tools, the MSDEV output window shows each packet sent and received |
66 <li id="GUID-2ADD828B-0EA9-5F74-8008-F50F6B6DFBAB"><p>When developing |
69 by the Symbian platformethernet driver. </p> </li> |
67 with Microsoft tools, the MSDEV output window shows each packet sent |
|
68 and received by the Symbian platformethernet driver. </p> </li> |
70 </ul> </section> |
69 </ul> </section> |
71 </conbody></concept> |
70 </conbody></concept> |