Socket Connect works on LAN but not WAN.

From: George Mitchell (peekandpoke_at_hotmail.com)
Date: 02/15/05 

Date: Mon, 14 Feb 2005 19:31:05 -0800

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

Relevant Pages

  • RE: Using kerberosSecurity Throws Security Exception
    ... I am experiencing this error while trying to use a Windows XP client ... application to access a web service located on a W2k3 server. ... client app on the server, ... > Account with a Custom Principal Name using SetSPN.exe utility. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Questions about Remoting, objects, threading. lease lifetime and object cleanup, and a couple of
    ... so long as the Client app is ... always refering to the same server object. ... it sets its ClassOne object to nothing and goes away. ... >>The client app at some point is going to become an ASP.Net app also. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Remoting or windows service
    ... Thanks for writing up such a decent overview of the remoting dev process ... the client and the server. ... > 2) Implement this class in the server app and say that it can be accessed ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Schannel and Session Renegotiation
    ... Schannel does not support the server sending app ... We are discussing the option of providing support for the client blowing off ...
    (microsoft.public.platformsdk.security)
  • Re: Getting Events, for Windows Service
    ... else tries to run my client app he gets an timeout error. ... The server application has a public object called logger, ... So it seems that the logger is properly instantiated and works. ...
    (microsoft.public.dotnet.framework.remoting)