remote desktop

Hi,
I'm tring to remotely control a Vista machine from a Windows XP machine, but it never connects.
The firewall log on the Vista machine shows it's dropping the packets coming in on port 3389.
I've changed the settings on the firewall (both using the control panel and the advanced console) to allow incoming connections and created an inbound rule as well to allow connections from anything on the subnet on port 3389.
The Remote Desktop service is running on the Vista machine.
It still doesn't work.
What am I overlooking?
Ben.

Have you tried using the ip address of the Vista machine instead of the machine name to connect? -- -- Andre Windows Connect | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm "Ben Kooijman" wrote in message

Hi,
I'm tring to remotely control a Vista machine from a Windows XP machine, but it never connects.
The firewall log on the Vista machine shows it's dropping the packets coming in on port 3389.
I've changed the settings on the firewall (both using the control panel and the advanced console) to allow incoming connections and created an inbound rule as well to allow connections from anything on the subnet on port 3389.
The Remote Desktop service is running on the Vista machine.
It still doesn't work.
What am I overlooking?
Ben.

Yes I have, doesn't work either.
I can ping the machine from a DOS prompt by name or IP address, that works fine.
Also, I can use Remote Deskop ion the Vista machine to control the Windows XP machine just not the other way around.
Ben.
"Andre Da Costa [Extended64]" wrote in message

Have you tried using the ip address of the Vista machine instead of the machine name to connect? -- -- Andre Windows Connect | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm "Ben Kooijman" wrote in message Hi,
I'm tring to remotely control a Vista machine from a Windows XP machine, but it never connects.
The firewall log on the Vista machine shows it's dropping the packets coming in on port 3389.
I've changed the settings on the firewall (both using the control panel and the advanced console) to allow incoming connections and created an inbound rule as well to allow connections from anything on the subnet on port 3389.
The Remote Desktop service is running on the Vista machine.
It still doesn't work.
What am I overlooking?
Ben.

You might have on the Vista machine configured to allow allow RDP 6.0 versions only. Go into System Properties and click the Remote tab - configure it in here. XP uses RDP 5.1 (I think?) and Vista uses the new RDP 6.0, so you'll want to enable it so that you have a broader connection range.
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

Yes, I checked that: it was set to allow any machine (not just Vista machines). Just to be on the safe side, I checked it, tried again, failed and unchecked it again, tried again and failed again.
In any case, the firewall log clearly shows that *it* is dropping the packets so I'm sure the packets never even reach the Remote Desktop service.
I don't know why it'd dropping them, though.
Ben. "Zack Whittaker (R2 Mentor)" wrote in message

You might have on the Vista machine configured to allow allow RDP 6.0 versions only. Go into System Properties and click the Remote tab - configure it in here. XP uses RDP 5.1 (I think?) and Vista uses the new RDP 6.0, so you'll want to enable it so that you have a broader connection range.
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

I'm wondering if defender is blocking the packets... What build of Vista are you using?
Have a pleasant day.
-- Jeffrey Randow (jeffreycentex@gmail.com) Windows Networking MVP http://www.networkblog.net
On Sun, 19 Feb 2006 15:45:20 +0100, "Ben Kooijman" wrote:

Yes, I checked that: it was set to allow any machine (not just Vista machines). Just to be on the safe side, I checked it, tried again, failed and unchecked it again, tried again and failed again.
In any case, the firewall log clearly shows that *it* is dropping the packets so I'm sure the packets never even reach the Remote Desktop service.
I don't know why it'd dropping them, though.
Ben. "Zack Whittaker (R2 Mentor)" wrote in message You might have on the Vista machine configured to allow allow RDP 6.0 versions only. Go into System Properties and click the Remote tab - configure it in here. XP uses RDP 5.1 (I think?) and Vista uses the new RDP 6.0, so you'll want to enable it so that you have a broader connection range.
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

Build 5270.
"Jeffrey Randow [MVP]" wrote in message

I'm wondering if defender is blocking the packets... What build of Vista are you using?
Have a pleasant day.
-- Jeffrey Randow (jeffreycentex@gmail.com) Windows Networking MVP http://www.networkblog.net
On Sun, 19 Feb 2006 15:45:20 +0100, "Ben Kooijman" <jvdvyah@yahoo.com wrote:
Yes, I checked that: it was set to allow any machine (not just Vista machines). Just to be on the safe side, I checked it, tried again, failed and unchecked it again, tried again and failed again.
In any case, the firewall log clearly shows that *it* is dropping the packets so I'm sure the packets never even reach the Remote Desktop service.
I don't know why it'd dropping them, though.
Ben. "Zack Whittaker (R2 Mentor)" wrote in message You might have on the Vista machine configured to allow allow RDP 6.0 versions only. Go into System Properties and click the Remote tab - configure it in here. XP uses RDP 5.1 (I think?) and Vista uses the new RDP 6.0, so you'll want to enable it so that you have a broader connection range.
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

