Re: RDP on ANY port other than 3389 (i.e., 3390, 3391, ETC.) Solved??
From: Bill Sanderson (Bill_Sanderson_at_msn.com.plugh.org)
Date: 11/29/04
- Next message: Bill Sanderson: "Re: Right-Click not working with Remote Desktop"
- Previous message: Sven Berg: "Re: Switch control in RDC on XP SP2"
- In reply to: guruuno: "RDP on ANY port other than 3389 (i.e., 3390, 3391, ETC.) Solved??"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 29 Nov 2004 17:34:04 -0500
Adding a rule to the firewall should work.
Let me see if I can get that tested.
Sorry short delay - I am testing with a laptop which always hibernates, and
on which I had set a CHKDSK to happen on next reboot--ever notice how
annoying that is when you forget it is going to happen?
OK--after the reboot, ping still works (echo responses are turned on in
firewall settings).
Telnet to 3389 fails, telnet to 3390 fails.
OK--create new port exception, called rdp 3390, port 3390, TCP.
Telnet to 3389 fails, telnet to 3390 appears to do what I'd expect.
MSTSC at the command prompt with the argument: 192.168.2.28:3390 fails
However, if I run MSTSC <enter>
and enter the argument 192.168.2.28:3390, it works just fine.
So--the new exception in the firewall works, the port change worked, so it
all works as documented.
So--what are you doing wrong?
"guruuno" <guruuno@hotmail.com> wrote in message
news:961401c4d4aa$fc832b00$a401280a@phx.gbl...
> Did this thread die?
> Does anyone have a resolve?
- Next message: Bill Sanderson: "Re: Right-Click not working with Remote Desktop"
- Previous message: Sven Berg: "Re: Switch control in RDC on XP SP2"
- In reply to: guruuno: "RDP on ANY port other than 3389 (i.e., 3390, 3391, ETC.) Solved??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|