Terminal Services, Static IP, Router Setup

[jmcd0719]

I am a relative newbie to Win2k Server, so I apologize profusely in advance.

We have 4 PC's (All-XP Home) and a Win2k Server.

Internet --> Sprint ADSL Router -->KTI Switch --> PC'S

Currently, we have a static IP address from Sprint and configured the router so that all the PC's on the network can access the internet. This works correctly.

What I want to do:

How do I set up Win2k on the client PC's, so that the PC's can login into the server. I have heard we may need XP Pro since Home doesn't support domains. I am willing to upgrade if this is the easiest solution.

I want to set up Terminal Services, so outside clients can dial in and use our application. How do I set up the static IP on the Server. I tried using the Static IP settings from Sprint for the TCP/IP setting but I could not connect or ping from the server. Do I reset the router settings and use the setting on the server?

Do I need to add another NIC card to the server?


Thanks in advance

Set up on the PC's an intern

 

[markdmac]

your first hurdle will be the client computers. I'd upgrade them to XP Pro rather than downgrade to Win2K Pro.

Next you need to take your Win2K Server and run DCPROMO to install Active Directory and make this server a Domain Controller. You can follow the wizard promots well enough to make your way through it, but I would strongly suggest that you read up on this first. VERY IMPORTANT that you check to make sure there isn't already a domain onsite, if there is then you will want to be joining the server to the domain rather than creating a new domain.

Once you have a domain in place you can modify the client machines so that they join the domain. You do this by right clicking My Computer and choosing properties. Click the Computer name tab and then click the Change button to change to your domain.

If you have a firewall you will need to open up the ports for Terminal Services wich is port 3389.

 

[Andyleates]

I imagine you are also going to have to set up some form of NAT on your filewall to connect directly to a server inside your network.

Andy Leates MCSE CCNA MCP+I