This seemed to work at first but got a timed out error. Just asks to try
later.
Will keep trying.
Do I have to check my IP address each time and enter this new #?
Did you give any permission to let other devices connect to your PC
remotely?

Signature
Carlo Ma. Guerrero
Microsoft MVP, Mobile Devices
This seemed to work at first but got a timed out error. Just asks to try
later.
Will keep trying.
Do I have to check my IP address each time and enter this new #?
"Clinton Fitch III" <newsgroups@NOSPAMMYTHANKIE.c3-technology.com> wrote in
message news:eeKfHQLiEHA.2848@TK2MSFTNGP10.phx.gbl...
> Monty,
>
[quoted text clipped - 7 lines]
> your network.
> 3. Using Terminal Services Client, put in the IP address of your PC in
the
> server box and tap connect.
> 4. Assuming you have allowed for remote access of your PC (you will need
to
> allow this) you should see the login screen for your PC.
>
[quoted text clipped - 4 lines]
>
> > Hi, I have a Dell X30 with built in Bluetooth/WiFi and have heard that
you
> > can login remotely and manipulate the PC as if right in front of it.
Any
> > clues on this?
> > I can sync remotely via bluetooth, and send files, but that is it.
> > Any help?
> > Thanks, Monty
Monty - 23 Aug 2004 04:51 GMT
Please tell me how to give permissions on my PC.
> Did you give any permission to let other devices connect to your PC
> remotely?
[quoted text clipped - 36 lines]
> > > Any help?
> > > Thanks, Monty
You should be able to enter the PCs name as well (if you are in a domain,
enter the FQDN).
Verify that you have given the permission for devices to connect to your PC.
This could be the cause of your timeout issue.
Regards,

Signature
Clinton Fitch
Editor
Clinton Fitch (Dot) Com!
HPC:Factor
http://www.clintonfitch.com
http://www.hpcfactor.com
> This seemed to work at first but got a timed out error. Just asks to try
> later.
[quoted text clipped - 31 lines]
>> > Any help?
>> > Thanks, Monty
Monty - 23 Aug 2004 04:35 GMT
On my PC, how do I allow permissions?
> You should be able to enter the PCs name as well (if you are in a domain,
> enter the FQDN).
[quoted text clipped - 39 lines]
> >> > Any help?
> >> > Thanks, Monty
Sooner Al - 23 Aug 2004 12:42 GMT
In order to use TSC to control a desktop the desktop must be running XP Pro Remote Desktop or be a
Windows 2003/2000 Server running Terminal Services. Is that the case in your situation? Also, if the
desktop is running any type of personal firewall software then you need to open TCP Port 3389.
An alternative, if your desktop is running some other flavor of Windows, is VNC. Get the server
software from...
http://ultravnc.sourceforge.net/
..and the PocketPC client from either...
http://www.cs.utah.edu/%7Emidgley/wince/vnc.html
http://www.allware.com.mx/Windowsce/
For VNC you need to open TCP Port 5900 through any firewall your using...
Otherwise, can you ping the PC your trying to connect to?
http://www.cam.com/vxutil.html

Signature
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...
> On my PC, how do I allow permissions?
>
[quoted text clipped - 48 lines]
>> >> > Any help?
>> >> > Thanks, Monty
Monty - 24 Aug 2004 04:32 GMT
Yes it is on WXP Pro, I do have a McAfee firewall as well.
aside from the firewall, how do I "allow" these permissions?
Thank you, Monty
> In order to use TSC to control a desktop the desktop must be running XP Pro Remote Desktop or be a
> Windows 2003/2000 Server running Terminal Services. Is that the case in your situation? Also, if the
[quoted text clipped - 68 lines]
> >> >> > Any help?
> >> >> > Thanks, Monty
Sooner Al - 24 Aug 2004 10:21 GMT
http://www.microsoft.com/windowsxp/using/mobility/getstarted/enableremote.mspx
The account you use to access the desktop must be an Administrator or a member of the Remote Desktop
Users Group *AND* have a password.
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/pre
e_rem_hzcq.asp
Also make sure the XP Pro desktop is configured for either "Client compatible" or "Not configured"
in the RDP encryption settings. The default setting should be "Not configured". TSC is *NOT*
encrypted at 128-bits.
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/pre
e_rem_quaq.asp
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/pre
e_rem_uvnl.asp

Signature
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...
> Yes it is on WXP Pro, I do have a McAfee firewall as well.
> aside from the firewall, how do I "allow" these permissions?
[quoted text clipped - 97 lines]
>> >> >> > Any help?
>> >> >> > Thanks, Monty
Eric Hicks [MVP, Windows Mobile devices] - 24 Aug 2004 18:05 GMT
Open control panel and click the system icon. Once that opens click
"Remote" tab and make sure "Allow users to connect remotely to this
computer" is checked under Remote Desktop. From there you can goto "Select
Remote Users" button and choose the users you want to be able to connect.

Signature
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...
> Yes it is on WXP Pro, I do have a McAfee firewall as well.
> aside from the firewall, how do I "allow" these permissions?
[quoted text clipped - 104 lines]
>> >> >> > Any help?
>> >> >> > Thanks, Monty