How to set up a terminal server?

Microsoft Microsoft windows nt server 4....
December 6, 2009 at 15:04:00
Specs: Windows NT 4.0 Terminal Server Edition, Unknown
As you can see, I am having problems getting a server setup for remote connections. I intended this to be where I can have my peers connect to my terminal server... but I don't know how I can do this. I only know how to get a computer to connect within a network, but I need people who are not in my network to connect. How can I do this step-by-step? Or can someone redirect me to a tutorial?

Thank you in advanced! :)

P.S. I am running Service Pack 6 with Internet Explorer 4.0... soon to be Internet Explorer 6.


See More: How to set up a terminal server?

Report •

#1
December 6, 2009 at 15:34:09
Am I getting it right, you want to provide Terminal Services accessed via Internet?

If so, are you using a static public ip address for your server?

Is Terminal Server running and configured, so that it can be accessed from the local network without problems?


Report •

#2
December 6, 2009 at 15:58:47
I can access it with my home network... ie. \\servername, but I need to provide access via. the internet so other people can access it. Also, thanks for the quick response!

Report •

#3
December 6, 2009 at 16:08:39
So what's about your public ip address?
Static or dynamic ip address?
That's necessary, because if you have a dynamic ip address, you must use an internet service like no-ip.com or DynDNS.com, where you can create a free account that is needed to update a free domain name like YourTerminalServer.dyndns.org with the current assigned ip address.
A user can then use \\YourTerminalServer.dyndns.org to find your server on the internet via terminal client.

Report •

Related Solutions

#4
December 6, 2009 at 16:15:50
Mine is a static IP. So with a static, I can still go onto DynDNS.com and make an account, so someone can just type //MyTerminalMachinesName.DynDNS.com and it would work?

Report •

#5
December 6, 2009 at 16:24:45
Yes.
It doesn't matter whether it's static or dynamic.
On a static ip address, one can directly use the ip address, on a dynamic address, no one knows you ip address, if it has been changed.

But anyway. It's alway easier to use a name and therefore you can use DynDNS.

As far as I know you need to update the DynDNS ip address at least every 28 days.
But you will get this infos on their homepage.

The easiest way to update the ip address at DynDNS is, if you have a router, that already support it.


Report •

#6
December 6, 2009 at 16:28:00
Ok, I tried to get someone to logon to the machine with the address from DynDNS. It didn't work. I think it's beause the server doesnt respond to it? How can I get the server to allow it to work with this address?

EDIT:
I recieved this error while trying to connect. The server is in the network of the DynDNS link that I created, but I get this error...
"Remote Desktop can't find the computer "(Blanked Out)". This might mean that "(Blanked Out)" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to."


Report •

#7
December 6, 2009 at 16:41:30
Tell me something about your environment.
How is the server connected to the internet?
Are you using a router with firewall?
Is there a firewall running on the server itself?

Report •

#8
December 6, 2009 at 16:43:58
There are no firewalls at all on the network, or on the server. Currently, I am running this in a virtual machine for now, since I am having difficulties with it installing on my tower. It's connected to the internet, and so on. I don't completely see why it's doing this.

Report •

#9
December 6, 2009 at 16:50:04
Ok, no firewall.
So your Terminal Server won't work for a long time without any firewall !!!
If you're lucky, it will run a few days, but I don't think so.

Anyway, go to this website and scan your pc for open ports. When finished, you'll get a list of found open ports. There should be listed port 3389 (Terminal Service).

Which VM are you using?


Report •

#10
December 6, 2009 at 16:52:26
Sorry forgot to mention the website:
www.auditmypc.com

Report •

#11
December 6, 2009 at 16:53:17
Microsoft Virtual Machine 6.0.156.0, and what website?

Report •

#12
December 6, 2009 at 16:53:45
Ahh ok thanks for the link!

Report •

#13
December 6, 2009 at 16:54:19
See response 10

:-)


Report •

#14
December 6, 2009 at 16:57:08
Port Scan Status
We completed the audit and did not find any open ports.
This is ideal for the average visitor.

Is this good... or bad?


Report •

#15
December 6, 2009 at 17:02:04
From the security aspect, thats fantastic, but you want to provide a service to the internet, service is running and as you told me, no firewall is running.

So there is something wrong.
When you use Microsoft Virtual Machine, your host system is also Microsoft Windows, correct?

I have never seen a Windows system, running completely without a firewall, where the port scan tell me, there are no open ports found.

Is there running a firewall on the host system?


Report •

#16
December 6, 2009 at 17:08:50
Yes, McAffe.

I redid the test and only 8080 was open, for http protocal. But, I don't get it. Is this a firewall issue, or a configuration issue within the OS?


Report •

#17
December 6, 2009 at 17:14:28
First, why is port 8080 open???
Port 8080 is normally used for proxy server !

How is the network adapter configured for the virtual machine, not in Windows NT, in the Microsoft Virtual PC configuration.


Report •

#18
December 6, 2009 at 17:25:42
There is no configuration. Just my internet adapter, and thats all thats there. Not clickcable.

Report •

#19
December 6, 2009 at 17:44:30
Can you access the internet from your Virtual Machine?

Report •

#20
December 6, 2009 at 17:48:58
Yes. And I found one thing that i cant seem to resolve. I get the following error while attempting to start the remote access service...

Error 2185; The service name is invalid.

How can I get that resolved?


Report •

#21
December 6, 2009 at 17:56:18
This error occurs, when "Remote Access Service" is not installed.

1. In the Control Panel window, choose the Network icon.
2. In the Network Settings dialog box, choose the Add Software button
3. In the Add Network Software dialog box, select Remote Access Service, and then choose the Continue button.
4. Specify the location of the source files
5. After the Remote Access Service is installed, restart Windows NT


Report •

#22
September 20, 2011 at 11:25:32
Here is another resource with interesting tips on configuring terminal services:

http://www.ericom.com/Configuring-T...

There is also information on load balancing.


Report •

Ask Question