Home > Archive > Smartphone Developer Forum > October 2005 > TcpClient problem with Passthrough
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
TcpClient problem with Passthrough
|
|
| NickFel 2005-10-18, 7:04 pm |
| I'm working on my own Smartphone MSN Messenger client, and finding some odd
behaviour while trying to make TCP connections.
For anyone who's never looked at the MSN Protocol, you start off by
connecting to messenger.hotmail.com, and it directs you to a second server
which will handle your session.
Typical example: 207.46.4.40:1863.
When using a Pass-Through connection, I can connect to the first server
using TcpClient, but always get "No such host is known" connecting to the
second.
Using GPRS, the client can connect just fine. Running more or less the same
code on a PC connects too... the problem is only with Pass-Through.
Any suggestions?
Thank you.
| |
|
| NickFel wrote:
> I'm working on my own Smartphone MSN Messenger client, and finding some odd
> behaviour while trying to make TCP connections.
>
> For anyone who's never looked at the MSN Protocol, you start off by
> connecting to messenger.hotmail.com, and it directs you to a second server
> which will handle your session.
>
> Typical example: 207.46.4.40:1863.
>
> When using a Pass-Through connection, I can connect to the first server
> using TcpClient, but always get "No such host is known" connecting to the
> second.
>
> Using GPRS, the client can connect just fine. Running more or less the same
> code on a PC connects too... the problem is only with Pass-Through.
>
try changing the 'your computer is connected to:' setting in activesync.
what is it set to now?
riki
Travel important today; IRS arrives tomorrow.
By Night:
ThemeChanger for Smartphone : http://homepages.inspire.net.nz/~gambit/
AbstractStart for Smartphone :
http://homepages.inspire.net.nz/~gambit/AbstractStart/
By Day: http://www.EmbeddedFusion.com
| |
|
|
| NickFel 2005-10-19, 7:59 am |
| > oh wait thats not the problem. are you writing it native or managed? I
> know i had an issue in managed land, whereby one API would work well on
> a name, whereas another worked well on IP addresses.
Managed, working with the TcpClient class in C#
| |
|
|
| NickFel 2005-10-19, 7:02 pm |
| Hrm... I can only find a Ping class in Framework 2.0. Anything I could use in
1.1?
"riki" wrote:
> can you try a look up using a few other API's? eg try a ping and ... ahh
> can't remember I'm sure theres a few others.
| |
| NickFel 2005-10-20, 7:01 pm |
| Fixed it!
If you're interested, the problem turned out to be with passing a string IP
address to TcpClient for connection. This attemps a reverse DNS lookup, which
is apparently not possible through ActiveSync.
Parsing the IP into an IPEndPoint works fine.
|
|
|
|
|