Hello

I have a lan with 2 XP Pro pc behind a router with a static wan ip, I
connect to them remotely with remote desktop.

I have forwarded in the router
port 3389 to 3389 PC A
port 3391 to 3389 PC B

From a vista pro remote desktop client, I connect to PC A without
problem
but I can't connect to PC B, as soon as I type IPort it displays
"syntax error"
I also use this vista pc to connect to another server on a different
Wan address and it works.

from a xp remote desktop client it just works fine, it connects to PC
A by typing IP and to PC B by typing IP:3391

Why can't I specify a port to use in vista remote desktop client in
the form IPort
I really don't understand....

Thank you if you can help me!

Marie

Hi
You have to alter one Remote Desktop to work with the None default ports.
http://support.microsoft.com/kb/306759
http://windowshelp.microsoft.com/Win...c61e61033.mspx
Jack (MVP-Networking).

wrote in message
...
Hello

I have a lan with 2 XP Pro pc behind a router with a static wan ip, I
connect to them remotely with remote desktop.

I have forwarded in the router
port 3389 to 3389 PC A
port 3391 to 3389 PC B

From a vista pro remote desktop client, I connect to PC A without
problem
but I can't connect to PC B, as soon as I type IPort it displays
"syntax error"
I also use this vista pc to connect to another server on a different
Wan address and it works.

from a xp remote desktop client it just works fine, it connects to PC
A by typing IP and to PC B by typing IP:3391

Why can't I specify a port to use in vista remote desktop client in
the form IPort
I really don't understand....

Thank you if you can help me!

Marie

Are you sure its not a router issue with port redirection of TCP Port 3391
to 3389? How about reversing the port redirection, ie. addressing PC A with
3391 and PC B with 3389 as a test. You also might try a different port, ie.
TCP Port 12345 for example.

If you can address another PC from the Vista client with TCP Port 3391 or
higher its not an issue with the Vista client.

FWIW, I have never seen that issue...

--

Al Jarvi (MS-MVP Windows - Desktop User Experience)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375

wrote in message
...
Hello

I have a lan with 2 XP Pro pc behind a router with a static wan ip, I
connect to them remotely with remote desktop.

I have forwarded in the router
port 3389 to 3389 PC A
port 3391 to 3389 PC B

From a vista pro remote desktop client, I connect to PC A without
problem
but I can't connect to PC B, as soon as I type IPort it displays
"syntax error"
I also use this vista pc to connect to another server on a different
Wan address and it works.

from a xp remote desktop client it just works fine, it connects to PC
A by typing IP and to PC B by typing IP:3391

Why can't I specify a port to use in vista remote desktop client in
the form IPort
I really don't understand....

Thank you if you can help me!

Marie

On 18 mar, 12:39, "Sooner Al [MVP]"
wrote:
Are you sure its not a router issue with port redirection of TCP Port 3391
to 3389? How about reversing the port redirection, ie. addressing PC A with
3391 and PC B with 3389 as a test. You also might try a different port, ie.
TCP Port 12345 for example.

If you can address another PC from the Vista client with TCP Port 3391 or
higher its not an issue with the Vista client.

FWIW, I have never seen that issue...

--

Al Jarvi (MS-MVP Windows - Desktop User Experience)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program -http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a questionhttp://support.microsoft.com/KB/555375



Thank you for your answer.

I don't think it is a router issue as I can connect this way from a xp
home client to PC A and to PC B. But I'll try as you suggest,
reversing the port redirection or trying another port.

Firstly I have thought it could be a firewall issue, but I have
allowed port 3391 outgoing and I still have the same problem.

Marie