Remote connection from WM5 PDA

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

Im trying to remotely connect to my home PC through my WM5 PDA's Terminal
Services App. The problem seems to be that My network has only got 1 ip
address. I have 2 pcs, 1 laptop, 1 PDA an xbox360 and PS3 on the network but
whichever i check out using whatismyip.com it gives me the same IP.

If I am on the network and connect using the local ip, eg 192.168.2.5 it
works but from outside it obviously doesn't. It gives me the error "The
client could not connect to the remote computer, the server might be busy"

This also happens when using another PC that is not on the network.

So my question is, how do I find out each computers specific public ip
address??

Hope you can help,
 
Ian said:
Hi,

Im trying to remotely connect to my home PC through my WM5 PDA's Terminal
Services App. The problem seems to be that My network has only got 1 ip
address. I have 2 pcs, 1 laptop, 1 PDA an xbox360 and PS3 on the network
but
whichever i check out using whatismyip.com it gives me the same IP.

If I am on the network and connect using the local ip, eg 192.168.2.5 it
works but from outside it obviously doesn't. It gives me the error "The
client could not connect to the remote computer, the server might be busy"

This also happens when using another PC that is not on the network.

So my question is, how do I find out each computers specific public ip
address??

Hope you can help,
Click to expand...

To access multiple PCs, that are behind a firewall/router, with Remote
Desktop or the TSC on your WM5 device see this page...

http://theillustratednetwork.mvps.org/RemoteDesktop/Multiple_PC_RD.html

If the target PCs are running Vista make sure the Vista host is configured
like this...

http://theillustratednetwork.mvps.org/ScreenShots/XP/RDP6-XPClienttoVistaServerConfig.jpg

Vista and XP clients should then be configured like this...

http://theillustratednetwork.mvps.org/ScreenShots/XP/RDP6-XPClientSettings.jpg

The problem with the WM5 device is if you need to change the calling port.
Normally you append the new port number to the address, ie.
12.34.56.78:NewPort. With WM5 devices that does not work, or at least it did
not when I last had a PocketPC. The solution is a registry hack. There is a
registry hack that you can try however...Open the registry and navigate
to...

HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default


Add a DWORD named Server Port and enter the decimal port number of the new
Remote Desktop Listening Port. Alternatively the Tweaks2K 2program automated
this a bit. See registry hack 81...

http://www.tweaks2k2.com/portal/staticpages/index.php?page=20050224182009983

Also note the WM5 device will only do 64-bit encryption so if the Remote
Desktop host PC is set to "High" encryption the WM5 device will never
connect. The host needs to be configured for the default "Not configured" or
a "Client compatible" mode.

--

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...
How to ask a question
http://support.microsoft.com/KB/555375
 
Sooner Al said:
To access multiple PCs, that are behind a firewall/router, with Remote
Desktop or the TSC on your WM5 device see this page...

http://theillustratednetwork.mvps.org/RemoteDesktop/Multiple_PC_RD.html

If the target PCs are running Vista make sure the Vista host is configured
like this...

http://theillustratednetwork.mvps.org/ScreenShots/XP/RDP6-XPClienttoVistaServerConfig.jpg

Vista and XP clients should then be configured like this...

http://theillustratednetwork.mvps.org/ScreenShots/XP/RDP6-XPClientSettings.jpg

The problem with the WM5 device is if you need to change the calling port.
Normally you append the new port number to the address, ie.
12.34.56.78:NewPort. With WM5 devices that does not work, or at least it
did not when I last had a PocketPC. The solution is a registry hack. There
is a registry hack that you can try however...Open the registry and
navigate to...

HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default


Add a DWORD named Server Port and enter the decimal port number of the new
Remote Desktop Listening Port. Alternatively the Tweaks2K 2program
automated
this a bit. See registry hack 81...

http://www.tweaks2k2.com/portal/staticpages/index.php?page=20050224182009983

Also note the WM5 device will only do 64-bit encryption so if the Remote
Desktop host PC is set to "High" encryption the WM5 device will never
connect. The host needs to be configured for the default "Not configured"
or a "Client compatible" mode.

--

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...
How to ask a question
http://support.microsoft.com/KB/555375
Click to expand...

I forgot to add this link to a registry editor you can use on the WM5
device...

http://www.phm.lu/products/PocketPC/RegEdit/

As always, when hacking the registry on either a PC or your WM5 device BE
CAREFUL...

--

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...
How to ask a question
http://support.microsoft.com/KB/555375
 
Sooner Al said:
I forgot to add this link to a registry editor you can use on the WM5
device...

http://www.phm.lu/products/PocketPC/RegEdit/

As always, when hacking the registry on either a PC or your WM5 device BE
CAREFUL...

--

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...
How to ask a question
http://support.microsoft.com/KB/555375
Click to expand...

You also might consider setting up a PPTP VPN into your home LAN. Both XP
and Vista can act as a PPTP VPN server.

Here is how to do that with a Vista box...

http://theillustratednetwork.mvps.org/Vista/PPTP/PPTPVPN.html

An old page for XP. Ignore the references to ActiveSync over a VPN to the
standalone PC. By design that no longer works in WM5 for security reasons...

http://theillustratednetwork.mvps.org/WM2003/WM2003PPTPVPN.html

WM5 VPN help...

http://www.microsoft.com/windowsmobile/help/pocketpc/connections.mspx#vpn

With a VPN you can access all PCs through one hole in your firewall/router
and do not need to change the listening ports on the PCs in order to use
Remote Desktop or TSC. Make sure you use a STRONG password...

http://www.microsoft.com/protect/yourself/password/checker.mspx

--

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...
How to ask a question
http://support.microsoft.com/KB/555375
 
Back
Top