http://www.dslreports.com/forum/r21058044 en Wed, 11 Nov 2009 12:55:58 EDT Wed, 11 Nov 2009 12:55:58 EDT http://www.dslreports.com/forum/remark,21066912 Genesis05175 : Thank you all,

I was really wondering if I was attempting to accomplish something that doesn't work as advertised.

It does work, and my real issue was DHCP. Port forwarding doesn't re-read the ip assignments; therefore port forwarding REQUIRES static ip addressing (thanks to SoonerAl.)

BTW, LeatHal I don't have a problem with the "mickey mouse" firewall, but when U offer that type of opinion please suggest what you consider adequate or more appropriate; thank you, I suspected the router/firewall, but not DHCP.

Thanks again to all,

G.]]> http://www.dslreports.com/forum/remark,21066912 Sat, 06 Sep 2008 05:23:11 EDT http://www.dslreports.com/forum/remark,21060974 SoonerAl : Can you connect to the Vista 64 Ult computer using the local IP:3391 from another PC on the same LAN? Does that work? What happens if you run the »www.canyouseeme.org test for port 3391 when your logged on the Vista 64 computer locally?

Can you connect to the third PC using its local LAN IP:3399 from another PC on the same LAN? Does that work? What happens if you run the »www.canyouseeme.org test for port 3399 when your logged on the third PC locally?

Does your router support port redirection as suggested by Leathal and as illustrated in the first link I gave you? If it does reconfigure each of your three PCs to use the default listening port, ie. TCP Port 3389, reboot and test again over the local LAN.

Its best, IMHO, to use a static LAN IP for each PC your trying to port forward to through your router. If you don't there is a possibility that the assigned IP address can change if the PC is rebooted effectively negating any port forwarding scheme you use.

The bottom line is if you can't connect over the local LAN you will never connect from a remote location.

»theillustratednetwork.mvps.org/R···sic.html

Lastly a VPN or SSH tunnel also works well, ie. you can access any PC on your network through one open port on any router the network is behind. This illustrates that...

»theillustratednetwork.mvps.org/S···ser.html
--
"When all else fails, read the instructions..."
MS-MVP Windows – Desktop User Experience]]> http://www.dslreports.com/forum/remark,21060974 Fri, 05 Sep 2008 06:39:02 EDT http://www.dslreports.com/forum/remark,21058876 anon : I usually RDP into just one LAN machine, and from that machine I RDPee into the rest of the LAN computers.]]> http://www.dslreports.com/forum/remark,21058876 Thu, 04 Sep 2008 19:44:08 EDT http://www.dslreports.com/forum/remark,21058144 Leathal : default port for RDC on all Windows OS's is 3389. You need to search on google how to change the RDP or RDC as some call it port. There is a registry setting, once you change you should reboot the machine..

My point about having a "firewall" is that on a firewall you can specify the incoming point it listens too and re-direct them to different servers on 3389 internally so you do not have to change the servers 3389 in the registry.

A mickey mouse cable/dsl nat router does not support this feature as it's not a "true" firewall, it's just a router. So you have to manually change the ports on the machines themselves and reflect the change on your mickey mouse rotuer. :)

Leathal]]> http://www.dslreports.com/forum/remark,21058144 Thu, 04 Sep 2008 17:44:40 EDT http://www.dslreports.com/forum/remark,21058044 Genesis05175 : Thank you SoonerAl, and Leathal for the reply(s).

This is where I am now(responses to "Open Port Ckeck" ):
3389 is open and working, is Server2008 Std.
3391 switches between "connection refused" and "connection timed out" on Vista 64 Ult. SP1
heard some? news about 3390/XP Pro so changed to 3399.
3399 is "connection timed out" on XP Pro Sp3.

does this help the Rx.

Also I have Westell 7500 modem-router/switch with port forwarding appropriately (otherwise 3389 wouldn't work.)

2. I see you say "static IP" it seems that the router handles the computer name ("netbios"/"workgroup") adequately (otherwise 3389 wouldn't work.) Is this a "quirk" that may help further identify the issue? If so, I'll change, it's not a big deal...

TIA

G.]]> http://www.dslreports.com/forum/remark,21058044 Thu, 04 Sep 2008 17:20:43 EDT http://www.dslreports.com/forum/remark,21057615 Leathal : If you had a firewall you wouldn't have to do this, you could just have the firewall listen on 33000 and talk to server1 on 3389, listen on 33001 and talk to server2 on 3389, and so forth. :)

The other option would be to install IIS on a independant machine and setup TSWeb on is RDC web version, then only grant access to authenticated users on the web, from there you could RDC into any machine on your LAN.

Leathal]]> http://www.dslreports.com/forum/remark,21057615 Thu, 04 Sep 2008 16:03:54 EDT http://www.dslreports.com/forum/remark,21055191 SoonerAl : See this page for help...

»theillustratednetwork.mvps.org/R···_RD.html

If you change the listening port on the second and third PCs via the registry hack you must reboot the PCs after making the change.

You can test port forwarding through the router by going to each PC and running the test on the »www.canyouseeme.org site.

Use strong passwords and NLA.

»www.microsoft.com/protect/yourse···ker.mspx

»theillustratednetwork.mvps.org/R···#Network

Note that XP SP3/SP2 RDC clients now supports NLA...

»theillustratednetwork.mvps.org/R···html#SP3

Personally I would setup a VPN or SSH server and access your PCs through the VPN or SSH tunnel. You only need to open one hole on your router and will have complete access to your PCs and shared files.
--
"When all else fails, read the instructions..."
MS-MVP Windows – Desktop User Experience]]> http://www.dslreports.com/forum/remark,21055191 Thu, 04 Sep 2008 06:53:36 EDT http://www.dslreports.com/forum/remark,21054781 anon : Have set router to forward to 3389, 3390, 3391.
PortQryV2 reports:
PortQry Version 2.0 Log File
System Date: Tue Sep 02 09:40:37 2008
Command run:
portqry -n Sunset-B03 -r 3389:3391 -l Vista-1.txt

Local computer name:
SUNSET-B03
Querying target system called:
Sunset-B03
Attempting to resolve name to IP address...
Name resolved to 192.168.1.114
querying...
TCP port 3389 (ms-wbt-server service): NOT LISTENING
TCP port 3390 (unknown service): NOT LISTENING
TCP port 3391 (unknown service): LISTENING

3391 says unknown service, however it is Listening.

WTF, how to do this]]> http://www.dslreports.com/forum/remark,21054781 Thu, 04 Sep 2008 01:37:04 EDT