Hello all,
I have managed to install Vista today but unfortunately I cannot make the
remote desktop connection work.
3389 is forwarded to my pc at internal ip of pc.
Remote desktop connection is enabled,
I can reach the pc and use rdc smooth from a machine running xp, from an
inside the private network but I cannot reach it from the outside!!!
I know it isn't NAT - router matter.
From firewall the program is allowed. I cannot telnet the pc outside the
network, but the hostname is valid and tracert-ed. It drives me mad...I am in
the awful position to think to go back to XP as remote desktop connection is
very important to me.
I have no third party programs (firewall or internet security software)
Is there anything I can do?
I am running Vista Business

--
Student Partner
Microsoft Hellas

On Sun, 11 Mar 2007 18:26:11 -0700, Aggelos Mpimpoudis
wrote:

Hello all,
I have managed to install Vista today but unfortunately I cannot make the
remote desktop connection work.
3389 is forwarded to my pc at internal ip of pc.
Remote desktop connection is enabled,
I can reach the pc and use rdc smooth from a machine running xp, from an
inside the private network but I cannot reach it from the outside!!!
I know it isn't NAT - router matter.
From firewall the program is allowed. I cannot telnet the pc outside the
network, but the hostname is valid and tracert-ed. It drives me mad...I am in
the awful position to think to go back to XP as remote desktop connection is
very important to me.
I have no third party programs (firewall or internet security software)
Is there anything I can do?
I am running Vista Business

Just to clarify.
Inside, you used RDC with the PC name with success.
Outside you used the ROUTER (with the port 3389 forwarded to the
STATIC IP of the PC) IP address?

You used the latest XP RDC CLIENT (I think there are tweaks for Vista
included) that was available in Microsoft Update?
You 'Allowed' a less than fully 'authenticated' connection?

"Steve Urbach" wrote:

Just to clarify.
Inside, you used RDC with the PC name with success.

Correct

Outside you used the ROUTER (with the port 3389 forwarded to the
STATIC IP of the PC) IP address?

Dynamic DNS....indeed

You used the latest XP RDC CLIENT (I think there are tweaks for Vista
included) that was available in Microsoft Update?
You 'Allowed' a less than fully 'authenticated' connection?

The Computer I have used, from inside the network had the regular RDC (not
the latest edition) and worked smooth. Using tha same pc located from an
outside location using the hostname of my router, I expect simply to forward
the request to the local address of the vista box at the port 3389 as i have
specified, but I cannot... "The client cannot connect to the remote computer"
Before my Vista era I used RDC every day...same settings and I cannot
connect even with telnet........ Is there anything with the firewall rules??

--
Student Partner
Microsoft Hellas

"Aggelos Mpimpoudis" wrote
in message ...
"Steve Urbach" wrote:

Just to clarify.
Inside, you used RDC with the PC name with success.

Correct

Outside you used the ROUTER (with the port 3389 forwarded to the
STATIC IP of the PC) IP address?

Dynamic DNS....indeed

You used the latest XP RDC CLIENT (I think there are tweaks for Vista
included) that was available in Microsoft Update?
You 'Allowed' a less than fully 'authenticated' connection?

The Computer I have used, from inside the network had the regular RDC
(not
the latest edition) and worked smooth. Using tha same pc located from
an
outside location using the hostname of my router, I expect simply to
forward
the request to the local address of the vista box at the port 3389 as
i have
specified, but I cannot... "The client cannot connect to the remote
computer"
Before my Vista era I used RDC every day...same settings and I cannot
connect even with telnet........ Is there anything with the firewall
rules??


It looks like you might need to turn on Edge Traversal for the Remote
Desktop firewall rule. Go to:
Control Panel
- Administrative Tools
- Windows Firewall with Advanced Security
- Inbound Rules
- Remote Desktop
- Properties
- Advanced
and check Allow edge traversal.

See if that helps.

Regards,

Dave

Don this but I do port forwarding at router settings.

