Re: TCP Sockets over Wireless

You can't communicate over wireless while the device is in the cradle.
That's the way Windows Mobile 5 devices work. You haven't given us any
specifics about versions, either of the .NET CF or of the device.

Allowing traffic through a given port doesn't have side-effects like that on
any firewall that I've ever seen. What firewall are you using? Where is it
running in the network infrastructure? Again, this works *just fine*, no
problems, no errors, nothing unexpected. Your network or your code on the
PC is doing something wrong. Is the PC code .NET, also?

Paul T.

"JonF" <jf02@xxxxxxxxxxxx> wrote in message
news:1149269550.307382.164570@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Also one of the strange side effects, if the wireless adaptor is
enabled then the connection cannot be made, while if it is disabled the
connection is fine (while in the cradle obviously).

JonF wrote:
The PocketPC is connected fine, can browse the internet etc... I have
added a firewall rule which explicitly allows TCP traffic between
devices on the required port however that didn't help and had the
annoying side effect of blocking other traffic - in short I can't be
bothered to setup a proper set of firewall rules for a domestic
router...

Although I can still demo the project without the network functionality
it would be very useful...

Paul G. Tobey [eMVP] wrote:
DNS is *not used* to resolve anything when IP addresses are used.

I'm guessing firewall, as Chris mentioned. Works fine for me.

Paul T.


"JonF" <jf02@xxxxxxxxxxxx> wrote in message
news:1149259437.038135.38050@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am working with C# compact framework and have written some code
which
allows communication over the socket layer, however I have
encountered
the strange problem that I can only communicate over a physical dock
connection not WiFi. At the moment I have set the IP to be
192.168.0.4
which is the address my laptop running the server which the PocketPC
is
trying to connect to.

I'm using the following code:

private string svraddress;
private int svrport;
private Socket connection;

IPEndPoint ip = new IPEndPoint(IPAddress.Parse(svraddress), svrport);
connection = new Socket(AddressFamily.InterNetwork,
SocketType.Stream,
ProtocolType.Tcp);
connection.Connect(ip);
connection.Send(data);

I'm guessing that this may be some sort of DNS problem with resolving
the local network IP?

Any ideas/pointers appreciated...




.

Relevant Pages

  • Re: Still cant connect to RWW or OWA remotely
    ... No, I don't have a 3rd party firewall, and it's a pretty plain vanilla WinXP ... Connected to the network like the other workstations, ... I could go to any workstation and connect to them just fine. ... match the broadband connection, the two NIC firewall, the remote ...
    (microsoft.public.windows.server.sbs)
  • Re: Workgroup is not accessible.
    ... The only network connection with the ... firewall set was the dial-up connection, ... Even when it accesses the workgroup, ...
    (microsoft.public.windowsxp.network_web)
  • RE: Serious Security Issue in Windows XP SP2s Firewall
    ... file and printer sharing is available for network login from any network (I ... Internet Connection Sharing of the PC has to be disabled." ... Serious Security Issue in Windows XP SP2's Firewall ...
    (Focus-Microsoft)
  • RE: Lost Internet Connectivity
    ... use network diagnostic tools, i.e. ipconfig, ping, etc. ... Firewall, McAfee Personal Firewall, VS, two-PC network, Motorola modem, ... PCI 10/100 Ethernet Connection. ... Windows Firewall/ICS Service not running, ...
    (microsoft.public.windowsxp.network_web)
  • Re: 32-bit TCP/IP Connection
    ... try the uninstall on MCAfee yet. ... Regarding my Network conncections though - first off, ... When I right-click on AOL only the AOL connection setup screen pops-up. ... have the Microsoft XP Firewall turned on, I do use SpyBot S & D, AdAware SE ...
    (microsoft.public.windowsxp.help_and_support)