Archived from groups: microsoft.public.pocketpc (More info?)
I have a Samsung i700 with Verizon service. I have many clients that I
connect to via terminal Services and Remote Desktop. I am sucessfull
connecting to all of these servers from computers or laptops. When I try to
connect via Terminal Services from the phone almost every connection times
out. What would be different connecting from a regular pc vs the phone?
Let me say that all of these clients have a hardware firewall using NAT but,
I do have port 3389 open.
Archived from groups: microsoft.public.pocketpc (More info?)
"Aztech" <Aztech@discussions.microsoft.com> wrote in message
news:A6DB8090-C4C9-4F4A-97E6-CA44F2E79E52@microsoft.com...
>I have a Samsung i700 with Verizon service. I have many clients that I
> connect to via terminal Services and Remote Desktop. I am sucessfull
> connecting to all of these servers from computers or laptops. When I try
> to
> connect via Terminal Services from the phone almost every connection times
> out. What would be different connecting from a regular pc vs the phone?
>
> Let me say that all of these clients have a hardware firewall using NAT
> but,
> I do have port 3389 open.
hmm... pretty vague.
is it trouble with the vpn or the RD?
Could you mention what type of vpn you are trying to connect to?
Have you searched the group for similar trouble and made sure to add the
internal ip to the exceptions list?
Archived from groups: microsoft.public.pocketpc (More info?)
This is a problem with RD. The internal IP is on the exceptions list as I am
able to use RD to connect from any remote PC to the servers. This only seems
to be a problem when connecting from mobile devices.
"Chance Hopkins" wrote:
>
> "Aztech" <Aztech@discussions.microsoft.com> wrote in message
> news:A6DB8090-C4C9-4F4A-97E6-CA44F2E79E52@microsoft.com...
> >I have a Samsung i700 with Verizon service. I have many clients that I
> > connect to via terminal Services and Remote Desktop. I am sucessfull
> > connecting to all of these servers from computers or laptops. When I try
> > to
> > connect via Terminal Services from the phone almost every connection times
> > out. What would be different connecting from a regular pc vs the phone?
> >
> > Let me say that all of these clients have a hardware firewall using NAT
> > but,
> > I do have port 3389 open.
>
>
> hmm... pretty vague.
>
> is it trouble with the vpn or the RD?
>
> Could you mention what type of vpn you are trying to connect to?
>
> Have you searched the group for similar trouble and made sure to add the
> internal ip to the exceptions list?
>
>
>
>
Archived from groups: microsoft.public.pocketpc (More info?)
"Aztech" <Aztech@discussions.microsoft.com> wrote in message
news:975E5672-ACA6-4B40-A628-B8CD0809AAFF@microsoft.com...
> This is a problem with RD.
ok, I'll take your word for it.
> The internal IP is on the exceptions list as I am
> able to use RD to connect from any remote PC to the servers.
Sorry, this doesn't make sense.
>This only seems
> to be a problem when connecting from mobile devices.
Understood, make sure the gateway address for the vpn is in the vpn
exception list on the mobile device.
Your qualifying logic on the previous statement is incorrect. "as I am able
to use RD to connect from any remote PC to the servers" does not mean "The
internal IP is on the exceptions list" for the mobile device. It means the
vpn on the server is set up correctly on the server for a desktop, nothing
else.
>
> "Chance Hopkins" wrote:
>
>>
>> "Aztech" <Aztech@discussions.microsoft.com> wrote in message
>> news:A6DB8090-C4C9-4F4A-97E6-CA44F2E79E52@microsoft.com...
>> >I have a Samsung i700 with Verizon service. I have many clients that I
>> > connect to via terminal Services and Remote Desktop. I am sucessfull
>> > connecting to all of these servers from computers or laptops. When I
>> > try
>> > to
>> > connect via Terminal Services from the phone almost every connection
>> > times
>> > out. What would be different connecting from a regular pc vs the phone?
>> >
>> > Let me say that all of these clients have a hardware firewall using NAT
>> > but,
>> > I do have port 3389 open.
>>
>>
>> hmm... pretty vague.
>>
>> is it trouble with the vpn or the RD?
>>
>> Could you mention what type of vpn you are trying to connect to?
>>
>> Have you searched the group for similar trouble and made sure to add the
>> internal ip to the exceptions list?
>>
>>
>>
>>
