Vista-2-Vista Remote Desktop using a secure Windows Internet Computer name

[Sooner Al [MVP]]

FWIW department...

I finally was able to connect to my Vista Ultimate desktop PC using a secure
Windows Internet Computer name. In my case the router is a Belkin F5D7230-4
ver
6002 running the F5D7230-4_US_8.02.25 firmware release. As an admin user I
generated a secure Windows Internet Computer name on the Vista Ultimate
desktop PC following the procedure on this page.

http://www.microsoft.com/technet/network/p2p/wicn.mspx

Previously I tested the router using the new Internet Connectivity
Evaluation tool...

http://www.microsoft.com/windows/using/tools/igd/default.mspx

....and discovered the router was in fact reported as a "restricted cone"
type NAT which supports Teredo. See the Teredo Overview for supported NAT
types.

http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/teredo.mspx

Note that I do configure my Vista Ultimate desktop PC and Vista Ultimate
laptop client so the Remote Desktop connection uses Network Level
Authentication (NLA). This contradicts the guidance in the previously
mentioned TechNet Windows Internet Computer name procedure which apparently
is written with a Windows XP RDP host in mind. XP does not support NLA.

http://theillustratednetwork.mvps.org/RemoteDesktop/RDP6ConfigRecommendations.html#Network

My home LAN is connected to the public internet via a cable broadband ISP.
In my case that is Cox HSI. The laptop connected to my ISP through a 56K
dialup link. The laptop was able to successfully access my home Vista
Ultimate desktop PC with Remote Desktop using its assigned secure Windows
Internet Computer name.


--

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...

 

[Robert L [MVP - Networking]]

Al,

Thank you for the information.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
FWIW department...

I finally was able to connect to my Vista Ultimate desktop PC using a secure
Windows Internet Computer name. In my case the router is a Belkin F5D7230-4
ver
6002 running the F5D7230-4_US_8.02.25 firmware release. As an admin user I
generated a secure Windows Internet Computer name on the Vista Ultimate
desktop PC following the procedure on this page.

http://www.microsoft.com/technet/network/p2p/wicn.mspx

Previously I tested the router using the new Internet Connectivity
Evaluation tool...

http://www.microsoft.com/windows/using/tools/igd/default.mspx

...and discovered the router was in fact reported as a "restricted cone"
type NAT which supports Teredo. See the Teredo Overview for supported NAT
types.

http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/teredo.mspx

Note that I do configure my Vista Ultimate desktop PC and Vista Ultimate
laptop client so the Remote Desktop connection uses Network Level
Authentication (NLA). This contradicts the guidance in the previously
mentioned TechNet Windows Internet Computer name procedure which apparently
is written with a Windows XP RDP host in mind. XP does not support NLA.

http://theillustratednetwork.mvps.org/RemoteDesktop/RDP6ConfigRecommendations.html#Network

My home LAN is connected to the public internet via a cable broadband ISP.
In my case that is Cox HSI. The laptop connected to my ISP through a 56K
dialup link. The laptop was able to successfully access my home Vista
Ultimate desktop PC with Remote Desktop using its assigned secure Windows
Internet Computer name.


--

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]]

FWIW department...

I finally was able to connect to my Vista Ultimate desktop PC using a
secure
Windows Internet Computer name. In my case the router is a Belkin
F5D7230-4 ver
6002 running the F5D7230-4_US_8.02.25 firmware release. As an admin user I
generated a secure Windows Internet Computer name on the Vista Ultimate
desktop PC following the procedure on this page.

http://www.microsoft.com/technet/network/p2p/wicn.mspx

Previously I tested the router using the new Internet Connectivity
Evaluation tool...

http://www.microsoft.com/windows/using/tools/igd/default.mspx

...and discovered the router was in fact reported as a "restricted cone"
type NAT which supports Teredo. See the Teredo Overview for supported NAT
types.

http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/teredo.mspx

Note that I do configure my Vista Ultimate desktop PC and Vista Ultimate
laptop client so the Remote Desktop connection uses Network Level
Authentication (NLA). This contradicts the guidance in the previously
mentioned TechNet Windows Internet Computer name procedure which
apparently
is written with a Windows XP RDP host in mind. XP does not support NLA.

http://theillustratednetwork.mvps.org/RemoteDesktop/RDP6ConfigRecommendations.html#Network

My home LAN is connected to the public internet via a cable broadband ISP.
In my case that is Cox HSI. The laptop connected to my ISP through a 56K
dialup link. The laptop was able to successfully access my home Vista
Ultimate desktop PC with Remote Desktop using its assigned secure Windows
Internet Computer name.


--

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...

CORRECTION:

This paragraph should read...

"> Note that I do configure my Vista Ultimate desktop PC and Vista Ultimate

laptop client so the Remote Desktop connection uses Network Level
Authentication (NLA). This contradicts the guidance in the previously
mentioned TechNet Windows Internet Computer name procedure which
apparently
is written with a Windows XP RDP client in mind. XP does not support NLA."

Note the change to "...Windows XP RDP client..."

Sorry for the confusion...

--

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...

 

[Michael A. Bishop \(MSFT]

I know.... That's possibly my favorite mostly-unknown new Vista feature.
Pity there's no UI around it for Vista, but still.

The only thing that stops me from using it more is the fact that I don't get
full IPv6 external connectivity, so I can't resolve home names from work and
vice versa.... Still need a forwarded IPv4 port for that.

 

[Sooner Al [MVP]]

I know.... That's possibly my favorite mostly-unknown new Vista feature.
Pity there's no UI around it for Vista, but still.

Perhaps a Vista Power Toy to provide that functionality?...

--

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...