Socket Connect works on LAN but not WAN.

[George Mitchell]

I'm not sure if this is the right forum for this question, but I'm hoping
someone could shed some light on the issue I'm having.

I have written a client-server app where the server is a Win32 app using
winsock running on WinXP SP2. The client runs on a pocket pc using the .NET
CF. Everything works great when I try to connect to my server from my
Pocket PC using the local IP address (192.168.1.100). However, when I try
to connect to the server from outside my LAN using an actual IP address, the
client cannot find it. Initially I thought that I may not have configured
my router correctly, so to double check, I wrote a simple Console version of
the app that runs on windows using the full framework, and it could connect
no problem using the actual IP. So I believe that the issue isn't with my
router.

Why would the same Connect call work in the full .NET framework version of
the Socket class and not the compact version? Do I need to configure
something differently on my pocket pc? Any insights would be greatly
appreciated.

George

 

[Koen Mannaerts]

George,

This should work without a problem.
I would use a network monitor to see what exactly the handheld attempts
to do. Perhaps its subnet mask or default gateway isn't correctly
configured?

Koen.

 

[Guest]

I've got the simulairy problem,. When connected with ActiveSync it works fine
but, when i want to connect by WiFi it won't happen to be conncted, although
conneting with the FTP sever works well when i'm using InternerExplorer on
then PocketPC.
The Socket Error i get says "no such Host" strange.

Any idee?