Check the Firewall log!!!!!
#Fields: date time action protocol src-ip dst-ip src-port dst-port size
tcpflags tcpsyn tcpack tcpwin icmptype icmpcode info path
2007-03-13 00:50:32 ALLOW UDP 192.168.1.33 yyy.yyy.yyy.yyy 49205 53 0 - - -
- - - - SEND
2007-03-13 00:50:32 ALLOW TCP 192.168.1.33 xxx.xxx.xxx.xxx 49162 3389 0 - 0
0 0 - - - SEND
2007-03-13 00:50:34 ALLOW TCP 192.168.1.33 xxx.xxx.xxx.xxx 49163 3389 0 - 0
0 0 - - - SEND
2007-03-13 01:05:27 ALLOW UDP 192.168.1.33 yyy.yyy.yyy.yyy 49247 53 0 - - -
- - - - SEND
2007-03-13 01:05:28 ALLOW TCP 192.168.1.33 xxx.xxx.xxx.xxx 49245 3389 0 - 0
0 0 - - - SEND
2007-03-13 01:05:29 ALLOW TCP 192.168.1.33 xxx.xxx.xxx.xxx 49246 3389 0 - 0
0 0 - - - SEND

192.168.1.33 = me
xxx.xxx.xxx.xxx = the pc that i try to achieve remote desktop connection from.
It seems wrong...Isn't it???
src ip and dest-ip ought to be at the opposite places each one...or not??
I think Port forwarding is done correctly!!!!
RemoteDesktop is also done correctly as it works from inside the network.
So???????????
Is this time to revert to XP??? grrrrrrrrrr I dont want toooo.......

--
Student Partner
Microsoft Hellas



"Dave R." wrote:


"Aggelos Mpimpoudis" wrote
in message ...
"Steve Urbach" wrote:

Just to clarify.
Inside, you used RDC with the PC name with success.

Correct

Outside you used the ROUTER (with the port 3389 forwarded to the
STATIC IP of the PC) IP address?

Dynamic DNS....indeed

You used the latest XP RDC CLIENT (I think there are tweaks for Vista
included) that was available in Microsoft Update?
You 'Allowed' a less than fully 'authenticated' connection?

The Computer I have used, from inside the network had the regular RDC
(not
the latest edition) and worked smooth. Using tha same pc located from
an
outside location using the hostname of my router, I expect simply to
forward
the request to the local address of the vista box at the port 3389 as
i have
specified, but I cannot... "The client cannot connect to the remote
computer"
Before my Vista era I used RDC every day...same settings and I cannot
connect even with telnet........ Is there anything with the firewall
rules??


It looks like you might need to turn on Edge Traversal for the Remote
Desktop firewall rule. Go to:
Control Panel
- Administrative Tools
- Windows Firewall with Advanced Security
- Inbound Rules
- Remote Desktop
- Properties
- Advanced
and check Allow edge traversal.

See if that helps.

Regards,

Dave

Well sorry about the missunderstanding, but I am very tired and I made a
mistake.
The previous records at the firewall log is the connects to the remote
desktop machine xxx.xxx.xxx.xxx (where I test from my remote desktop
cnnection) thats why there is that 3389 port at destination!!!
So there are no records at my firewall log...so

No telnet
No 3389 listening port at my pc outside the router
Port Forwarded to my pc 192.168.1.33
My pc has static ip address 192.168.1.33
DNS server of my ISP is running smooth ( I can find my pc via tracert, pings
etc etc)

So.... There isnt anything more I can do! Is there any chance the
remotedesktop needed something else too?
--
Student Partner
Microsoft Hellas



"Aggelos Mpimpoudis" wrote:

Don this but I do port forwarding at router settings.

Check the Firewall log!!!!!
#Fields: date time action protocol src-ip dst-ip src-port dst-port size
tcpflags tcpsyn tcpack tcpwin icmptype icmpcode info path
2007-03-13 00:50:32 ALLOW UDP 192.168.1.33 yyy.yyy.yyy.yyy 49205 53 0 - - -
- - - - SEND
2007-03-13 00:50:32 ALLOW TCP 192.168.1.33 xxx.xxx.xxx.xxx 49162 3389 0 - 0
0 0 - - - SEND
2007-03-13 00:50:34 ALLOW TCP 192.168.1.33 xxx.xxx.xxx.xxx 49163 3389 0 - 0
0 0 - - - SEND
2007-03-13 01:05:27 ALLOW UDP 192.168.1.33 yyy.yyy.yyy.yyy 49247 53 0 - - -
- - - - SEND
2007-03-13 01:05:28 ALLOW TCP 192.168.1.33 xxx.xxx.xxx.xxx 49245 3389 0 - 0
0 0 - - - SEND
2007-03-13 01:05:29 ALLOW TCP 192.168.1.33 xxx.xxx.xxx.xxx 49246 3389 0 - 0
0 0 - - - SEND

