Problem in RSocket Connect on phone
| Thu, 2005-09-01 22:31 | |
|
Hi All,
I am having this problem where the Connect call of my RSocket always returns an error KErrTimedOut (-33) on the phone, whereas in the emulator is just works fine. Also the point to note is the socket example that comes with the Symbian SDK also returns KErrTimedOut on the phone. I am able to send/receive email on the phone and also able to browse the web. Can someone please tell me as to what can be going wrong here. I thought that sending/receving mail used TCP/IP and since that was successfull, the socket connect should also be successfull. But its timing out every time. Any help would be appreciated. Thanks Karan |
|






Forum posts: 83
Forum posts: 6
http://forum.newlc.com/index.php/topic,7653.0.html
The access point name that the phone uses is "wap.voicestream.com" and the rest are default settings as follows:
Access point settings
-------------------------------
Connection name: Tmobile
Data bearer: Packet Data
Access point name: wap.voicestream.com
User name: None
Prompt password: No
Password: <empty>
Authentication: Normal
Homepage: www.google.com
Advanced settings
-------------------------------
Phone IP address: Automatic
Primary name server: 0.0.0.0
Second. name server: 0.0.0.0
Proxy serv. address: None
Proxy port number: 0
Packet Data settings
-------------------------------
Packet data connection: When available
Access point: wap.voicestream.com
Any ideas about what could be wrong here?
Thanks
Karan
Forum posts: 6
sad
Thanks
Karan
Forum posts: 83
Try to use port 80 to connect.
Look in nokia site for this IAP setting and make sure what they are correct.
Forum posts: 6
Thansk
Karan
Forum posts: 83
Forum posts: 20
tell me one thing. Do you get (dns) host resolution when you ping google.com using the SDK sockets example?? If yes, then the app is connecting to the DNS(via your operators gateway of course) and the prob is with TCP sockets support from current access point . Timed out error is typical of lack of TCP sockets support from current access point.
Operators generally differentiate between WAP access point and internet access point and using sockets isnt supported on WAP only access point.
Another thing you can try out is using WAP stack. That should work with WAP access point
Abhinav