Zone Alarm kills Terminal Services access

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

At home, I have a Windows 2000 server on a PC which acts as a
router/firewall for the rest of my LAN. I have a cable modem, connected to
NIC card #1 in the Windows 2000 server, with DHCP, and the server is
connected to a Netgear router via NIC card #2. From the router the LAN
branches out to the individual PCs.

In any case, recently I had this great idea of installing Zone Alarm 4.5 on
this Windows 2000 server. Bad idea... Things were working fine prior to
Zone Alarm, but after I installed Zone Alarm, I realized that it wasn't
meant for a server...too many ZA warning messages began to drive me crazy.
So after a few days, I performed an uninstall of Zone Alarm.

The uninstall went uneventful, and I had assumed everything was fine, but
I've discovered one problem that I have been unable to resolve:

Prior to Zone Alarm, I would often access the server via my other LAN
connected PCs using "Remote Terminal Services" (aka Terminal Services
Client - "C:\Program Files\Terminal Services Client\Mstsc.exe" ). I could
log in to this one server without having to take a hike down 2 flights of
stairs to the basement, where the server is located. But during and after
Zone Alarm, this was no longer possible...logging in remotely, that is.
Now, whenever I try to access the server via MSTSC.EXE, I am told "The
client could not connect to the Terminal server. The server may be too busy
(which it is not). Please try connecting later."

The server isn't "busy", and it has been rebooted several times. By the
way, the server CAN indeed stil be reached via the LAN PC's "Network
Neighborhood" icons, so I know that the cables, router, NIC cards are all
working just fine.

The Terminal Services service is indeed shown as Automatic and running on
the Manage > Services list.

I have also done the following...

START > SETTINGS > CONTROL PANEL > ADD/REMOVE PROGRAMS > ADD/REMOVE WINDOWS
COMPONENTS

....and removed (unticked) the "Terminal Services" items, then rebooted the
PC.

Then I repeated the above steps, but added (checked) the "Terminal Services"
items, and rebooted the PC.

The result? Nothing changed. I still can't connect to this server via the
terminal services client.

BTW, from the server, I can use the terminal services client to connect to
another PC on the LAN or a server on the Internet. For the fun of it, I
tried to connect to this selfsame server from the server. In other words, I
tried to connect the server to the server. The result? Same error: "The
client could not connect to the Terminal server."

I do NOT have Terminal Server Licensing installed.

What might have Zone Alarm "mucked up" to cause this problem?

Thanks.