Quite likely. Make sure you're disconnected from the Internet (not the network) to enable full security still, and disable the Windows Defender service in services.msc. Try the remote connection again, and see if that helps.
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

Will do. I'll post the results. Thanks.
"Zack Whittaker (R2 Mentor)" wrote in message

Quite likely. Make sure you're disconnected from the Internet (not the network) to enable full security still, and disable the Windows Defender service in services.msc. Try the remote connection again, and see if that helps.
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

Hi Ben,
I am experiencing your issue, I tried to connect to Vista from Windows XP x64 and I keep getting a connection error to make sure I am using the correct computer name or ip address. This happens under a UAP and NON-UAP account. I'm gonna file a bug report. -- -- Andre Windows Connect | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm "Ben Kooijman" wrote in message

Will do. I'll post the results. Thanks.
"Zack Whittaker (R2 Mentor)" wrote in message Quite likely. Make sure you're disconnected from the Internet (not the network) to enable full security still, and disable the Windows Defender service in services.msc. Try the remote connection again, and see if that helps.
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

I forgot to add that I am using a pure residential account from my ISP. In my case I use a free dynamic naming service from No-IP.com that maps a fully qualified domain name (FQDN) or alias if you will to my ISP's dynamically assigned IP address. I simply call home using the alias.
http://www.no-ip.com
-- 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...
"Sooner Al [MVP]" wrote in message news:...

You could, at least with XP Pro, run Remote Desktop through a VPN or Secure Shell (SSH) tunnel for added security. I have done both and currently use OpenVPN.
With OpenVPN you need a cert, key and you protect the key with a strong password. With SSH you can use a key pair protected with a strong password.
-- 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...
"Puppy Breath" wrote in message Yeah, that makes sense. With my ISP I'd have to upgrade my home account to a business account for that. I was looking for the free/easy/mindless way to do it. Something like Remote Assistance without needing someone on the other side to respond when you click Request Control. You connect through an RA ticket or just by entering the IP addresses from that ticket into some prompt, enter the password, and you're connected.
Not the most secure thing in the world. But hey, we're talking about a home network with a dynamic IP address. It's not like it would be exposed all the time. You'd just have to remember to generate an RA ticket or check your IP address before you leave.
"Zack Whittaker" wrote in message Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Puppy Breath" wrote in message The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

Thanks for the tip. I guess it's mainly the "free" part I'm interested in, because I'd rarely ever have to connect to my home network remotely.
"Sooner Al [MVP]" wrote in message

I forgot to add that I am using a pure residential account from my ISP. In my case I use a free dynamic naming service from No-IP.com that maps a fully qualified domain name (FQDN) or alias if you will to my ISP's dynamically assigned IP address. I simply call home using the alias.
http://www.no-ip.com
-- 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...
"Sooner Al [MVP]" wrote in message news:... You could, at least with XP Pro, run Remote Desktop through a VPN or Secure Shell (SSH) tunnel for added security. I have done both and currently use OpenVPN.
With OpenVPN you need a cert, key and you protect the key with a strong password. With SSH you can use a key pair protected with a strong password.
-- 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...
"Puppy Breath" wrote in message Yeah, that makes sense. With my ISP I'd have to upgrade my home account to a business account for that. I was looking for the free/easy/mindless way to do it. Something like Remote Assistance without needing someone on the other side to respond when you click Request Control. You connect through an RA ticket or just by entering the IP addresses from that ticket into some prompt, enter the password, and you're connected.
Not the most secure thing in the world. But hey, we're talking about a home network with a dynamic IP address. It's not like it would be exposed all the time. You'd just have to remember to generate an RA ticket or check your IP address before you leave.
"Zack Whittaker" wrote in message Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Puppy Breath" wrote in message The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

I like free... Everything I mentioned is free by the way...ie. OpenVPN, SSH (I used the free copSSH server package), PuTTY a free SSH client and of course Remote Desktop...
-- 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...
"Puppy Breath" wrote in message

