Good News............ at least for me! I now have RD working both internally (LAN) and externally (Internet Web Connection)! After several hours of scratching my head, I decided to check the firewall. Remote Desktop was listed in the programs "allowed" to access the system, I had to also allow it to act as a server (which the auto configuration never asked me to address)..... and voila! everything works great!
Now, I have another question..........
Suppose I want to have access to all of the computers in my house at the same time.............. (after installing IIS on the other computers) should I go in to each machine's registry and change the port to which IIS listens, and then forward those ports on the router to the machines I want to access? I guess what I am asking is, can the same port be forwarded to more than one machine at the same time? My guess is the answer is No, but I just wanted to ask to make sure.......
Thanks again for everyone's help!! I truly can't thank you all enough!!
I think I could do this all over again, alone, if needed someday......... hopefully not too soon though!
--
Eric Thompson
(e-mail address removed)
(e-mail address removed)
to lock your machine, press ctrl-alt-del. One of the tabbed menu items is lock computer. This means, when attempting to connect to your winxp box from "somewheres else" you...or whomever is attempting to log in, will have to supply the user name and password to acutally log in. If you are the administrator of your own machine, you're set. If someone else is to have this priviledge, you'll have to add that permission.
You can verify that you're using the correct IP address by going to
www.whatismyipaddress.com and making sure that the ip address it reports is what you're using.
best wishes...
Mike,
Thanks so much for the info!!!!
First of all, I am not familiar with the process by which you "lock" the machine. I left my account logged in when I left home.... but didn't do anything to "lock" it.
I suspected the 192 address was a mistake specifically for the reason you stated. However, the 12.xxx.xx.x (IP address of the router which is registered with my ISP) didn't work either.
I followed all of the instructions to get tsweb set up correctly, rechecked the settings per the instructions, and everything checks out fine.
In my router setup for port forwarding, I left the application name blank, start port 3389/end port 3389, chose TCP as the type of traffic, listed my XP machine's IP address as the "forward to" machine, and clicked the "enable" box shown. (I did the exact same thing for port 80) I have the Linksys WRT54G v.1.1, which is a popular model.
I have not found a place to change the port Remote Desktop listens, and have no idea how to do that. Basically, I followed the Help files to setup Remote Desktop Web Connection and re-checked the settings for accuracy to the help files. I re-checked the settings because I couldn't connect using Remote Desktop via the internal network (choosing Start/All Programs/Accessories/Communications/Remote Desktop) either!
You (and others in this newsgroup) have helped me tremendously to understand the things I shouldn't be doing. However, there are some things I am learning that I should be doing that I am just not sure how to accomplish. Setting IIS to listen to a particular port is one, and locking the machine is another, just to name a couple. Unless it is absolutely mandatory to list an application in the router port forwarding setup screen, I believe I have my router set correctly. (looking for positives here
I also tend to believe that I have setup tsweb correctly, assuming the Help files are accurate and complete.
Again, I am sure these questions are elementary to most of you, but I appreciate yours and others help here. If you could tell me how to lock the machine to which I am trying to connect, and tell me how to change the port on which Remote Desktop listens (just in case I need to do that later), I might get "over the hump"..........
In case I have setup tsweb incorrectly, would it hurt anything to go through the process again? I think I tried that, but all components were already installed and no further action was indicated during the process............. just trying to cover all angles...........
One last question........... I have been assuming that the 12.xxx.xx.x IP address shown in my router as the WAN IP address' Default Gateway to be the IP that I need to be using here. I base this assumption on the fact that the 12.xxx.xx.xx IP address shown as the registered IP address of the router and using that IP address in my browser brings up the setup configuration screen of my router (after I type in my password, of course).
Thanks Again!!
--
Eric Thompson
(e-mail address removed)
(e-mail address removed)
The address you will use from IE will not begin with 192. anything. Any
address starting with 192 is a local address...that is...an address your
personal LAN uses behind your router (which might possibly explain why you
had some success in experimenting at home behind your router, but no success
when outside your router). The address you must use is the IP address of
your cable modem (or whatever you are using). For instance, if you are
using RoadRunner, your ip address might start with 24.xxx.xxx.xxx. You will
not be typing the :3389 nor the :80. You will only need to append a :nnnn
if you have changed the port which Remote Desktop uses to listen on.
Perhaps, until you get this working, you should not worry about changing
this port.
You must configure your router to pass port 80 and port 3389 to your winXP
machine. Once accomplished, remember that you must have logged in to your
winXP machine, and then locked it....repeat...you must have locked
it...before you leave for the airport (or wherever).
Then you will type
http://xxx.xxx.xxx.xxx/tsweb into IE. When the server
logon screen comes up, simply press enter.
Here's an additional thought....before attempting to connect via the Remote
Desktop Web Connection (using IE) why don't you attempt to connect using
Remote Desktop? That would eliminate the chance that you do not have tsweb
set up correctly. Once you get connected, your motivation will be renewed
(sounds like you're growing weary)..as this is an extremely useful tool.
Hope this gets you going....
Thanks Mike!!
I did all of my experimentation from home, using the Internet instead of the
Intranet connection method. However, today when I was in the airport, I
tried to get to the sign-on screen just as before (in my house) but couldn't
get connected this time. Here's what I typed into the browser URL address
field in IE:
(I tried each one separately of course)
192.168.1.xxx/tsweb
192.168.1.xxx/web/tsweb
192.168.1.xxx :3389/tsweb
192.168.1.xxx :80/tsweb
12.xxx.xx.x/tsweb (this is the IP given by the ISP for the router)
12.xxx.xx.x :3389/tsweb
12.xxx.xx.x/192.168.1.xxx/tsweb
None of them worked, even to get me to the sign-on screen this
time...........
It seems I should need to connect to the <ISP>/<Home PC>/tsweb, but that
doesn't work either............. very frustrating!
I even setup the home PC with a static IP address due to some information I
found in the Help Files.
Can you give me an example of how I should get to the sign-on screen from
outside my house? I am not running a domain, and there is no registration in
the WINS servers............. just a normal, mundane home PC network!
Thanks again for your time!!
--
Eric Thompson
(e-mail address removed)
(e-mail address removed)
the browser address field? The IP of the router >>such as xx.xxx.xx.x/tsweb,
or should I type in the IP of my machine such as xxx.xxx.x.xxx/tsweb. When I
use the <IP of >>the machine/tsweb> I can get to the connect screen. When I
use the <IP of the router/name of the machine/tsweb> I don't >>get to the
connect screen.
Use the method which gets you to the connect screen.
field? Should it be <IP of the router/IP of the >>machine/tsweb> or <IP of
the machine>, or <IP of the router>, or <name of the machine>?
Don't enter any info in the server field. Just press enter (on your
keyboard).
And if so, what should I type in the "User Name" >>field? I have typed my
name, which is by default an authorized user of the machine to which I am
trying to connect......... but >>nothing works!!
As I stated above...don't enter any info. Just press enter (on your
keyboard).
Hope this gets you going!
--
Eric Thompson
(e-mail address removed)
(e-mail address removed)
Hi everyone,
Trying to remote desktop from my office pc to home. (using web component and
mstsc)
- both PCs are running XP
- remote desktop is enabled on home PC
- remote desktop works on home PC if I connect using a PC on the same LAN
- have router in front of PC at home. Have setup port forward rule to
forward TCP port 3389 to home pc
- have installed remote desktop web component on IIS server on home pc. IIS
listening on a custom port number.
- I can connect to http://<homepc>:<port-x>/tsweb. I get the Remote desktop
web connection default page
- When I press connect I get a -pause- then, "The client could not connect
to the remote computer. Remote connections might not be enabled . .. ."
- the same error occurs when I use the XP remote desktop client
I can ping/tracert my router at home from work, connect to the router's web
management console and the /tsweb hosted by IIS on my home pc.
any ideas?
