My PDA doesn't communicate with LAN when connected in acti..

On 24 Óåðô, 07:26, "Sven" <sejohann....TakeThisOut@hotmail.com> wrote:
> My guess is there is some firewall setting at the client's site that is
> causing you issues. Even on your own LAN the PPC will have an IP of
> 192.168.55.101. The PC will be seen as 192.168.55.100 within the ActiveSync
> connection. That's just how it is always set up. AS acts as a partial router
> to bridge your network to the little two node network established by AS.
> Sometimes firewalls or other security settings will see that as a foreign
> network and block traffic. No you can't change the IPs in AS, but hopefully
> you can use this to start looking for a fix.
>
>

So you mean that my PDA will be seen from outside as having my
computer's IP?

In my case I connect the PDA to my laptop in my office and it works.
But in my client's office even with my own same laptop (with no
firewall) it cannot connect. But I can see my PDA through activesync.
The problem is that AS doesn't see the rest of the world.

Oh, didn't get the problem quite right. At the client site you are hooking
the PDA to your PC via AS and connecting your PC to the client's LAN? is
that right? I am assuming that you can get to your server from your laptop
while it is connected to the client's lan, right?

For your first line though, yea. The PDA will not be seen as having an
address of it's own, The AS bit acts much like a network address translation
like you would see on a home router. Everything looks like it comes from the
IP assigned to the router by the ISP from the outside. That is one reason
you can't get to the PDA from the LAN while it is connected via AS. You
would have to be able to turn on some sort of DMZ or port forwarding, which
doesn't exist in AS.

You might want to pick up some sort of network tools for the PDA to see what
subnet mask and gateway are being picked up, and what the client PCs are set
to. With the two different subnets ( 1 and 40) it might not have the right
ones to get out of your PC and out the gateway/router.

http://www.cam.com/windowsce.html has some great stuff. Worth the price
IMHO, but they allow trials so you can decide yourself.


"HK" <hkosmidi DeleteThis @gmail.com> wrote in message
news:93207141-d469-4f46-b184-8fbb75d4384d@p15g2000vbl.googlegroups.com...
On 24 Óåðô, 07:26, "Sven" <sejohann... DeleteThis @hotmail.com> wrote:
> My guess is there is some firewall setting at the client's site that is
> causing you issues. Even on your own LAN the PPC will have an IP of
> 192.168.55.101. The PC will be seen as 192.168.55.100 within the
> ActiveSync
> connection. That's just how it is always set up. AS acts as a partial
> router
> to bridge your network to the little two node network established by AS.
> Sometimes firewalls or other security settings will see that as a foreign
> network and block traffic. No you can't change the IPs in AS, but
> hopefully
> you can use this to start looking for a fix.
>
>

So you mean that my PDA will be seen from outside as having my
computer's IP?

In my case I connect the PDA to my laptop in my office and it works.
But in my client's office even with my own same laptop (with no
firewall) it cannot connect. But I can see my PDA through activesync.
The problem is that AS doesn't see the rest of the world.

On 25 Óåðô, 05:46, "Sven" <sejohann....TakeThisOut@hotmail.com> wrote:
> Oh, didn't get the problem quite right. At the client site you are hooking
> the PDA to your PC via AS and connecting your PC to the client's LAN? is
> that right?

correct!

> I am assuming that you can get to your server from your laptop
> while it is connected to the client's lan, right?

correct

>
> For your first line though, yea. The PDA will not be seen as having an
> address of it's own, The AS bit acts much like a network address translation
> like you would see on a home router. Everything looks like it comes from the
> IP assigned to the router by the ISP from the outside. That is one reason
> you can't get to the PDA from the LAN while it is connected via AS. You
> would have to be able to turn on some sort of DMZ or port forwarding, which
> doesn't exist in AS.

The problem is that my laptop connecto to the LAN server, while the
PDA connecto to my laptop through AS cannot connect.
Since my PDA is seen as having the same IP as my laptop it shouldn't
be a problem connectin to the server. But it doesn't

"HK" <hkosmidi.DeleteThis@gmail.com> wrote in message
news:0eaa199c-2e28-4937-8ca7-47535cdb78d1@d21g2000vbm.googlegroups.com...
On 25 Óåðô, 05:46, "Sven" <sejohann....DeleteThis@hotmail.com> wrote:

>The problem is that my laptop connecto to the LAN server, while the
>PDA connecto to my laptop through AS cannot connect.
>Since my PDA is seen as having the same IP as my laptop it shouldn't
>be a problem connectin to the server. But it doesn't

Yea, but requests from the PPC, need to be translated by AS to be forwarded
out the laptop to the client gateway, to your server, and back. Again to be
translated through your laptop to the PPC. Can't tell you exactly what the
addresses in the PPC, gateway, subnet mask should be, given that the network
you are connecting to is more enterprise than I am comfortable with, having
multiple subnets, or a subnet with a mask other than 255.255.255.0. However,
getting an IP utility and looking at what those values are on the PPC when
on your home (office) network, and what they do on the client network, may
point you to a solution.