Thanks for the tip. I guess it's mainly the "free" part I'm interested in, because I'd rarely ever have to connect to my home network remotely.
"Sooner Al [MVP]" wrote in message I forgot to add that I am using a pure residential account from my ISP. In my case I use a free dynamic naming service from No-IP.com that maps a fully qualified domain name (FQDN) or alias if you will to my ISP's dynamically assigned IP address. I simply call home using the alias.
http://www.no-ip.com
-- 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...
"Sooner Al [MVP]" wrote in message news:... You could, at least with XP Pro, run Remote Desktop through a VPN or Secure Shell (SSH) tunnel for added security. I have done both and currently use OpenVPN.
With OpenVPN you need a cert, key and you protect the key with a strong password. With SSH you can use a key pair protected with a strong password.
-- 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...
"Puppy Breath" wrote in message Yeah, that makes sense. With my ISP I'd have to upgrade my home account to a business account for that. I was looking for the free/easy/mindless way to do it. Something like Remote Assistance without needing someone on the other side to respond when you click Request Control. You connect through an RA ticket or just by entering the IP addresses from that ticket into some prompt, enter the password, and you're connected.
Not the most secure thing in the world. But hey, we're talking about a home network with a dynamic IP address. It's not like it would be exposed all the time. You'd just have to remember to generate an RA ticket or check your IP address before you leave.
"Zack Whittaker" wrote in message Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Puppy Breath" wrote in message The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Puppy Breath" wrote in message

The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

Yeah, that makes sense. With my ISP I'd have to upgrade my home account to a business account for that. I was looking for the free/easy/mindless way to do it. Something like Remote Assistance without needing someone on the other side to respond when you click Request Control. You connect through an RA ticket or just by entering the IP addresses from that ticket into some prompt, enter the password, and you're connected.
Not the most secure thing in the world. But hey, we're talking about a home network with a dynamic IP address. It's not like it would be exposed all the time. You'd just have to remember to generate an RA ticket or check your IP address before you leave.
"Zack Whittaker" wrote in message

Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Puppy Breath" wrote in message The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

You could, at least with XP Pro, run Remote Desktop through a VPN or Secure Shell (SSH) tunnel for added security. I have done both and currently use OpenVPN.
With OpenVPN you need a cert, key and you protect the key with a strong password. With SSH you can use a key pair protected with a strong password.
-- 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...
"Puppy Breath" wrote in message

Yeah, that makes sense. With my ISP I'd have to upgrade my home account to a business account for that. I was looking for the free/easy/mindless way to do it. Something like Remote Assistance without needing someone on the other side to respond when you click Request Control. You connect through an RA ticket or just by entering the IP addresses from that ticket into some prompt, enter the password, and you're connected.
Not the most secure thing in the world. But hey, we're talking about a home network with a dynamic IP address. It's not like it would be exposed all the time. You'd just have to remember to generate an RA ticket or check your IP address before you leave.
"Zack Whittaker" wrote in message Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Puppy Breath" wrote in message The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

By "cert" you mean like an SSL certificate or something?
"Sooner Al [MVP]" wrote in message

You could, at least with XP Pro, run Remote Desktop through a VPN or Secure Shell (SSH) tunnel for added security. I have done both and currently use OpenVPN.
With OpenVPN you need a cert, key and you protect the key with a strong password. With SSH you can use a key pair protected with a strong password.
-- 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...
"Puppy Breath" wrote in message Yeah, that makes sense. With my ISP I'd have to upgrade my home account to a business account for that. I was looking for the free/easy/mindless way to do it. Something like Remote Assistance without needing someone on the other side to respond when you click Request Control. You connect through an RA ticket or just by entering the IP addresses from that ticket into some prompt, enter the password, and you're connected.
Not the most secure thing in the world. But hey, we're talking about a home network with a dynamic IP address. It's not like it would be exposed all the time. You'd just have to remember to generate an RA ticket or check your IP address before you leave.
"Zack Whittaker" wrote in message Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Puppy Breath" wrote in message The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

Yes...With OpenVPN you roll your own...
http://theillustratednetwork.mvps.org/OpenVPN/OpenVPN.html
-- 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...
"Puppy Breath" wrote in message

By "cert" you mean like an SSL certificate or something?
"Sooner Al [MVP]" wrote in message You could, at least with XP Pro, run Remote Desktop through a VPN or Secure Shell (SSH) tunnel for added security. I have done both and currently use OpenVPN.
With OpenVPN you need a cert, key and you protect the key with a strong password. With SSH you can use a key pair protected with a strong password.
-- 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...
"Puppy Breath" wrote in message Yeah, that makes sense. With my ISP I'd have to upgrade my home account to a business account for that. I was looking for the free/easy/mindless way to do it. Something like Remote Assistance without needing someone on the other side to respond when you click Request Control. You connect through an RA ticket or just by entering the IP addresses from that ticket into some prompt, enter the password, and you're connected.
Not the most secure thing in the world. But hey, we're talking about a home network with a dynamic IP address. It's not like it would be exposed all the time. You'd just have to remember to generate an RA ticket or check your IP address before you leave.
"Zack Whittaker" wrote in message Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Puppy Breath" wrote in message The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

