Port 3389 not listening Windows 10

Having read through quite a few posts, I'm hesitant to add another one
to the pile but here it is. I've exhausted almost all the suggestions
I have seen previously. One thing that never seems to get answered
though is how to get port 3389 to listen appropriately. It is showing
has the selected port in the registry. Here it is:

Windows 2000 server, Terminal Services configured and running however
port 3389 is not established or listening.
Troubleshooting steps already taken:
1.) Terminal Service is up and running in services.mgr
2.) I have run netstat -a -n. Port 3389 is definitely NOT listening or
established. As a double check, I have also tried to telnet to the
machine and it fails on a connection error.
3.) There is no firewall on the machine or on my internal network. In
fact, this machine has worked in the past and I have a Windows 2003 SBS
server that works.
4.) The machine was running in Application Server Mode, but I have
since switched it to Remote Administration mode just to check if it
could be an issue with my License server. This had no effect.
5.) I removed Symanted Antivirus Corporate Edition, just in case it
was blocking port 3389.
6.) I have insured that no filters are running on my network connection
that might prohibit entry through this port.
7.) I have tried changing the port that Terminal Services use.
8.) I have tried reinstalling (through upgrade) the operating system.
I tried reinstalling SP 4.
9.) I have verified that port number 3389 is located in the registry.
10.) Please DO NOT suggest checking the Remote tab in System
properties. This is a 2000 server and the tab does not exist. In this
same vein, unless someone can assure me differently, I do not believe
there is a local security policy that "Enables remote desktop
connection" in Server 2000. I've checked already. If there should be
one, I don't have it on my system.

This issue all started after I reinstalled the operating system as a
result of Active Directory Issues I was having with replication. The
reinstall did fix these problems, but since, my terminal services are
not running properly.

Thanks.

Mike

This post might be inappropriate. Click to display it.

This post was of great help. I just had a machine that was refusing to
listen on port 3389 for RDP connections. I checked the registry entries
you pointed to and found an error. I had the particular key you
reference, but the value, which was supposed to be
\REGISTRY\Machine\System\CurrentControlSet\Services\RDPDD\Device0
was instead
\REGISTRY\Machine\System\CurrentControlSet\Serviceŋ\RDPDD\Device0
Notice the ŋ symbol? I changed that to an s and rebooted.
Everything is working great now. I would never have found and fixed
this without your post.

Thank You!!

(for some reason the posts have a space character in 'Services' that I
am not putting there, but the information is still valid)

--
dvellis
------------------------------------------------------------------------
dvellis's Profile: http://forums.techarena.in/members/100407.htm
View this thread: http://forums.techarena.in/windows-server-help/541656.htm

http://forums.techarena.in

***@elitefoodco.com@ THANK YOU SO MUCH for your resolution

I did a P2V in VMWARE on a Windows 2000 server which went fine
Performed anther P2V and it booted into the OS fine but I couldn't RD
TO it and couldn't figure out why

After performing two additional P2V's and adding/removing the termina
services via add/remove programs I could not figure it out. Than
goodness scouring the net paid off after finding your post

Thanks for the hardwork and the effort to post the resolution onlin
for the rest of us

--
nickbs
-----------------------------------------------------------------------
nickbsd's Profile: http://forums.techarena.in/members/141354.ht
View this thread: http://forums.techarena.in/windows-server-help/541656.ht

http://forums.techarena.i

I did a P2V in VMWARE on a Windows 2000 server which went fine.
Performed anther P2V and it booted into the OS fine but I couldn't RDP
TO it and couldn't figure out why.
After performing two additional P2V's and adding/removing the terminal
services via add/remove programs I could not figure it out. Thank
goodness scouring the net paid off after finding your post.
Thanks for the hardwork and the effort to post the resolution online
for the rest of us.
--
nickbsd
------------------------------------------------------------------------
nickbsd's Profile: http://forums.techarena.in/members/141354.htm
http://forums.techarena.in/windows-server-help/541656.htm
http://forums.techarena.in

Nickbsd,

Techarena pulls and pushes posts to the Microsoft public newsgroups. That is
where all posts originate or are sent. However, they expire at the
newsgroups in 90 days, therefore we cannot see what you are replying to. I
am posting the previous suggested reasons why the problem you are
experiencing occured and the suggested solution for others to benefit.
Please keep in mind for future references to post the previous relevant post
to help others in the MIcrosoft public groups.

---
Re: Terminal Services not working - Port 3389 not listening

--------------------------------------------------------------------------------

Found the solution to my particular problem. Article:
http://support.microsoft.com/kb/270588/en-us

CAUSE
This problem can occur if the server has been booted by using the Last
Known Good Configuration option more than once. When the server has
been booted into the last known good configuration more than once, the
ControlSet001 registry key is deleted. However, the following registry
value is hard-coded to use the ControlSet001 registry key:
Key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Terminal
Server\VIDEO\rdpdd\

Value name: \Device\Video0
Value type: REG_SZ
Value data:
\REGISTRY\Machine\System\ControlSet001\Services\RD PDD\Device0
Back to the top

RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system.
Microsoft cannot guarantee that you can solve problems that result from
using Registry Editor incorrectly. Use Registry Editor at your own
risk.

To resolve this problem, obtain the latest service pack for Windows
2000. For additional information, click the following article number to
view the article in the Microsoft Knowledge Base:
260910 (http://support.microsoft.com/kb/260910/EN-US/) How to Obtain
the Latest Windows 2000 Service Pack
To resolve this problem: 1. Start Registry Editor (Regedt32.exe).
2. Locate and click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Terminal
Server\VIDEO\rdpdd\
Note If you do not have this key, use Registry Editor to create it.
3. Do one of the following:· If you did not have to create the key in
step 2, change the following value
Name: \Device\Video0
Type: REG_SZ
Value: \REGISTRY\Machine\System\ControlSet001\Services\RD PDD\Device0
to the following:
Name: \Device\Video0
Type: REG_SZ
Value:
\REGISTRY\Machine\System\CurrentControlSet\Service s\RDPDD\Device0
· If you had to create the registry key in step 2, add the following
value:
Subkey name: RDPDD
Name: \Device\Video0
Type: REG_SZ
Value:
\REGISTRY\Machine\System\CurrentControlSet\Service s\RDPDD\Device0

4. After you change (or create) the value, restart the computer that is
running Terminal Services.
---
--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS 2008, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA
Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

What listens on port 3389?

Why is my computer not connecting to RDP?

Is port 3389 open by default?

Does 3389 use TCP or UDP?