Troubleshooting -guide

The following may help if you have trouble connecting the emulator:

Specific errors

HttpExampleClient.exe reports error -1: In most cases -1 indicates that the current -comms database is not compatible with the emulator.

The best way to -avoid trouble is to use the Quick -ethernet configuration. Ensure that the IAP, LANBearer and LANService tables -are set up exactly as indicated.
HttpExampleClient.exe reports error -5120: This error indicates that the URL cannot be resolved to an IP address. -This is usually caused by a problem with DNS; either the location of the DNS -server is incorrectly specified or there is no DNS server.

If using -a statically allocated DNS address, check that the value in your comms database's LANService table -is correct for your network.
Windows reports that there is an IP address conflict: The likely cause is that the (static) IP address of your emulator is -the same as that of your computer. This will not occur if your IP addresses -are dynamically allocated.

The solution is to ensure that the emulator -is allocated a unique IP address in the LANService table -of the comms database configuration file.

Checklist

Ensure only one copy -of WinPcap is installed. Version 4.0 is known to work with Symbian -platform
For EKA1 kernel, ensure etherdriver.dat and ethermac.dat are in \epoc32\<wins or winscw>\c\system\data\

For -EKA2 kernel, ensure that the file \epoc32\data\epoc.ini exists
For EKA 1, verify the -contents of etherdriver.dat. The file should contain -a string that resembles a Windows registry key. For example:
\Device\NPF_{A2E3CC5B-AD54-4F47-BE93-2C3E06}
For EKA 1, ensure ethermac.dat contains -a valid MAC address and there is no line-break at the end of the file. The -MAC address should only contain numbers and letters, no hyphens
Be careful not to confuse etherdriver.dat with ethermac.dat
For EKA2, ensure that \epoc32\data\epoc.ini contains -something similar to:
ETHER_NIF=\Device\NPF_{8A2D1EEF-A264-49CF-A681-6BFFB7608F48} - ETHER_MAC=0202a5b856c9 - ETHER_SPEED=10Mbps

Debug information

When using a debug build, -the Symbian platform ethernet software writes log files to the c:\logs\log.txt file. -This file is in your Symbian platform platform's C drive, such as \epoc32\winscw\c
Ethereal is -an open-source protocol analyser that can be used to capture traffic from -the adapter; see www.ethereal.com. -It can be especially useful in tracking down problems with the DHCP negotiation
When developing with -Microsoft tools, the MSDEV output window shows each packet sent and received -by the Symbian platformethernet driver.

+ + + + + +Troubleshooting guideCommon errors and solutions to avoid whilst using ethernet. +

The following may help if you have trouble connecting the emulator:

Specific +errors

HttpExampleClient.exe reports error -1: In most cases -1 indicates that +the current comms database is not compatible with the emulator.

The best way to avoid trouble is to use the Quick ethernet configuration. Ensure that the IAP, LANBearer and LANService tables are set up exactly as indicated.
HttpExampleClient.exe reports error -5120: This error indicates that the URL cannot be resolved to an +IP address. This is usually caused by a problem with DNS; either the +location of the DNS server is incorrectly specified or there is no +DNS server.

If using a statically allocated DNS address, check +that the value in your comms database's LANService table is correct for your network.
Windows reports that there is an IP address conflict: The likely cause is that the (static) IP address of your emulator +is the same as that of your computer. This will not occur if your +IP addresses are dynamically allocated.

The solution is to +ensure that the emulator is allocated a unique IP address in the LANService table of the comms database configuration file.

Checklist

Ensure only +one copy of WinPcap is installed. Version 4.0 is known to work +with Symbian platform
For EKA1 kernel, +ensure etherdriver.dat and ethermac.dat are in \epoc32\<wins or winscw>\c\system\data\

For EKA2 kernel, ensure that the file \epoc32\data\epoc.ini exists
For EKA 1, verify +the contents of etherdriver.dat. The file should +contain a string that resembles a Windows registry key. For example:
\Device\NPF_{A2E3CC5B-AD54-4F47-BE93-2C3E06}
For EKA 1, ensure ethermac.dat contains a valid MAC address and there is +no line-break at the end of the file. The MAC address should only +contain numbers and letters, no hyphens
Be careful not +to confuse etherdriver.dat with ethermac.dat
For EKA2, ensure +that \epoc32\data\epoc.ini contains something +similar to:
ETHER_NIF=\Device\NPF_{8A2D1EEF-A264-49CF-A681-6BFFB7608F48} + ETHER_MAC=0202a5b856c9 + ETHER_SPEED=10Mbps

Debug +information

When using a +debug build, the Symbian platform ethernet software writes log files +to the c:\logs\log.txt file. This file is in +your Symbian platform platform's C drive, such as \epoc32\winscw\c
Ethereal is an open-source protocol analyser that can be used to capture +traffic from the adapter; see www.ethereal.com. It can be especially useful in tracking down problems with the +DHCP negotiation
When developing +with Microsoft tools, the MSDEV output window shows each packet sent +and received by the Symbian platformethernet driver.

\ No newline at end of file