Remote Connect on WAN

Microsoft Windows 7 professional
January 11, 2010 at 07:38:46
Specs: Windows 7
Good Morning - apologies if this is a double post. I posted earlier but I think I messed up and couldn't locate this.

I recently switched to windows 7 and have run into issues attempting to remote connect to any PC across my WAN. I can remote connect to any PC in my local subnet, just not across WAN. I have admin role - using default ports for both RDP and Dameware - neither work across WAN. I can use XP to communicate just fine - this only occurs when using win 7. I was wondering if it's just something simply that has changed for the win7 and I haven't found this yet. I can disable firewalls, etc - no change.

Thanks in advance for advice and help

See More: Remote Connect on WAN

Report •

January 11, 2010 at 07:56:09
is the rdp port open or forwarded in the wan router?
It is only win7 that is not accessable via the wan but xp is?

Report •

January 11, 2010 at 08:00:10
yes, RDP is open on the router. I can do this from my XP but not from my windows 7.

Report •

January 11, 2010 at 09:58:39
Still unclear
"using default ports for both RDP and Dameware - neither work across WAN"

Are you saying you can rdp from the wan with xp but not win7?

I took your first statement to say neither work across the wan but xp works locally whereas win7 doesn't work locally

Report •

Related Solutions

January 11, 2010 at 12:27:51
Hi, sorry for the confusion.

I can use windows XP to remotely access any pc across the WAN. I cannot use windows 7 to remotely access PC across WAN.

If accessing any pc on local subnet I CAN successfully remote to any PC using winXP or win7

Report •

January 11, 2010 at 15:26:34
"XP to remotely access any pc across the WAN"

Since RDP uses port 3389 on the lan you would only have to specify the host like jims computer or without a port number.

To go across a router [WAN link] you have to do two things
1. forward the RDP port in the router
2. change the listening port on the distination pc for RDP

This means pc1= port 3389, pc2=port 3390, pc3=port3391

To access via the wan you have to specify what ports are forwarded to which internal ip. For example:
wan port ip: port number for pc1
wan port ip: port number for pc2. etc.

How are you accessing pcs across the wan? What are you putting in for the RD config?

Report •

January 13, 2010 at 13:06:27
Good info but I'm hung up on why it would operate differently when I use XP Professional instead of Windows 7.

I wasn't clear in my first post but I am only having this issue when I use my Windows 7 pc to try and remote connect to a PC across WAN. if I stay on my local subnet it works fine. If I use an XP computer I can remote connect to any pc (local subnet or across wan). So I had been wondering if they use different ports or something along those lines as for why they would act differently.

Thanks again

Report •

January 13, 2010 at 13:34:49
I am hung up on how you are rdping to other pcs across a router without specifing the listening ports.

This makes me think your "wan" isn't a wan but you are rdping to another local segment. Your local dns would resolve the name and no change of the listening port or forwarding would be required.

What are you calling a wan? Router to a different segment of pcs at work or other pcs via a point to point/frame relay/vpn link?

I don't know or have not heard of any differences in Windows 7 for RDP concerning security or protocol changes.

What dns servers are listed in xp vs win7?

Report •

Ask Question