Terminal Services

Archived from groups: microsoft.public.pocketpc (More info?)

Hi,
I never got a response after this. Could someone please help?
_____________________________________________________________

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?)

You can also set at the router a Virtual server that assigns the port of the
remote desktop (3389) to this internal NAT address.

--
Helio Diamant
MS-MVP/Mobile Devices
www.pocketpcfreak.com

"Eric Hicks [MVP]" <i'm@home.with.u> wrote in message
news:uIwKxqldFHA.3712@TK2MSFTNGP12.phx.gbl...
> You can't connect to an internal ip of a computer that sits on the other
> side of a nat firewall. You will either need to use the external IP of
> the machine or us vpn to get to the internal network.
>
> --
> --
> Eric Hicks [That_Kid] (MS-MVP Mobile Devices)
>
> The MS-MVP Program - http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no
> rights...
>
> "Aztech" <Aztech@discussions.microsoft.com> wrote in message
> news:97144353-B247-4867-AE99-D00023A3EC5B@microsoft.com...
>> Hi,
>> I never got a response after this. Could someone please help?
>> _____________________________________________________________
>>
>> 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?)

I am using the external public address to connect but it times out. I am
saying that from a remote PC I am able to connect to the server using the
public IP address of the server (we are using 1 to 1 NAT) and I have port
3389 open. I can connect from a PC but not from the PDA using the same public
IP address or FQDN.

"Sooner Al [MVP]" wrote:

> You can also a different port than the default TCP Port 3389 by hacking the registry on the Pocket
> device. See the end of this page for more information...
>
> http://theillustratednetwork.mvps. [...] oting.html
>
> --
>
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
> The MS-MVP Program - http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no rights...
>
>
> "Helio Diamant - MS-MVP/Mobile Devices" <helio@nospam.pocketpcfreak.com> wrote in message
> news:egvVqxmdFHA.1600@tk2msftngp13.phx.gbl...
> > You can also set at the router a Virtual server that assigns the port of the remote desktop (3389)
> > to this internal NAT address.
> >
> > --
> > Helio Diamant
> > MS-MVP/Mobile Devices
> > www.pocketpcfreak.com
> >
> > "Eric Hicks [MVP]" <i'm@home.with.u> wrote in message
> > news:uIwKxqldFHA.3712@TK2MSFTNGP12.phx.gbl...
> >> You can't connect to an internal ip of a computer that sits on the other side of a nat firewall.
> >> You will either need to use the external IP of the machine or us vpn to get to the internal
> >> network.
> >>
> >> --
> >> --
> >> Eric Hicks [That_Kid] (MS-MVP Mobile Devices)
> >>
> >> The MS-MVP Program - http://mvp.support.microsoft.com
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights...
> >>
> >> "Aztech" <Aztech@discussions.microsoft.com> wrote in message
> >> news:97144353-B247-4867-AE99-D00023A3EC5B@microsoft.com...
> >>> Hi,
> >>> I never got a response after this. Could someone please help?
> >>> _____________________________________________________________
> >>>
> >>> 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?
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>
> >>
> >
> >
>
>
>