Windows Server 2003/Terminal Server [Archive]

View Full Version : Windows Server 2003/Terminal Server

Doctor Manhattan

01-30-2006, 07:00 AM

Hi, I have a buddy who's running a small buisness. He has a LAN set up with a Firewall/NAT broadband router with a server that is running Windows Server 2003 (He has the lisence to run Terminal Server) and he has it setup for file sharing with about half a dozen people inside the network.How can I help him set it up so that a few users can remotely connect from outside the firewall and work with the files on the server, they need to make changes to those files and be able to save them to their local PC, or save files that are already on their local PCs to the server? Is there a good place to look up this kind of thing?Thanks!

<a href="http://www.xmradio.com/programming/channel_page.jsp?ch=202" target="_blank"><img src="http://scripts.cgispy.com/image.cgi?u=skw" border=0></a>

Death Metal Moe

01-30-2006, 07:37 AM

<img height="200" src="http://www.goodlogo.com/logos/apple_red.gif" width="158" border="0" />

<img src="http://scripts.cgispy.com/image.cgi?u=njdmmoe">

<A HREF="http://www.unhallowed.com">www.unhallowed.com</A>
<A HREF="http://thebigsexxxy.blogspot.com/">One Big SeXXXy Blog</A>
<A HREF="http://www.myspace.com/deathmetalmoe">Death Metal MySpace</A>

DTN

Death Metal Moe

01-30-2006, 07:37 AM

<img height="237" src="http://upload.wikimedia.org/wikipedia/uk/3/33/Linux-logo.jpg" width="200" border="0" />

<img src="http://scripts.cgispy.com/image.cgi?u=njdmmoe">

<A HREF="http://www.unhallowed.com">www.unhallowed.com</A>
<A HREF="http://thebigsexxxy.blogspot.com/">One Big SeXXXy Blog</A>
<A HREF="http://www.myspace.com/deathmetalmoe">Death Metal MySpace</A>

DTN

Death Metal Moe

01-30-2006, 07:37 AM

Just kidding, I have no idea.              Obviously.

<img src="http://scripts.cgispy.com/image.cgi?u=njdmmoe">

<A HREF="http://www.unhallowed.com">www.unhallowed.com</A>
<A HREF="http://thebigsexxxy.blogspot.com/">One Big SeXXXy Blog</A>
<A HREF="http://www.myspace.com/deathmetalmoe">Death Metal MySpace</A>

DTN

FUNKMAN

01-30-2006, 07:40 AM

i believe you are interested in PCAnywhere or GoToMyPc. Do a search on them and check e'm out...

<img src="http://scripts.cgispy.com/image.cgi?u=Ippolito">

Doctor Manhattan

01-30-2006, 07:53 AM

Thanks, but I thought Terminal Server would be able to do this as well.

<a href="http://www.xmradio.com/programming/channel_page.jsp?ch=202" target="_blank"><img src="http://scripts.cgispy.com/image.cgi?u=skw" border=0></a>

KC2OSO

01-30-2006, 07:58 AM

Can they log onto the box using the Terminal Services Client? 

<img src="http://scripts.cgispy.com/image.cgi?u=chestermoonrock">

Doctor Manhattan

01-30-2006, 08:00 AM

"Terminal Services Client"? I bet that would help. So they need this setup on the remote PC? Is it as simple as setting up the firewall to allow access to the server via certain ports?Thanks

<a href="http://www.xmradio.com/programming/channel_page.jsp?ch=202" target="_blank"><img src="http://scripts.cgispy.com/image.cgi?u=skw" border=0></a>

KC2OSO

01-30-2006, 08:11 AM

Yes.  As long as the firewall allows access to the server, the
Client user gets access to the box at what ever level the server admin
sets for that user.  Moving large files back and forth can get a
bit tricky from the server to the client since the Terminal Services
Client is another separete instance (much like PCAnywhere etc.) 
For that they could use a shared network drive maybe. 

<img src="http://scripts.cgispy.com/image.cgi?u=chestermoonrock">

Doctor Manhattan

01-30-2006, 08:24 AM

so is "Windows Server 2003 Administration Tools Pack" the thing I need? I googled "Terminal Services Client" and was directed to <a href="http://www.microsoft.com/downloads/thankyou.aspx?familyId=C16AE515-C8F4-47EF-A1E4-A8DCBACFF8E3&displayLang=en&oRef=http%3a%2f%2fdownload.microsoft.com%2fdownloa d%2f8%2f0%2f8%2f808551ab-f897-41c4-a6c1-2a4efea95f6a%2fReadme.htm" target="_blank">this page</a> because "The Terminal Services Advanced Client 5.01 Pack: RDP client with high encryption (128-bit) are no longer available." <a href="http://www.xmradio.com/programming/channel_page.jsp?ch=202" target="_blank"><img src="http://scripts.cgispy.com/image.cgi?u=skw" border="0" /></a>