192.168.1.33 = me
xxx.xxx.xxx.xxx = the pc that i try to achieve remote desktop connection from.
It seems wrong...Isn't it???
src ip and dest-ip ought to be at the opposite places each one...or not??
I think Port forwarding is done correctly!!!!
RemoteDesktop is also done correctly as it works from inside the network.
So???????????
Is this time to revert to XP??? grrrrrrrrrr I dont want toooo.......

--
Student Partner
Microsoft Hellas



"Dave R." wrote:


"Aggelos Mpimpoudis" wrote
in message ...
"Steve Urbach" wrote:

Just to clarify.
Inside, you used RDC with the PC name with success.

Correct

Outside you used the ROUTER (with the port 3389 forwarded to the
STATIC IP of the PC) IP address?

Dynamic DNS....indeed

You used the latest XP RDC CLIENT (I think there are tweaks for Vista
included) that was available in Microsoft Update?
You 'Allowed' a less than fully 'authenticated' connection?

The Computer I have used, from inside the network had the regular RDC
(not
the latest edition) and worked smooth. Using tha same pc located from
an
outside location using the hostname of my router, I expect simply to
forward
the request to the local address of the vista box at the port 3389 as
i have
specified, but I cannot... "The client cannot connect to the remote
computer"
Before my Vista era I used RDC every day...same settings and I cannot
connect even with telnet........ Is there anything with the firewall
rules??


It looks like you might need to turn on Edge Traversal for the Remote
Desktop firewall rule. Go to:
Control Panel
- Administrative Tools
- Windows Firewall with Advanced Security
- Inbound Rules
- Remote Desktop
- Properties
- Advanced
and check Allow edge traversal.

See if that helps.

Regards,

Dave

On Mon, 12 Mar 2007 17:21:05 -0700, Aggelos Mpimpoudis
wrote:

Well sorry about the missunderstanding, but I am very tired and I made a
mistake.
The previous records at the firewall log is the connects to the remote
desktop machine xxx.xxx.xxx.xxx (where I test from my remote desktop
cnnection) thats why there is that 3389 port at destination!!!
So there are no records at my firewall log...so

No telnet
No 3389 listening port at my pc outside the router
Port Forwarded to my pc 192.168.1.33
My pc has static ip address 192.168.1.33
DNS server of my ISP is running smooth ( I can find my pc via tracert, pings
etc etc)

So.... There isnt anything more I can do! Is there any chance the
remotedesktop needed something else too?
Hmmm.

Port forward: is TCP (not UDP)?
by any chance is there a duplicate(3389) forwarded to another IP (the
router should have squawked "foul" g )?

RDC from the outside (Netgear router NAT) works for me.
did you try turning off uPNP in Vista ?

I have the same issue - i can remote desktop in, but an not connect via a
remote desktop invitation to share the screen.

Error:
A Remote Assistance connection could not be established. You may want to
check for network issues or determine if the invitation expired or was
cancelled by the person who sent it.

router forwarded port 3389 to Vista Host - Is there another port for Remote
Assistance?

On Tue, 13 Mar 2007 13:40:08 -0700, AP123
wrote:

I have the same issue - i can remote desktop in, but an not connect via a
remote desktop invitation to share the screen.

Error:
A Remote Assistance connection could not be established. You may want to
check for network issues or determine if the invitation expired or was
cancelled by the person who sent it.

router forwarded port 3389 to Vista Host - Is there another port for Remote
Assistance?
Remote desktop and Remote assistance are not the same thing.
I use the former (RDC) and do not use the latter (RA), so I am unable
to help with that one other than my experience with RA is it is
*stupid* in that it sends the IP of the computer that is behind a NAT
router (If you don't believe me, open the invitation with a hex
editor). RA needs to send the PUBLIC IP, not the local IP and the USER
needs to have set up Port Forwarding in advance. Feedback was sent on
this during CPP.