Re: How do I open Port 3389

I did restart after changing it in the registry. I also did a virus scan in
case there was a virus involved; it came up clean. Is there a way to
reinstall or reset Remote Desktop on the client?

"Claus" wrote:

Well, that is really weird. RDP in the Registry should be on 3389. Did you
restart the computer after you made that change?

I wonder what else has been changed on those 2 boxes. I'm almost tempted to
advise you to wipe the box and install from scratch.

--
Claus
"rfIPS" <rfIPS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6DCC5035-C989-42E4-8A9E-E86AACFD7ABE@xxxxxxxxxxxxxxxx
For some reason, regedit.exe was missing from this desktop so I had to
reinstall.

I found out the value for PortNumber under HKEY_LOCAL_MACHINE - System -
CurrentControlSet - Control -Terminal Server - WinStations - RDP-tcp was
set
to 3399. In Windows Firewall exceptions, RDC is configured to use 3389. I
changed the value in the registry to 3389 to see if it would work and it
didn't. I wasn't able to edit the value in the Exceptions list, it
wouldn't
let me. Probably because of domain policy? And, I wasn't allowed to
disable
the Windows Firewall because of Domain Policy; I tried via command line,
too.
Before I go thru the hassle of going to the GPO to exclude this desktop
from
the domain policy, I thought I'd check to see if you had any suggestions.

Thanks again!

"Claus" wrote:

QB is not using 3389. Clicking on the checkbox for RDP under the computer
properties is normally all you need to do. Disabling Firewall and AV for
testing would be my next step. If it still doesn't work I'm out of ideas
at
the moment.

--
Claus
"rfIPS" <rfIPS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:72945E21-5ABE-446B-B004-3E03DA4FDA03@xxxxxxxxxxxxxxxx
Hi Claus, I did try to add Port 3389 to the exception list and got the
error
message that it was already being used for Remote Desktop Connection.
How
can
I find out if there is an application using this port already? Off the
top
of
my head, the only application I can think of that is being used on
these
desktops and not others is Quickbooks. That being said, I have another
desktop that has Quickbooks and the user is able to successfully log in
to
her computer remotely. And, I will test turning off the firewall when I
am
able to access the system physically.

"Claus" wrote:

I would still test it. Also, if you have the firewall running on those
2
boxes try to add 3389 to the exception list. Something is different on
those
2 boxes and these test will help you finding the cause.

--
Claus
"rfIPS" <rfIPS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:937D6174-E081-4F7B-8B7F-4D05124B06A7@xxxxxxxxxxxxxxxx
Hi! Thanks for replying to my post. Yes, NAV is installed on this
system
as
well as all the other 23 systems. Not sure why it would be a problem
on
2
but
not the others. I haven't tried disabling it; I will do that when
I'm
back
in
the office Mon., just to see.

"Claus" wrote:

Any Antivirus software installed on those boxes? Have you tried
disabling
it?

--
Claus
"rfIPS" <rfIPS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B5C87EFD-B6EE-4EB0-B945-04E2C6AA1AD5@xxxxxxxxxxxxxxxx
I have two desktops in our 25 client LAN that will not allow
Remote
Desktop
Connections. I ran a netstat -ano and couldn't find a listing for
port
3389
listening. I also could not telnet in using Telnet command.
Terminal
services
is running. I checked that Remote Desktop was selected in the
system
properties and that the appropriate users were added for access.
I
checked
Windows Firewall and see that it is configured for access. I
tried
to
add
Port 3389 and got a message "can't use that port, it is in use
for
remote
desktop" or something like that.

Is there something blocking it? How do I find out or, how can I
open
it?

I need help! I have a user that needs to be able to access from
home.
BTW,
I
tried to access from outside the LAN and inside the LAN with no
success.

Thx in advance.












.

Relevant Pages

  • Re: How do I open Port 3389
    ... In Windows Firewall exceptions, RDC is configured to use 3389. ... Disabling Firewall and AV ... message that it was already being used for Remote Desktop ... I find out if there is an application using this port already? ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I open Port 3389
    ... In Windows Firewall exceptions, RDC is configured to use 3389. ... message that it was already being used for Remote Desktop Connection. ... I find out if there is an application using this port already? ... I haven't tried disabling it; ...
    (microsoft.public.windows.server.sbs)
  • Re: GPO for Remote Desktop and Firewall Settings
    ... pasted below is the settings as shown in the GPO Edit, ... Windows Firewall: ... > "Allows this computer to receive Remote Desktop requests. ... > Windows Firewall opens this port so that this computer can receive Remote ...
    (microsoft.public.win2000.group_policy)
  • Re: How do I open Port 3389
    ... message that it was already being used for Remote Desktop Connection. ... I find out if there is an application using this port already? ... I will test turning off the firewall when I am ... I haven't tried disabling it; I will do that when I'm ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I open Port 3389
    ... In Windows Firewall exceptions, RDC is configured to use 3389. ... message that it was already being used for Remote Desktop Connection. ... I find out if there is an application using this port already? ...
    (microsoft.public.windows.server.sbs)