Unsolved

This post is more than 5 years old

53 Posts

3888

December 2nd, 2005 04:00

Remote Desktop

PV725N, W2K Powered By Windows Default OS.
I can access NAS Appliance remotely via terminal services (port 1279) or even RDP via 3389.
Router has ports forwarded to fixed IP of NAS, all works, non-issue.
However, 4 XP Pro clients on subnet (192.168.1.XXX), all have RDP enabled
as well as XP firewall enabled to allow Remote Desktop (RDP).
Each client has RDP Port changed (registry modification & reboot) to allow connections.
Router is enabled to allow forwarding of each associated port to each IP of each client.
(ie.:)
Server=192.168.1.110 RDP Port =3389 (Powervault 725N)
PC-001=192.168.1.109 RDP Port =3390
PC-002=192.168.1.108 RDP Port =3391
PC-003=192.168.1.107 RDP Port =3392
PC-004=192.168.1.106 RDP Port =3393

I cannot access any client remotely. (only NAS Appliance)
I have very similar setup at another location, all works, however, server is W2003, not W2K/NAS Appliance.

Is something specific to the whole big picture with the NAS on the network, running all the services by default (like terminal services) having any type of effect on my inability to connect to the clients remotely, or is all of that a non issue.

Did I try to connect when onsite via locally (internal IP), yes, and works.

Linksys WRT54G router

May not be the appropiate question for this forum, however, I want to be clear that there is no involvement of the Powervault 725N causing any of the issues.

Anyone?

175 Posts

December 2nd, 2005 15:00

Enabling RDP on the firewall only opens port 3389. IF you are using a custom port you need a custom rule. My suggestion would be to setup a VPN endpoint in your network.

53 Posts

December 2nd, 2005 18:00

I did not have to setup any custom port settings on any previous installs (as specified), so why now?

So, what you are saying is to change/modify/or create a new rule in the Windows Firewall for the RDP to match each port as referenced?

Thanks
No Events found!

Top