Cool, thanks all.
"Sooner Al [MVP]" wrote in message

Yes...With OpenVPN you roll your own...
http://theillustratednetwork.mvps.org/OpenVPN/OpenVPN.html
-- 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...
"Puppy Breath" wrote in message By "cert" you mean like an SSL certificate or something?
"Sooner Al [MVP]" wrote in message You could, at least with XP Pro, run Remote Desktop through a VPN or Secure Shell (SSH) tunnel for added security. I have done both and currently use OpenVPN.
With OpenVPN you need a cert, key and you protect the key with a strong password. With SSH you can use a key pair protected with a strong password.
-- 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...
"Puppy Breath" wrote in message Yeah, that makes sense. With my ISP I'd have to upgrade my home account to a business account for that. I was looking for the free/easy/mindless way to do it. Something like Remote Assistance without needing someone on the other side to respond when you click Request Control. You connect through an RA ticket or just by entering the IP addresses from that ticket into some prompt, enter the password, and you're connected.
Not the most secure thing in the world. But hey, we're talking about a home network with a dynamic IP address. It's not like it would be exposed all the time. You'd just have to remember to generate an RA ticket or check your IP address before you leave.
"Zack Whittaker" wrote in message Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Puppy Breath" wrote in message The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

Hi Sooner Al,
Have you try SSH tunnel in Windows Vista? In XP SP2, I am using Putty to set up a SSH tunnel and use the XP Remote Desktop. It works fine. However, using the same Putty and the same parameters in Windows Vista's Remote Desktop (for example, in the Computer box, I put 127.0.0.1:3390), it doesn't work. I got an error message: "The client could not connect. You are already connected to the console of this computer. Anew console session cannot be established." It is because this beta of Windows Vista doesn't know how to deal with SSH tunnel set up by Putty? or it requires other way to perform the tunnelling?
---kam
"Sooner Al [MVP]" wrote:

You could, at least with XP Pro, run Remote Desktop through a VPN or Secure Shell (SSH) tunnel for added security. I have done both and currently use OpenVPN.
With OpenVPN you need a cert, key and you protect the key with a strong password. With SSH you can use a key pair protected with a strong password.
-- 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...
"Puppy Breath" wrote in message Yeah, that makes sense. With my ISP I'd have to upgrade my home account to a business account for that. I was looking for the free/easy/mindless way to do it. Something like Remote Assistance without needing someone on the other side to respond when you click Request Control. You connect through an RA ticket or just by entering the IP addresses from that ticket into some prompt, enter the password, and you're connected.
Not the most secure thing in the world. But hey, we're talking about a home network with a dynamic IP address. It's not like it would be exposed all the time. You'd just have to remember to generate an RA ticket or check your IP address before you leave.
"Zack Whittaker" wrote in message Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Puppy Breath" wrote in message The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

Hi Sooner Al,
I am using Putty (for SSH tunnel) with XP SP2 Remote Desktop. It works fine.
However, while I use the same Putty and parameters in Windows Vista Remote Desktop, I get this error message: "The client could not connect. You are already connected to the console of this computer. A new sonsole session cannot be established."
Do you know what is the reason?
---kam
"Sooner Al [MVP]" wrote:

Yes...With OpenVPN you roll your own...
http://theillustratednetwork.mvps.org/OpenVPN/OpenVPN.html
-- 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...
"Puppy Breath" wrote in message By "cert" you mean like an SSL certificate or something?
"Sooner Al [MVP]" wrote in message You could, at least with XP Pro, run Remote Desktop through a VPN or Secure Shell (SSH) tunnel for added security. I have done both and currently use OpenVPN.
With OpenVPN you need a cert, key and you protect the key with a strong password. With SSH you can use a key pair protected with a strong password.
-- 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...
"Puppy Breath" wrote in message Yeah, that makes sense. With my ISP I'd have to upgrade my home account to a business account for that. I was looking for the free/easy/mindless way to do it. Something like Remote Assistance without needing someone on the other side to respond when you click Request Control. You connect through an RA ticket or just by entering the IP addresses from that ticket into some prompt, enter the password, and you're connected.
Not the most secure thing in the world. But hey, we're talking about a home network with a dynamic IP address. It's not like it would be exposed all the time. You'd just have to remember to generate an RA ticket or check your IP address before you leave.
"Zack Whittaker" wrote in message Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Puppy Breath" wrote in message The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

