It's like i thought I was gonna have to use a VCN or something, but no, it actually works!! So now I'm making this post remotely from my axim, but it's really my pc's browser!! To tell you the truth, I think browsing this way is actually FASTER than using PIE directly on my handheld. Now I just need to see if there are any ports I need to foward to do this from open WiFi access point and not my local network. Yippie!!
I'd just thought I'd share my little experience as it could not have been accomplished without all the info I've gained here at Aximsite!
I'm still trying to get my head wrapped around this concept.
So, if my kids are occupying my home comp and my laptop is dead or I don't want to lug it outside ... while i'm sitting on my lawn chair sipping a Mai Tai ...I could use PIE on my Ax but use Terminal Services to use the home comp's browser (so it's faster)?
It's definately better for some things... because big IE is more powerful that little IE.
The main drawback is you use heaps more bandwidth by using remote desktop rather than just surfing in Pocket IE, so it's going to be a lot slower if you're connected to the big PC via anything slower than broadband.
If you're connecting to your home/work via a wireless LAN link though it's tons better to just remote desktop into your computer.
__________________
:exc: Fatal Error: Please perform a hard reset
You can then use the terminal services client which should already be installed under your programs menu on your Axim to connect to your PC's IP address.
The exact steps will vary slightly depending on how your network is set up, whether you have a router/firewall, and what machine you're connecting to.
__________________
:exc: Fatal Error: Please perform a hard reset
The standard port for Remote Desktop is 3389. You should forward this port from you router to the server PC in order for you to access from the internet. If you want to set up more machines for Remote desktop, you can forward different public ports to the port 3389 in different machines. It is better to use static internal LAN IP for your server PCs, so that the port forward rule will be simpler.
Also, it seem that the standard Terminal client in the PPC (at least my x50v) can only use the standard 3389 port. If I type in xxx.xxx.xxx.xxx:yyyy (yyyy is the port number) in the terminal client in the PPC, it said it is not a valid IP.
Windows XP Professional, Server 2003, and Server 2K have build-in Terminal service.
Due to license issue, the XP Pro allow only one user actively using the machine in anytime. If there is a user physically using the XP Pro machine, Remote Desktop to that machine will kick out the current user like forcing to switch user. There is a hack to allow two concurrent users on the XP Pro but both the users should have the administrator right.
To allow XP Home or concurrent user on XP Pro, 3rd party software is required but they are pretty expensive.
One more note, if there is a lot of graphic on the screen, remote desktop will be very slow because the graphic compression ratio is much lower than the JPG and GIF compression.
Also, there is also a convoluted hack to enable TSC on XP HOME systems (Search google).
I use TSC daily to log into my office PC using PORT FORWARDING on our office router and the standard 3389 port. Works great. Much faster than VNC.
to l
Originally Posted by wstam
The standard port for Remote Desktop is 3389. You should forward this port from you router to the server PC in order for you to access from the internet. If you want to set up more machines for Remote desktop, you can forward different public ports to the port 3389 in different machines. It is better to use static internal LAN IP for your server PCs, so that the port forward rule will be simpler.
Also, it seem that the standard Terminal client in the PPC (at least my x50v) can only use the standard 3389 port. If I type in xxx.xxx.xxx.xxx:yyyy (yyyy is the port number) in the terminal client in the PPC, it said it is not a valid IP.
Windows XP Professional, Server 2003, and Server 2K have build-in Terminal service.
Due to license issue, the XP Pro allow only one user actively using the machine in anytime. If there is a user physically using the XP Pro machine, Remote Desktop to that machine will kick out the current user like forcing to switch user. There is a hack to allow two concurrent users on the XP Pro but both the users should have the administrator right.
To allow XP Home or concurrent user on XP Pro, 3rd party software is required but they are pretty expensive.
One more note, if there is a lot of graphic on the screen, remote desktop will be very slow because the graphic compression ratio is much lower than the JPG and GIF compression.
Also, there is also a convoluted hack to enable TSC on XP HOME systems (Search google).
KPDUTY, I do a quick search on Google and cannot find the convoluted hack to enable TSC on XP HOME.It will be very helpfull if you can help me to find this out.
KPDUTY, I do a quick search on Google and cannot find the convoluted hack to enable TSC on XP HOME.It will be very helpfull if you can help me to find this out.
Yeah, Terminal Service is great and reasonably fast, way faster than VNC. What I don't like about it is that it forces display resolution change to VGA on my desktop. I hope there's an option to keep the original resolution. I use VNC for this reason.
The link you suggested is for running IIS in XP Home. I believe IIS is WEB and FTP servers and Terminal Server is not part of IIS. In XP Pro, I can enable Remote Desktop (Terminal Server) without install IIS.
Using the same method, I found a line "TerminalServer=TsOc.dll, HydraOc, TsOc.inf,hide,2" in the SYSOC.INF in a XP Pro machine.
I will try this at home.
My Dell Dimension 2400 come with a legal XP Home. I don't want to change this to illegal XP Pro.
In my opinion, the real importance different between XP Home and XP Pro is:
1. Remote Desktop
2. File and Directory user privilege setting. XP Home only allow to set file and directory user privilege when boot in safe mode.
3. Login to a Domain network.
Otherwise, I don't see any importance difference between XP Home and XP Pro.
Originally Posted by KPDUTY
Like I said, it is possible. I wouldn't bother with all this . . . alot simpler just to upgrade to XP Professional:
I agree, this is not a recommended change. I only referenced it because you asked. I did not really look at its details.
(I found reference to this by searching Aximsite...here is the original thread): TSC HOME AXIMSITE THREAD
I personally use XP Professional everywhere for the reasons you noted.
Originally Posted by wstam
KPDUTY, sorry again.
The link you suggested is for running IIS in XP Home. I believe IIS is WEB and FTP servers and Terminal Server is not part of IIS. In XP Pro, I can enable Remote Desktop (Terminal Server) without install IIS.
Using the same method, I found a line "TerminalServer=TsOc.dll, HydraOc, TsOc.inf,hide,2" in the SYSOC.INF in a XP Pro machine.
I will try this at home.
My Dell Dimension 2400 come with a legal XP Home. I don't want to change this to illegal XP Pro.
In my opinion, the real importance different between XP Home and XP Pro is:
1. Remote Desktop
2. File and Directory user privilege setting. XP Home only allow to set file and directory user privilege when boot in safe mode.
3. Login to a Domain network.
Otherwise, I don't see any importance difference between XP Home and XP Pro.
Can someone help me connect to my PC from outside home network?
Ok, I got Terminal Services Client to work on my home network. But i was wondering if someone can provide me a step by step procedure on how to get it to work from outside my home network. Say at school and I want to access my home computer.
Any help will be appreciated. Please remember, I don't know too much about networking so please explain in laymen's terms. thanks.
Follow Us
RSS Feed
Follow on Twitter
Facebook
YouTube
Terminal Services.......WOW it works!!!
