Configuring WinTap for S60 3rd FP2 SDK

HI,

Has anyone tried configuring WinTap for S60 3rd Edition FP2 SDK? Does the E=
KA2 driver in the package work?
http://developer.symbian.com/main/to..._tap/index.js=
p
I am just not able to get the settings right,
If anyone has tried doing it, please can you share the steps?

Thanks
Bhavana

Hi [~bkunigal]

Can you please provide more details? What exactly you mean by you can't get=
the settings right?

See [Ask smart questions!|ann.jspa?annID=3D6]

Hope that helps.

Hi,=20
Thanks for the reply.

I have followed the steps that are mentioned in the readme that accompanies=
the download. Specifically:
1. I have the SDK installed
2. Installed Tap-win32 adapter.
3. Well the script that accompanies the wintap download (setuptap) did not =
work on the SDK, I had to manually run the steps which included:
1. copying the ethertap.pdd for eka2 to /release/winscw/udeb
2. modifying commDB to reflect the new interface (the script renames th=
e extension and copies the ced.cfg which is in the wintap download to wi=
nscw/c and runs ced.exe)
3. configured Tap-win32 and set the ip to 192.168.0.1. (same set at co=
mmDB)
4. Since symbian tcp/ip stack is disabled, and the emulator sees only w=
insock, I have changed ip.tcpip.esk in winscw/c/private/101f7989/esock to p=
oint to tcpip6.prt

Now, the symbian ethertap.pdd is supposed to communicate with tap-win32 and=
which inturn communicates with the windows ethernet driver.

Problem encountered is: My emulator fails to see any access point and gives=
me a "connection not availabe -26041" via web.
If an application running on emulator tries to open a connection with a win=
dows application, emulator fails to connect to the windows server with "-34=
, failed to connect"

I need to know, if the settings that I have done above is correct. Where am=
I going wrong?

Help is really appreciated.

Thanks

Hi [~bkunigal],

Great to hear that you've actually done your homework. It seems that there =
still might be a compatibility issue. There are a couple of things that I n=
eed to know:

1. The changes you made to the commdb (actually commsdat) config file that =
comes with WinTAP installer. Post it here as an attachment.

2. The ced.log file that was generated when you used ced.exe to generate th=
e new commsdat file (see \epoc32\winscw\c folder).

3. Did you setup ICS properly?

4. Have you tried using a sniffer like WireShark to see the packet activity=
on the TAP adapter?

Hope that helps.