remote desktop conn

[NosferatuX]

I failed to mention, if you already have SP3 installed you don't need it as it's already installed and Windows Update would've upgraded your version to 6.1. Just incase you still need it, you can download the latest one v6.1 here

 

[chinga69]

yes service pack 3 installed

cheers brad

 

[NosferatuX]

Just a thought...

I've you're able to remotely access Vista with XP on your LAN, then it points to just a router configuration, or a listening port conflict. If there are multiple computers behind the router, all computers should have their own listening ports, regardless of OS and opened subsequently on your router as well.

 

[chinga69]

ok so heres what i have found if i leave the port number as default i can remote connect to all puters on home network
once i change the port number to unique number for each puter i can no longer connect at home including the win 7 pc

so this explains why i could connect to win 7 puter from work as i left that one as the default port

cheers brad

 

[NosferatuX]

Hmmm... Interesting.

Just to make sure, since you've assigned unique listening ports to all computers, when you connect to say, computer A listening to port 7777, you connect to it by entering the IP address and it's port separated by a colon, (ex. 192.168.0.11:7777), right?

 

[chinga69]

no that doesnt let me connect just gives error message
computer not turned on
check config settings

 

[NosferatuX]

For the sake of thoroughness...

You've done the following;
Assigned a unique listening port to PC1 and picked 6666 in the registry
Configured Windows Firewall to allow communication on port 6666
Configured Third party software firewall to allow communication on port 6666
Configured Router to port forward to port 6666
Restarted computer to commit the registry changes

Repeated the above steps to PC2 and PC3

We'll use the table below as reference with your ISP IP = 202.202.202.111

Name - IP - Port - Local Connection - Behind Router
PC1 192.168.0.10 6666 192.168.0.10:6666 202.202.202.111:6666
PC2 192.168.0.11 7777 192.168.0.11:7777 202.202.202.111:7777
PC3 192.168.0.12 8888 192.168.0.12:8888 202.202.202.111:8888

Note: please excuse the formating of the table, it wont accept long spaces between characters. I hope it's understandable. I just placed separators in the heading.

To verify if the port assigned is indeed open on PC1, we'll open a command prompt and type in "netstat -an" without the quotes. On the list, you should see that IP 192.168.0.10:6666 is listening, this means that the port is open and awaiting connection.

Please verify that these were the steps you've done. Thank you

 

[chinga69]

hi ok so it looks like it doesnt like the port number i chose i tried a different one and it worked vista 64

so i know have vista64 by 2 puters unique port numbers and they work
xp machine still a no go will work on that
win7 machine i have left default as i cant find where to allow the port number through the firewall

so looks like monday night i should be able to log on to 2 x vista64 and the win7 machine

once again thanks muchly for your patience and great help

cheers brad

 

[chinga69]

ok run the command and appently i have 9 ports listening plus the one i want

 

[NosferatuX]

That's great! I hope you'd be able to crack the right configuration on the XP machine. I know how frustrating it is to have these types connection issues, it won't make you rest - LOL

Just let me know if there's something I can do to help out with the xp config that's giving you a hard time, I'll see what we can come up with.

And you are most welcome!

Nos

 

[NosferatuX]

ok run the command and appently i have 9 ports listening plus the one i want

I'm very sure that its a just a very small oversight. You'll be able to make it work

 

[chinga69]

ok so the xp machine is not listening on the port i set

 

[chinga69]

hi so i change the ports they are all listening on and now i cant get the win7 machine to answer from the work puter and the vista machine still doesn't work.
had them working with the new ports at home so must be firewall problem and i have allowed the new ports in the firewall

cheers brad
.

 

[NosferatuX]

hi so i change the ports they are all listening on and now i cant get the win7 machine to answer from the work puter and the vista machine still doesn't work.
had them working with the new ports at home so must be firewall problem and i have allowed the new ports in the firewall

cheers brad
.

As long as you're able to access them from the lan with the reconfigured ports, all should be fine and I totally agree that it's highly likely a firewall issue. I hope you get that sorted out soon

Please try using this tool from Sysinternals, TCPView it will show you detailed listings of all TCP and UDP endpoints on your system, including the local and remote addresses and state of TCP connections. Could show you which ports are used and possible conflicts from the one you chose to open

 

[chinga69]

hi still trying to get it working

i can get it to work if i set the port back to default 3389 then i can access the vista machine from work.
the only thing i can see when changing the port from default setting and i allow that port through the firewall is when i check the firewall in advanced mode i check the settings for remote desktop the port is still showing default 3389 with no way of changing it to the port i want.

cheers brad

 

[NosferatuX]

hi still trying to get it working

i can get it to work if i set the port back to default 3389 then i can access the vista machine from work.
the only thing i can see when changing the port from default setting and i allow that port through the firewall is when i check the firewall in advanced mode i check the settings for remote desktop the port is still showing default 3389 with no way of changing it to the port i want.

cheers brad

I see :huh:

What you can do is, on the machines with "personalized" ports for RDC, in your firewall, disable the default RDC rule. Make another rule which contains the port you specified for that machine copying the settings of the default RDC rule. Its just like making another exception on your firewall.

Note: Do not copy and paste the RDC rule as the copy will also be not editable.

Cheers

 

[chinga69]

I see :huh:

What you can do is, on the machines with "personalized" ports for RDC, in your firewall, disable the default RDC rule. Make another rule which contains the port you specified for that machine copying the settings of the default RDC rule. Its just like making another exception on your firewall.

Note: Do not copy and paste the RDC rule as the copy will also be not editable.

Cheers

ok thanks will give it a try

cheers brad