Unfortunately I am about a week to two weeks away from installing my first Vista machine so I can't really answer that question. Hopefully someone else can help further...
-- 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...
"kwan" wrote in message

Hi Sooner Al,
I am using Putty (for SSH tunnel) with XP SP2 Remote Desktop. It works fine.
However, while I use the same Putty and parameters in Windows Vista Remote Desktop, I get this error message: "The client could not connect. You are already connected to the console of this computer. A new sonsole session cannot be established."
Do you know what is the reason?
---kam
"Sooner Al [MVP]" wrote:
Yes...With OpenVPN you roll your own...
http://theillustratednetwork.mvps.org/OpenVPN/OpenVPN.html
-- 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...
"Puppy Breath" wrote in message By "cert" you mean like an SSL certificate or something?
"Sooner Al [MVP]" wrote in message You could, at least with XP Pro, run Remote Desktop through a VPN or Secure Shell (SSH) tunnel for added security. I have done both and currently use OpenVPN.
With OpenVPN you need a cert, key and you protect the key with a strong password. With SSH you can use a key pair protected with a strong password.
-- 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...
"Puppy Breath" wrote in message Yeah, that makes sense. With my ISP I'd have to upgrade my home account to a business account for that. I was looking for the free/easy/mindless way to do it. Something like Remote Assistance without needing someone on the other side to respond when you click Request Control. You connect through an RA ticket or just by entering the IP addresses from that ticket into some prompt, enter the password, and you're connected.
Not the most secure thing in the world. But hey, we're talking about a home network with a dynamic IP address. It's not like it would be exposed all the time. You'd just have to remember to generate an RA ticket or check your IP address before you leave.
"Zack Whittaker" wrote in message Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "Puppy Breath" wrote in message The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

Hello kwan, Do you know if Putty has an updated or patch available for the Vista OS? Your probably ahead of the game considering not many people are in full swing with Vista. I am curious to know if Putty has an upgrade that needs to be applied in order to be fully operational in Vista.
I recently attended a Windows TechNet conference and the most important thing he said all day was; " Vista is not an upgrade from XP, it is an entirely different approach"
Danny Gallegos Roland Schorr & Tower http://www.rolandschorr.com

Hi Sooner Al,
I am using Putty (for SSH tunnel) with XP SP2 Remote Desktop. It works fine.
However, while I use the same Putty and parameters in Windows Vista Remote Desktop, I get this error message: "The client could not connect. You are already connected to the console of this computer. A new sonsole session cannot be established." Do you know what is the reason?
---kam
"Sooner Al [MVP]" wrote:
Yes...With OpenVPN you roll your own...
http://theillustratednetwork.mvps.org/OpenVPN/OpenVPN.html
-- 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... "Puppy Breath" wrote in message
By "cert" you mean like an SSL certificate or something?
"Sooner Al [MVP]" wrote in message
You could, at least with XP Pro, run Remote Desktop through a VPN or Secure Shell (SSH) tunnel for added security. I have done both and currently use OpenVPN.
With OpenVPN you need a cert, key and you protect the key with a strong password. With SSH you can use a key pair protected with a strong password.
-- 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... "Puppy Breath" wrote in message
Yeah, that makes sense. With my ISP I'd have to upgrade my home account to a business account for that. I was looking for the free/easy/mindless way to do it. Something like Remote Assistance without needing someone on the other side to respond when you click Request Control. You connect through an RA ticket or just by entering the IP addresses from that ticket into some prompt, enter the password, and you're connected.
Not the most secure thing in the world. But hey, we're talking about a home network with a dynamic IP address. It's not like it would be exposed all the time. You'd just have to remember to generate an RA ticket or check your IP address before you leave.
"Zack Whittaker" wrote in message
Well, it can be as simple as that yeh. All you need is an external IP of which your router or ISP can provide you with, or a direct port or something like that.
I've done it with mine - I've got my computer names linked up to ***.zacknet.co.uk so I can access them wherever I go :o)
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up! --: Original message follows :-- "Puppy Breath" wrote in message The Remote Desktop documentation in Windows Ultimate (5308) is a little confusing, as though it's not just a client. But it couldn't possibly be the sort of thing where I just leave my home PC online through my ISP, then connect to it remotely across the Internet, right? My home machine would need a FQDN for me to even be able to find it from afar, right? Not to mention Terminal Services, a Web server, or something.

I test the remote desktop connection from vista itself - it was ok to connect although as we expect, it disallow connection because it can not create another console session and I ma already connected to console.
When I try to connect form another PC, I don't get any connection despite the vista firewall ahs been set correctly.
what else do I have to do?