Newbie here

  • Thread starter Thread starter Sam
  • Start date Start date
S

Sam

I have recently started implementing TS Web, and the
regular RD connection on Win2k Server, note I have the
novell client 4.9 running on the server to give
connections to the novell servers. Currently users have no
access to the desktop, I just put the application in the
environment tab in active directory users and computers
section. I installed with NT 4.0 legacy permissions.


A few questions:

1)I want the TS WEB to only run over port 80 (security is
not an issue as we have a portal with SSL &
Authentication) - I can not open any other ports than 80
2)How do I get the local drive and the local printer to
map. I can't seem to get this to work.
3)Re: Security, I saw a post which explained how to
implement security, but I am not sure how to apply
security to the registry. I am a dummy here
4)When I log into RD as a standard user - without admin
privileges, I get an error: user cannot log in
interactively. How do I solve this, without giving a user
admin rights?
5)I need to start controlling the security much better, is
my best option to change the operation mode to windows
2000, what impact will this have on my program (we are
running office and Saleslogix client which is a CRM) ?
6)Is there a better way to start the applications and map
the drives than specifying a batch file under the
environment tab (users & computers) to start
automatically. First the script executes a few net use
commands then it call the program (saleslogix.exe)
Help would be greatly appreciated,
Sam
 
That is what I assumed unfortunately. This gives citrix
and advantage I guess. any ideas on the other questions
anyone?

Many thanks for the quick response.
-----Original Message-----
You can't have both the WWW service and Terminal Server
Click to expand...
both listening on Port 80. Terminal Services listens on
port 3389 by default, so if you want to use TSWeb you need
to open Port 3389 to the TS and Port 80 to the IIS Server
(if it's NOT running on the TS). It's possible to have TS
listen on a port other than 3389, but not on a standard
port that's already listening for another service.
 
1. What do you run that requires the legacy permissions
for the registry?
I actually don't think I need the legacy permissions. :)
I rebuilt the server in the other mode, and so far so good.
3. In regards to TS WEB: I am having a problem getting the
local drives to map in either system. How does this work?
4. Do you need to map network drives to local hard
Click to expand...
drives or just have them available for copy/paste?

***Either may be find, can you explain how I would
implement either system? I can't seem to understand how
this works or how to set it up.

Many thanks,
-----Original Message-----
Citrix has a lot of add-on features for TS, but it costs
Click to expand...
a bundle too. AFAIK you still need to open another port
to use Citrix NFuse, i.e. Port 1494 .
1. What do you run that requires the legacy permissions for the registry?
2. RDP Traffic on port 3389 is every bit as secure as SSL.
3. To enable the use of local drives & printers via
Click to expand...
TSWeb you need to change the default.htm, in this section:
'Device redirection options
MsRdpClient.AdvancedSettings2.RedirectDrives = FALSE
MsRdpClient.AdvancedSettings2.RedirectPrinters = TRUE
MsRdpClient.AdvancedSettings2.RedirectPorts = FALSE
MsRdpClient.AdvancedSettings2.RedirectSmartCards = FALSE

4. Do you need to map network drives to local hard
Click to expand...
drives or just have them available for copy/paste?
5. Users of TS on 2003 need to be member of the
Click to expand...
local "Remote Desktop Users Group", as detailed in the
Terminal Server Help in 2003. If this is a Domain
Controller (NOT recommended) then you need to modify the
Default Domain Controllers Security Policy to allow these
users the "Logon Locally Right", which also allows them to
logon to any of your DC's consoles (FYI).
Patrick Rouse
Microsoft MVP - Terminal Server
www.workthin.com



----- (e-mail address removed) wrote: ---- -

That is what I assumed unfortunately. This gives citrix
and advantage I guess. any ideas on the other questions
anyone?

Many thanks for the quick response. Server
both listening on Port 80. Terminal Services listens on
port 3389 by default, so if you want to use TSWeb you need
to open Port 3389 to the TS and Port 80 to the IIS Server
(if it's NOT running on the TS). It's possible to have TS
listen on a port other than 3389, but not on a standard
port that's already listening for another service. have users
have no application in
the
Click to expand...
&> Authentication) - I can not open any other ports
 
Back
Top