Archived from groups: microsoft.public.pocketpc (More info?)
Hello,
I am trying to open with my Pocket PC (Windows Mobile 2003) a terminal
services connexion to a Windows terminal server in our company using a VPN
connexion.
The VPN seems to work fine. On the VPN server (Microsoft ISA 2004) I see the
VPN client connected. When I then open the Terminal client on the Pocket PC
there is no way to connect to a terminal server: always "host not found"
message. Same thing when I use an IP address instead of the server name.
With a Windows terminal client (i.e. Remote Desktop from Windows XP), there
is no problem.
Archived from groups: microsoft.public.pocketpc (More info?)
The PPC has no way to resolve the name of your terminal server, you can
plugin the IP address and that should work. However, you could always set up
PocketHosts (http://www.zimac.de/cestuff.htm) and add an enter for your
termserv with the correct IP address.
"When a man sits with a pretty girl for an hour, it seems like a minute. But
let him sit on a hot stove for a minute and it's longer than any hour.
That's relativity." - Albert Einstein
"Ezechiel Darvas" <edarvas@hotmail.com> wrote in message
newsZ4aeNAeFHA.2420@TK2MSFTNGP12.phx.gbl...
> Hello,
>
> I am trying to open with my Pocket PC (Windows Mobile 2003) a terminal
> services connexion to a Windows terminal server in our company using a VPN
> connexion.
>
> The VPN seems to work fine. On the VPN server (Microsoft ISA 2004) I see
> the VPN client connected. When I then open the Terminal client on the
> Pocket PC there is no way to connect to a terminal server: always "host
> not found" message. Same thing when I use an IP address instead of the
> server name.
>
> With a Windows terminal client (i.e. Remote Desktop from Windows XP),
> there is no problem.
>
> Any suggestions ?
>
> Ezéchiel Darvas
>
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.