Link to home
Create AccountLog in
Windows Server 2003

Windows Server 2003

--

Questions

--

Followers

Top Experts

Avatar of robertbranch
robertbranch🇺🇸

W2K3 Terminal Server Not Accepting Connections
I have a Windows 2003 Terminal Server in Application mode.

It has been working correctly for about 3 years with no issues. Suddenly, this morning it is no longer accepting connections.

Things I have tried:

netstat -an: server is NOT listening on 3389
Terminal Services service: running
No firewall running on server (on same subnet)
Remote Desktop Users Group has all of the correct users in it.
No errors in event log that have to do with Terminal Services
I've check the registry entries and they all look correct.
Disabled virus protection - same result
Reset TCPIP stack - no help


One thing that has something to do with the issue, but I can't figure out exactly what:  
When I open the Terminal Services Configuration managment console and look at the properties of the connection ... if I click on the Network Adapter tab, the mmc hangs and has to be forcibly killed.   I deleted and recreated the connection, but the same thing happens.


This has the entire office down, so any help is GREATLY appreciated!!

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

Avatar of robertbranchrobertbranch🇺🇸

ASKER

Just another piece of info:

No changes have been made to the server in the pasr 21 days.

Avatar of PenguinNPenguinN

Is your server service running and netlogon?
Avatar of robertbranchrobertbranch🇺🇸

ASKER

Yes Server and Netlogon services are running.  I have restarted them to no vail and rebooted the server a couple of times with no change.
Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

Avatar of devinnoeldevinnoel🇺🇸

What errors/warnings are showing up in the Application & System log for the server?
Avatar of PenguinNPenguinN

How is your disk health, the hanging of your mmc sounds like a problem with your tcp/ip cable/files/other dependancy's. If you unplug the cable can you then open tcp/ip settings?
Avatar of maxxmyermaxxmyer🇺🇸

@PenquinN good track, NIC card too.
Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

Avatar of robertbranchrobertbranch🇺🇸

ASKER

I can open the NIC card setting, etc without issue.  It is only when I try to look at the Network Adapter tab in the Terminal Services Configuration that is hangs.

I'll check the issue with the cable unplugged and let you know.
Avatar of devinnoeldevinnoel🇺🇸

Does anything show up in the event logs?
Avatar of robertbranchrobertbranch🇺🇸

ASKER

There are no errors showing up in the event logs about the terminal services.
Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

Avatar of PenguinNPenguinN

Is your server patched to the last updates?
Avatar of robertbranchrobertbranch🇺🇸

ASKER

the Server has on Service Pack 1 becuase the vendor whose software runs on the server had not "certified" SP2.  I spoke with them and they agreed I could update to SP2, but when I attempt the install it starts and hangs at Inventorying Your Hardware and never proceeds.  It allows you to cacel the install, but the process never terminates.

Also, I sttempted to restart the NETLOGON and SERVER services. NETLOGON worked fine, but SERVER failed to restart.

I unplugged the NIC and attempted to look the Network Adapter tab in Terminal Services Configuration, but it still hangs.

Still no TS errors in the event logs.

I ran devcon.exe -r install %windir%\inf\machine.inf root\rdpdr ... it ran then rebooted the server and still no joy ....
Avatar of robertbranchrobertbranch🇺🇸

ASKER

Ok, the problem is solved.  I ended up bring Microsoft in to help resolve it.

The problem was a faulty print driver that had been installed that hung the print spool and ended up blocking all requests to port 3389.

We pruned the print hive, reset all of the print monitors to default and that resolved the issue.
Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

ASKER CERTIFIED SOLUTION
Avatar of robertbranchrobertbranch🇺🇸

ASKER

Link to home
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Create Account
Avatar of robertbranchrobertbranch🇺🇸

ASKER

I had to contact Microsoft Support in order to get this issue resolved, so I posted the solution for everyone to use.
Avatar of Mad_LennyMad_Lenny

Very many thanks for posting the solution Robert!! I stumbled across this eventually, just in time to save my bacon and make me look good :)
Windows Server 2003

Windows Server 2003

--

Questions

--

Followers

Top Experts

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).