This message was edited by SKW on 1-30-06 @ 12:25 PM

KC2OSO

01-30-2006, 08:36 AM

Yes. <a target="_self" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=0A06E845-57EF-43EB-802F-F274FD937400&displaylang=en">This</a>
appears to be the same thing and how to do it for Server 2003.
We're using Win2K servers for Terminal Services Client was still
used. I'm guessing a shared network drive won't do the
trick? You may still face the problem of how to move large files
back and forth though in the 2003 version.Also -I don't think on 2003 Terminal Services installs by default.  I think it's part of add-ins. 

<img border="0" src="http://scripts.cgispy.com/image.cgi?u=chestermoonrock" /> 

This message was edited by KC2OSO on 1-30-06 @ 12:55 PM

bwanna

01-30-2006, 09:00 AM

The client you need is part of windows.  Go to start, programs, accessories, comminications and choose remote desktop connection.  Then you put the IP address of the server in there and if everything is setup right, they should get hit with a username and password and then get a desktop from the terminal server.  Getting outside user access to the terminal server is more complicated. You have to poke some holes in the firewall or setup VPN tunnels and stuff like that.  Send me an e-mail if you want some help with.  <a href="mailto:bjh@absolution.com">bjh@absolution.com</a>.  I do this shit all the time.

Doctor Manhattan

01-30-2006, 09:25 AM

quote: The client you need is part of windows.  Go to start, programs, accessories, comminications and choose remote desktop connection.  Then you put the IP address of the server in there and if everything is setup right, they should get hit with a username and password and then get a desktop from the terminal server.  Getting outside user access to the terminal server is more complicated. You have to poke some holes in the firewall or setup VPN tunnels and stuff like that.  Send me an e-mail if you want some help with.  <a href="mailto:bjh@absolution.com">bjh@absolution.com</a>.  I do this shit all the time. I did some more research. It seems that client I found is for administrating the Server, I don't need that for this project. The Remote Desktop Connection (+ Clicking Options, Clicking the Local Resources tab and selecting the Disk Drives check box) is all I need. I'll be able to figure out the firewall, that is the easy part for me, I just have never used Terminal Server before now. We already got the list of users setup with permissions to just the folders they will have access to. Locally when they log on they can't access folders other than those specified for them, some with read-only access. Hopefully when they log in remotely the permissions will be the same. quote: Also -I don't think on 2003 Terminal Services installs by default.  I think it's part of add-ins.  We figured out how to active Terminal Server and even got the licensing (Terminal Server CALs) to work out and it seems to be running and active now.Thanks for your input guys!Mahabone! <a href="http://www.xmradio.com/programming/channel_page.jsp?ch=202" target="_blank"><img src="http://scripts.cgispy.com/image.cgi?u=skw" border="0" /></a>

This message was edited by SKW on 1-30-06 @ 1:29 PM

PaulF

01-31-2006, 07:08 PM

I have set up about half a dozen servers for this purpose. If you are still having issues, here's the checklist:1. Make users who need remote access members of the remote users group2. Forward port 3389 on the firewall to the server (this is the default listening port for Remote Desktop - also goes for Windows XP Pro's remote desktop). You can change the listening port via the Terminal Services Configuration or via the registry, but if you use another port, the remote user will have to specify it when they connect. ie. remote.somedomain.com:3390BTW - For those that don't own their own domain, I use DynDns to configure a dynamic domain so that remote users don't have to remember an IP address, or for those addresses that may periodically change.3. If you haven't already selected, go with User CALs instead of Device CALS. Technically you need a CAL (Client Access License) for each user, but Server 2003 cannot actually keep track of this, while device licenses get locked to a specific computer, not a user, and can be tracked. Windows 2000 clients get a license automatically.4. On the client computers, if you want the user to to be able to copy files from their local PC to the server and vice-versa, go to the Options of the Remote Desktop Client (Start > Programs > Accessories > Communications > Remote Desktop Connection) and then go to Local Resources. Make sure that "Disk Drives" is checked. For speed purposes, change Sound option to "Do Not Play". If you check "Printers", as long as the proper driver is available on the server, the remote user will be able to direct print jobs back to their personal printer. Works best with parallel lasers, like HP.