Re: Local logon for terminal server without specifying machine name?

I hope you are still here Dragos!

I made the changes as said below to the registry. At first they work. However, when someone uses the pull down list to go to another domain, the registry values are reset to whatever domain was used in the pull down list on the windows login screen. It appears from my research these values are changed whenever a different domain is selected from this pull down list. I can specify the domain in the userid as 'domain\userid' during the login process and this doesn't appear to change the registry values, just using the pull down list to select the domain does.

Any idea on how to stop the registry values from being changed?

I feel like I'm so close! Thanks!

Chris Smith

"Dragos CAMARA" <dragos_c@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F3231633-79CA-4563-9618-7B9DB43F1266@xxxxxxxxxxxxxxxx
hi,
it's all about default domain login, if you want to change the default
domain login :

HKLM
SOFTWARE
Microsoft
Windows NT
Current Version
Winlogon

Change the following keys to the name of the domain that you want as the
default on the login screen:

- AltDefaultDomain
- DefaultDomain


--
Dragos CAMARA
MCSA Windows 2003 server


"Wingnet" wrote:

Hello all,

I'll keep this short without explaining why I need this but simply say I
need to do the following.

I want to set up a local account on a terminal server machine and allow this
account to access the computer through terminal services.

I don't want to use the domain pull down list to select the machine. I
prefer to logon to the local account by typing 'Machine_Name\UserId' then
enter the password. The trick is, I also need to leave off the machine name
in the userid field.

I have two Server 2003 based TS systems. One of these machines is based on
an NT4 domain while the other machine is based on a Server 2003 active
directory.

I started on the TS machine in the NT4 domain first. I created some local
accounts. After messing around, I discovered I could logon through terminal
services by specifying for the username '\userid' and then the password. In
other words, leave off the machine name from the userid (I didn't have to
select the machine name from the domain pull down list either). Great
start. I created some local logons and all worked fine on the domain based
machine.

I then went to the active directory based TS server and created some local
accounts. Thinking the same thing I did on the domain based TS machine
would work, I tried to login. The login failed with a message saying the
userid or password was wrong. In other words, specifying '\userid' for the
userid didn't work. I tried to login with 'machinename\userid' as the
userid. This time it worked and I was able to log into Terminal Services
onto the AD based Terminal Services machine using the local account. This
verified the userid/password was correct and the local account can log into
terminal services.

Questions: why can I log onto the domain based TS server without specifying
the machine name but I can't on the AD based TS machine? How do I log onto
all TS server machines without specifying the machine name on local
accounts?

Thanks!



.

Relevant Pages

  • Re: Local logon for terminal server without specifying machine name?
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... I made the changes as said below to the registry. ... was used in the pull down list on the windows login screen. ... I want to set up a local account on a terminal server machine ...
    (microsoft.public.windows.terminal_services)
  • RE: Local logon for terminal server without specifying machine name?
    ... it's all about default domain login, if you want to change the default ... I want to set up a local account on a terminal server machine and allow this ... in the userid field. ...
    (microsoft.public.windows.terminal_services)
  • Re: Server login via LAN...
    ... When you say AD server do you mean a Domain Controller? ... If you want to login to a workstation locally then it would be the same as ... account and specifiy and login time to use the local account credentials ... select the local workstation in the log onto drop down box. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replicate Wins problem
    ... in the "other" as the second WINS server etc. ... Shows in DC1-WINS, they seem to replicate, yet doesn't show ... server has a Push and a Pull partnership with the OTHER. ...
    (microsoft.public.win2000.networking)
  • Re: Localizing SQL Server Data
    ... The best way to limit the data transferred through the wire is to built ... if you do the join on the Server, that means that the same repeated data ... make a local query implying the local tables. ... to pull the changed records for those tables. ...
    (microsoft.public.access.modulesdaovba)