problems connecting to terminal server from outside the network

[Marco Soria]

Hi I have a windows 2000 server with sp4, i have a application that is
used by all the employees of our company. Half of our employees are
here in the offices and the other half are in several locations.
Everything was working fine until yesterday. Right now i can only
connect to the terminal server from our network using the local ip. The
employees from outside the network use a public static ip, but since
yesterday, they are not able to connect. I checked the terminal server
service and its up and running. I can ping the public ip from outside
the network, i even tried to redirect the remote desktop connection
requests to another server and it worked fine, so im sure there is
something wrong with the sever 2000. I noticed that there is a service
set in automatic that didnt start and i havent been able to start it.
Its the license for terminal server service, i dont know if this has
anything to do with my problem

Any help would be very apreciated

thanks

 

[Vera Noest [MVP]]

What error message do you get when you try to connect?
Which Events do you see in the EventLog on the Terminal Server?
Do you have a TS Licensing Server installed and activated?
Is this Terminal Server a member server in an AD domain, a standalone
server in a workgroup, or.....?
Which Operating system are your clients running?

 

[Marco Soria]

I get error 29 in the event viewer, the termianl server is a member
server in the ad domain, and the terminal server licensing service is
running in the domain controller, its also installed in the terminal
server member server but im unable to run the service from there, but i
was reading that the licensing server must run in the dc right???

Thanks for your reply

 

[Vera Noest [MVP]]

Yes, as Event 29 from TermServDevices says, the TS Licensing Server
on a W2K server must run on a Domain Controller. So you might as well
uninstall it from the member server.
But this has nothing to do with your connectivity problem.

I still have this question:
What error message do you get when you try to connect?

And I assume you have a firewall? Is traffic to port 3389 redirected
to the Terminal Server?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

 

[Marco Soria]

Yes, the TS Licensing Server is running on the DC, its alredy
uninstalled from the member server. Also i redirected traffic from port
3389 to port 3392 to the Terminal server. Internal users can connect,
the problem is with the external users. It was working fine and
suddenly it stopped working. The first time this happened i reinstalled
the terminal server service. Also i checked the event viewer and there
are no errors that relate to this issue. When i try to connect from
outside i get this error:

remote connections might not be enabled or the computer might be too
busy to accept new connections. It is also possible that network
problems are preventing your connection.

Remote connection is enabled to there must be a networ error but
where???


Thanks for your help

 

[Vera Noest [MVP]]

OK, so the Terminal Server is configured to listen on port 3392,
correct? Can you telnet to port 3389 of the firewall?

187628 - Using Telnet to Test Port 3389 Functionality
http://support.microsoft.com/?kbid=187628

Since this suddenly stopped working, there has either been a
configuration change somewhere, or a time limit has passed. Which
means licensing.
You don't happen to see licensing problems with these clients, are
you (event 1004: can't issue license)? A black hole router could
explain what you see (preventing transfer of the permanent license
to the clients).

314825 - How to Troubleshoot Black Hole Router Issues
http://support.microsoft.com/?kbid=314825