|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
April 15th 04, 12:27 PM
|
|||
|
|||
Remote Desktop problems
I've never been able to get Remote Desktop to work. But I'm trying again.
I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either. -- Tom Richards 
|
| Ads |
|
#2
April 15th 04, 12:30 PM
|
|||
|
|||
|
Remote Desktop problems
I assume your connecting to the lan ip address of the other xp pro box(or
the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
|
#4
April 15th 04, 12:33 PM
|
|||
|
|||
|
Remote Desktop problems
Great. Now it gets a bit tricker, since you have a router involved. The
first thing you have to do is setup the router to port forward. In the routers config page (usually at 192.168.0.1) you should see settings to setup port forwarding. You will have to tell the router to open port 3389 and if anyone tries to connect to it to forward that connection to your computers lan ip address that has remote desktop listening. (note: 3389 is the default port and can be changed in the registry for added security). Once you have the port forwarding setup, from outside your network you would try to connect to your networks WAN ip address. You'll find this in the router info pages. When a connection to the wan is initiated it will forward that connection to the correct box, the logon will popup, and you can log in. Note: the computer listening with RD must be online Note: if you change the default port then when you try to connect you have to specify the port as well, like this: 66.66.66.68:7777 Tom Richards wrote: Wow Phil...that worked! I assigned myself a psswd and voila....Now, once I make sure the appropriate files are installed on my remote (girlfriend's - xp home) machine, what address would she use to access my desktop? "Phil (a.k.a. purplehaz)" wrote in message ... I assume your connecting to the lan ip address of the other xp pro box(or the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
|
#5
April 15th 04, 01:22 PM
|
|||
|
|||
|
Remote Desktop problems
What is the service that should be listening? RDsessmgr (sessmgr.exe)?? Is
the procedure the same for a software firewall (Sygate PF)? -- Tumppi Reply to group ================================================= Most learned here on nntp://news.mircosoft.com Helsinki, Finland (remove NO _SPAM) (translations from FI/SE not always accurate) ================================================= "Phil (a.k.a. purplehaz)" kirjoitti viestissä ... Great. Now it gets a bit tricker, since you have a router involved. The first thing you have to do is setup the router to port forward. In the routers config page (usually at 192.168.0.1) you should see settings to setup port forwarding. You will have to tell the router to open port 3389 and if anyone tries to connect to it to forward that connection to your computers lan ip address that has remote desktop listening. (note: 3389 is the default port and can be changed in the registry for added security). Once you have the port forwarding setup, from outside your network you would try to connect to your networks WAN ip address. You'll find this in the router info pages. When a connection to the wan is initiated it will forward that connection to the correct box, the logon will popup, and you can log in. Note: the computer listening with RD must be online Note: if you change the default port then when you try to connect you have to specify the port as well, like this: 66.66.66.68:7777 Tom Richards wrote: Wow Phil...that worked! I assigned myself a psswd and voila....Now, once I make sure the appropriate files are installed on my remote (girlfriend's - xp home) machine, what address would she use to access my desktop? "Phil (a.k.a. purplehaz)" wrote in message ... I assume your connecting to the lan ip address of the other xp pro box(or the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
|
#6
April 15th 04, 02:14 PM
|
|||
|
|||
|
Remote Desktop problems
Thanks, Phil. I set my forwarding and then went to test a remote hookup
(from my laptop....still on my home network) by inputting http://141.151.xx.xxx which is my wan ip address. The logon screen for the router admin came up, not rd. Here's my ip info from the router admin: LAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 192.xxx.x.x Subnet Mask: 255.255.255.0 DHCP server: Enabled WAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 141.151.xxx.xxx DNS: 151.197.xxx.xxx 151.197.xxx.xxx 0.0.0.0 -- Tom Richards "Phil (a.k.a. purplehaz)" wrote in message ... Great. Now it gets a bit tricker, since you have a router involved. The first thing you have to do is setup the router to port forward. In the routers config page (usually at 192.168.0.1) you should see settings to setup port forwarding. You will have to tell the router to open port 3389 and if anyone tries to connect to it to forward that connection to your computers lan ip address that has remote desktop listening. (note: 3389 is the default port and can be changed in the registry for added security). Once you have the port forwarding setup, from outside your network you would try to connect to your networks WAN ip address. You'll find this in the router info pages. When a connection to the wan is initiated it will forward that connection to the correct box, the logon will popup, and you can log in. Note: the computer listening with RD must be online Note: if you change the default port then when you try to connect you have to specify the port as well, like this: 66.66.66.68:7777 Tom Richards wrote: Wow Phil...that worked! I assigned myself a psswd and voila....Now, once I make sure the appropriate files are installed on my remote (girlfriend's - xp home) machine, what address would she use to access my desktop? "Phil (a.k.a. purplehaz)" wrote in message ... I assume your connecting to the lan ip address of the other xp pro box(or the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
|
#7
April 15th 04, 03:27 PM
|
|||
|
|||
|
Remote Desktop problems
Thanks, Phil. I set my forwarding and then went to test a remote hookup
(from my laptop....still on my home network) by inputting http://141.151.xx.xxx which is my wan ip address. The logon screen for the router admin came up, not rd. Here's my ip info from the router admin: LAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 192.xxx.x.x Subnet Mask: 255.255.255.0 DHCP server: Enabled WAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 141.151.xxx.xxx DNS: 151.197.xxx.xxx 151.197.xxx.xxx 0.0.0.0 -- Tom Richards "Phil (a.k.a. purplehaz)" wrote in message ... Great. Now it gets a bit tricker, since you have a router involved. The first thing you have to do is setup the router to port forward. In the routers config page (usually at 192.168.0.1) you should see settings to setup port forwarding. You will have to tell the router to open port 3389 and if anyone tries to connect to it to forward that connection to your computers lan ip address that has remote desktop listening. (note: 3389 is the default port and can be changed in the registry for added security). Once you have the port forwarding setup, from outside your network you would try to connect to your networks WAN ip address. You'll find this in the router info pages. When a connection to the wan is initiated it will forward that connection to the correct box, the logon will popup, and you can log in. Note: the computer listening with RD must be online Note: if you change the default port then when you try to connect you have to specify the port as well, like this: 66.66.66.68:7777 Tom Richards wrote: Wow Phil...that worked! I assigned myself a psswd and voila....Now, once I make sure the appropriate files are installed on my remote (girlfriend's - xp home) machine, what address would she use to access my desktop? "Phil (a.k.a. purplehaz)" wrote in message ... I assume your connecting to the lan ip address of the other xp pro box(or the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
|
#8
April 15th 04, 07:01 PM
|
|||
|
|||
|
Remote Desktop problems
Same idea for a software firewall, but you don't really port forward, you
just have to allow the connection in, usually by ip address. Zone alarm pro, for example, will allow you to put in trusted ip addresses. Then when this and only this ip address tries to connect to lets it thru and connects to remote desktop. The service actually gets listed as one of the svchost.exe's, I don't know the exact .exe that turn rd on or off. Thomas Wendell wrote: What is the service that should be listening? RDsessmgr (sessmgr.exe)?? Is the procedure the same for a software firewall (Sygate PF)? "Phil (a.k.a. purplehaz)" kirjoitti viestissä ... Great. Now it gets a bit tricker, since you have a router involved. The first thing you have to do is setup the router to port forward. In the routers config page (usually at 192.168.0.1) you should see settings to setup port forwarding. You will have to tell the router to open port 3389 and if anyone tries to connect to it to forward that connection to your computers lan ip address that has remote desktop listening. (note: 3389 is the default port and can be changed in the registry for added security). Once you have the port forwarding setup, from outside your network you would try to connect to your networks WAN ip address. You'll find this in the router info pages. When a connection to the wan is initiated it will forward that connection to the correct box, the logon will popup, and you can log in. Note: the computer listening with RD must be online Note: if you change the default port then when you try to connect you have to specify the port as well, like this: 66.66.66.68:7777 Tom Richards wrote: Wow Phil...that worked! I assigned myself a psswd and voila....Now, once I make sure the appropriate files are installed on my remote (girlfriend's - xp home) machine, what address would she use to access my desktop? "Phil (a.k.a. purplehaz)" wrote in message ... I assume your connecting to the lan ip address of the other xp pro box(or the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
|
#9
April 15th 04, 07:05 PM
|
|||
|
|||
|
Remote Desktop problems
You can't test it that way. If your "inside" the network you can't connect
to the wan(outside) ip address to get in again, your already in the network. Test it from outside the network. Connect to the wan ip and it should forward you to the computer running rd. I have a setup just like this and also a setup with a software firewall that I use every single day, works great. Tom Richards wrote: Thanks, Phil. I set my forwarding and then went to test a remote hookup (from my laptop....still on my home network) by inputting http://141.151.xx.xxx which is my wan ip address. The logon screen for the router admin came up, not rd. Here's my ip info from the router admin: LAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 192.xxx.x.x Subnet Mask: 255.255.255.0 DHCP server: Enabled WAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 141.151.xxx.xxx DNS: 151.197.xxx.xxx 151.197.xxx.xxx 0.0.0.0 "Phil (a.k.a. purplehaz)" wrote in message ... Great. Now it gets a bit tricker, since you have a router involved. The first thing you have to do is setup the router to port forward. In the routers config page (usually at 192.168.0.1) you should see settings to setup port forwarding. You will have to tell the router to open port 3389 and if anyone tries to connect to it to forward that connection to your computers lan ip address that has remote desktop listening. (note: 3389 is the default port and can be changed in the registry for added security). Once you have the port forwarding setup, from outside your network you would try to connect to your networks WAN ip address. You'll find this in the router info pages. When a connection to the wan is initiated it will forward that connection to the correct box, the logon will popup, and you can log in. Note: the computer listening with RD must be online Note: if you change the default port then when you try to connect you have to specify the port as well, like this: 66.66.66.68:7777 Tom Richards wrote: Wow Phil...that worked! I assigned myself a psswd and voila....Now, once I make sure the appropriate files are installed on my remote (girlfriend's - xp home) machine, what address would she use to access my desktop? "Phil (a.k.a. purplehaz)" wrote in message ... I assume your connecting to the lan ip address of the other xp pro box(or the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
|
#10
April 15th 04, 07:52 PM
|
|||
|
|||
|
Remote Desktop problems
Same idea for a software firewall, but you don't really port forward, you
just have to allow the connection in, usually by ip address. Zone alarm pro, for example, will allow you to put in trusted ip addresses. Then when this and only this ip address tries to connect to lets it thru and connects to remote desktop. The service actually gets listed as one of the svchost.exe's, I don't know the exact .exe that turn rd on or off. Thomas Wendell wrote: What is the service that should be listening? RDsessmgr (sessmgr.exe)?? Is the procedure the same for a software firewall (Sygate PF)? "Phil (a.k.a. purplehaz)" kirjoitti viestissä ... Great. Now it gets a bit tricker, since you have a router involved. The first thing you have to do is setup the router to port forward. In the routers config page (usually at 192.168.0.1) you should see settings to setup port forwarding. You will have to tell the router to open port 3389 and if anyone tries to connect to it to forward that connection to your computers lan ip address that has remote desktop listening. (note: 3389 is the default port and can be changed in the registry for added security). Once you have the port forwarding setup, from outside your network you would try to connect to your networks WAN ip address. You'll find this in the router info pages. When a connection to the wan is initiated it will forward that connection to the correct box, the logon will popup, and you can log in. Note: the computer listening with RD must be online Note: if you change the default port then when you try to connect you have to specify the port as well, like this: 66.66.66.68:7777 Tom Richards wrote: Wow Phil...that worked! I assigned myself a psswd and voila....Now, once I make sure the appropriate files are installed on my remote (girlfriend's - xp home) machine, what address would she use to access my desktop? "Phil (a.k.a. purplehaz)" wrote in message ... I assume your connecting to the lan ip address of the other xp pro box(or the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
|
#11
April 15th 04, 07:59 PM
|
|||
|
|||
|
Remote Desktop problems
You can't test it that way. If your "inside" the network you can't connect
to the wan(outside) ip address to get in again, your already in the network. Test it from outside the network. Connect to the wan ip and it should forward you to the computer running rd. I have a setup just like this and also a setup with a software firewall that I use every single day, works great. Tom Richards wrote: Thanks, Phil. I set my forwarding and then went to test a remote hookup (from my laptop....still on my home network) by inputting http://141.151.xx.xxx which is my wan ip address. The logon screen for the router admin came up, not rd. Here's my ip info from the router admin: LAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 192.xxx.x.x Subnet Mask: 255.255.255.0 DHCP server: Enabled WAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 141.151.xxx.xxx DNS: 151.197.xxx.xxx 151.197.xxx.xxx 0.0.0.0 "Phil (a.k.a. purplehaz)" wrote in message ... Great. Now it gets a bit tricker, since you have a router involved. The first thing you have to do is setup the router to port forward. In the routers config page (usually at 192.168.0.1) you should see settings to setup port forwarding. You will have to tell the router to open port 3389 and if anyone tries to connect to it to forward that connection to your computers lan ip address that has remote desktop listening. (note: 3389 is the default port and can be changed in the registry for added security). Once you have the port forwarding setup, from outside your network you would try to connect to your networks WAN ip address. You'll find this in the router info pages. When a connection to the wan is initiated it will forward that connection to the correct box, the logon will popup, and you can log in. Note: the computer listening with RD must be online Note: if you change the default port then when you try to connect you have to specify the port as well, like this: 66.66.66.68:7777 Tom Richards wrote: Wow Phil...that worked! I assigned myself a psswd and voila....Now, once I make sure the appropriate files are installed on my remote (girlfriend's - xp home) machine, what address would she use to access my desktop? "Phil (a.k.a. purplehaz)" wrote in message ... I assume your connecting to the lan ip address of the other xp pro box(or the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
|
#12
April 15th 04, 09:04 PM
|
|||
|
|||
|
Remote Desktop problems
Same idea for a software firewall, but you don't really port forward, you
just have to allow the connection in, usually by ip address. Zone alarm pro, for example, will allow you to put in trusted ip addresses. Then when this and only this ip address tries to connect to lets it thru and connects to remote desktop. The service actually gets listed as one of the svchost.exe's, I don't know the exact .exe that turn rd on or off. Thomas Wendell wrote: What is the service that should be listening? RDsessmgr (sessmgr.exe)?? Is the procedure the same for a software firewall (Sygate PF)? "Phil (a.k.a. purplehaz)" kirjoitti viestissä ... Great. Now it gets a bit tricker, since you have a router involved. The first thing you have to do is setup the router to port forward. In the routers config page (usually at 192.168.0.1) you should see settings to setup port forwarding. You will have to tell the router to open port 3389 and if anyone tries to connect to it to forward that connection to your computers lan ip address that has remote desktop listening. (note: 3389 is the default port and can be changed in the registry for added security). Once you have the port forwarding setup, from outside your network you would try to connect to your networks WAN ip address. You'll find this in the router info pages. When a connection to the wan is initiated it will forward that connection to the correct box, the logon will popup, and you can log in. Note: the computer listening with RD must be online Note: if you change the default port then when you try to connect you have to specify the port as well, like this: 66.66.66.68:7777 Tom Richards wrote: Wow Phil...that worked! I assigned myself a psswd and voila....Now, once I make sure the appropriate files are installed on my remote (girlfriend's - xp home) machine, what address would she use to access my desktop? "Phil (a.k.a. purplehaz)" wrote in message ... I assume your connecting to the lan ip address of the other xp pro box(or the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
|
#13
April 15th 04, 09:08 PM
|
|||
|
|||
|
Remote Desktop problems
You can't test it that way. If your "inside" the network you can't connect
to the wan(outside) ip address to get in again, your already in the network. Test it from outside the network. Connect to the wan ip and it should forward you to the computer running rd. I have a setup just like this and also a setup with a software firewall that I use every single day, works great. Tom Richards wrote: Thanks, Phil. I set my forwarding and then went to test a remote hookup (from my laptop....still on my home network) by inputting http://141.151.xx.xxx which is my wan ip address. The logon screen for the router admin came up, not rd. Here's my ip info from the router admin: LAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 192.xxx.x.x Subnet Mask: 255.255.255.0 DHCP server: Enabled WAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 141.151.xxx.xxx DNS: 151.197.xxx.xxx 151.197.xxx.xxx 0.0.0.0 "Phil (a.k.a. purplehaz)" wrote in message ... Great. Now it gets a bit tricker, since you have a router involved. The first thing you have to do is setup the router to port forward. In the routers config page (usually at 192.168.0.1) you should see settings to setup port forwarding. You will have to tell the router to open port 3389 and if anyone tries to connect to it to forward that connection to your computers lan ip address that has remote desktop listening. (note: 3389 is the default port and can be changed in the registry for added security). Once you have the port forwarding setup, from outside your network you would try to connect to your networks WAN ip address. You'll find this in the router info pages. When a connection to the wan is initiated it will forward that connection to the correct box, the logon will popup, and you can log in. Note: the computer listening with RD must be online Note: if you change the default port then when you try to connect you have to specify the port as well, like this: 66.66.66.68:7777 Tom Richards wrote: Wow Phil...that worked! I assigned myself a psswd and voila....Now, once I make sure the appropriate files are installed on my remote (girlfriend's - xp home) machine, what address would she use to access my desktop? "Phil (a.k.a. purplehaz)" wrote in message ... I assume your connecting to the lan ip address of the other xp pro box(or the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
|
#14
April 16th 04, 04:09 AM
|
|||
|
|||
|
Remote Desktop problems
I set everything up and tried to connect to my pc running xp pro from
outside of the network and it throws an error message "the client could not connect to the reomote computer. Remote connections might not be enabled,,,," I tried putting my wan address in the http://wan address here form and also in the remote desktop logon window on the client pc. "Phil (a.k.a. purplehaz)" wrote in message ... You can't test it that way. If your "inside" the network you can't connect to the wan(outside) ip address to get in again, your already in the network. Test it from outside the network. Connect to the wan ip and it should forward you to the computer running rd. I have a setup just like this and also a setup with a software firewall that I use every single day, works great. Tom Richards wrote: Thanks, Phil. I set my forwarding and then went to test a remote hookup (from my laptop....still on my home network) by inputting http://141.151.xx.xxx which is my wan ip address. The logon screen for the router admin came up, not rd. Here's my ip info from the router admin: LAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 192.xxx.x.x Subnet Mask: 255.255.255.0 DHCP server: Enabled WAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 141.151.xxx.xxx DNS: 151.197.xxx.xxx 151.197.xxx.xxx 0.0.0.0 "Phil (a.k.a. purplehaz)" wrote in message ... Great. Now it gets a bit tricker, since you have a router involved. The first thing you have to do is setup the router to port forward. In the routers config page (usually at 192.168.0.1) you should see settings to setup port forwarding. You will have to tell the router to open port 3389 and if anyone tries to connect to it to forward that connection to your computers lan ip address that has remote desktop listening. (note: 3389 is the default port and can be changed in the registry for added security). Once you have the port forwarding setup, from outside your network you would try to connect to your networks WAN ip address. You'll find this in the router info pages. When a connection to the wan is initiated it will forward that connection to the correct box, the logon will popup, and you can log in. Note: the computer listening with RD must be online Note: if you change the default port then when you try to connect you have to specify the port as well, like this: 66.66.66.68:7777 Tom Richards wrote: Wow Phil...that worked! I assigned myself a psswd and voila....Now, once I make sure the appropriate files are installed on my remote (girlfriend's - xp home) machine, what address would she use to access my desktop? "Phil (a.k.a. purplehaz)" wrote in message ... I assume your connecting to the lan ip address of the other xp pro box(or the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
|
#15
April 16th 04, 05:00 AM
|
|||
|
|||
|
Remote Desktop problems
I set everything up and tried to connect to my pc running xp pro from
outside of the network and it throws an error message "the client could not connect to the reomote computer. Remote connections might not be enabled,,,," I tried putting my wan address in the http://wan address here form and also in the remote desktop logon window on the client pc. "Phil (a.k.a. purplehaz)" wrote in message ... You can't test it that way. If your "inside" the network you can't connect to the wan(outside) ip address to get in again, your already in the network. Test it from outside the network. Connect to the wan ip and it should forward you to the computer running rd. I have a setup just like this and also a setup with a software firewall that I use every single day, works great. Tom Richards wrote: Thanks, Phil. I set my forwarding and then went to test a remote hookup (from my laptop....still on my home network) by inputting http://141.151.xx.xxx which is my wan ip address. The logon screen for the router admin came up, not rd. Here's my ip info from the router admin: LAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 192.xxx.x.x Subnet Mask: 255.255.255.0 DHCP server: Enabled WAN: (MAC Address: 00-04-5A-E5-xxxx) IP Address: 141.151.xxx.xxx DNS: 151.197.xxx.xxx 151.197.xxx.xxx 0.0.0.0 "Phil (a.k.a. purplehaz)" wrote in message ... Great. Now it gets a bit tricker, since you have a router involved. The first thing you have to do is setup the router to port forward. In the routers config page (usually at 192.168.0.1) you should see settings to setup port forwarding. You will have to tell the router to open port 3389 and if anyone tries to connect to it to forward that connection to your computers lan ip address that has remote desktop listening. (note: 3389 is the default port and can be changed in the registry for added security). Once you have the port forwarding setup, from outside your network you would try to connect to your networks WAN ip address. You'll find this in the router info pages. When a connection to the wan is initiated it will forward that connection to the correct box, the logon will popup, and you can log in. Note: the computer listening with RD must be online Note: if you change the default port then when you try to connect you have to specify the port as well, like this: 66.66.66.68:7777 Tom Richards wrote: Wow Phil...that worked! I assigned myself a psswd and voila....Now, once I make sure the appropriate files are installed on my remote (girlfriend's - xp home) machine, what address would she use to access my desktop? "Phil (a.k.a. purplehaz)" wrote in message ... I assume your connecting to the lan ip address of the other xp pro box(or the laptops full computer name) and all software firewalls are turned off. Once the logon box comes up, you put in a user name that's on the computer your connecting to and its password. If the user account does not exist and /or does not have a password on the box your connecting to you'll get an error message. Does user sal exist on the box your connecting to? Does the user sal have a password? Tom Richards wrote: I've never been able to get Remote Desktop to work. But I'm trying again. I've searched the newsgroups and terminal services is started, there's nothing in event viewer and rd is installed on both pcs - I'm trying to connect my server pc (desktop) to my laptop on my home network. Both run xp pro. I get to the rd logon screen on my laptop, type in my desktop name (sal) and get the "the client could not connect to the remote computer" error message. I'm using a lynksyss router and tried entering the wan and lan ip address instead of sal - no good. The router is set to assign a wan address automatically. I also ran a run command to determine if the ports were "listening" and they all were. My home network works fine - shared printer, files, etc. I'd like to eventually work remotely from a machine running xp home but if I can't get my home network up and running, I guess that won't work either.
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
