TS Logon

  • Thread starter Thread starter Alan Rawdin
  • Start date Start date
A

Alan Rawdin

I currently have w2k small business installed. I have two
security groups. One For Technicians and one for
Management. I have set four usernames in the Technicians
group and two in Management. I have four client Machines
running XP pro. Machine name are listed in active
Directory OK. I have installed Terminal server in
application mode. The Clients also have TS client
software installed. I have configured the server to share
the documents and settings path as UNC \\server01\users.
I also have a UNC \\server01\Documents. IN the user
settings in profile i entered the following \\server01
\users\%Username% and home directory connect Z: to
\\server01\Documents\%Username%. In terminal services I
have used the same settings. With C: instead of Z: for
the home directory. I have locked down the technicians so
that all the is shown is the shortcut to awork32.exe and
the startup to to mstcc.The problems I have are the
following. The mechanics cannot log on the domain from xp
pro logon screen. The message i get is unable to locate
roaming profile trying with local profile. Then Unable to
locate local profile logging off. I have tried
permissions right the way up to giving the mehanics group
administrator access to both UNC's. Still doesn't work.
Except one user, Who has all the same secuirty settings.
I have even tried copying that users contents of the
profile to the other users but to no avail. When the user
that can log in loads TS client to says connecting to
192.168.0.1 and then says unable to log on to TS. I have
checked his permission to log onto TS and it is ticked.
When I tried logging the users on at the server
everything works as it should.

Problem no. two is that when the users including the
administrator account tries to log on to the client
machines it takes up to five minutes to log on.

Incidently I have logged onto the clients as
administrator and then Run TS client and logged the
technicains on succesfully where all the proper security
settings are applied.

Thirdly a bit of information is is possbile to make the
clients go straight into TS without logging on locally???



HELP MY BOSS IS SHOUTING

(e-mail address removed)
 
answers are inline...
-----Original Message-----
I currently have w2k small business installed. I have two
security groups. One For Technicians and one for
Management. I have set four usernames in the Technicians
group and two in Management. I have four client Machines
running XP pro. Machine name are listed in active
Directory OK. I have installed Terminal server in
application mode. The Clients also have TS client
software installed. I have configured the server to share
the documents and settings path as UNC \\server01\users.
I also have a UNC \\server01\Documents. IN the user
settings in profile i entered the following \\server01
\users\%Username% and home directory connect Z: to
\\server01\Documents\%Username%. In terminal services I
have used the same settings. With C: instead of Z: for
the home directory. I have locked down the technicians so
that all the is shown is the shortcut to awork32.exe and
the startup to to mstcc.The problems I have are the
following. The mechanics cannot log on the domain from xp
pro logon screen. The message i get is unable to locate
roaming profile trying with local profile. Then Unable to
locate local profile logging off. I have tried
permissions right the way up to giving the mehanics group
administrator access to both UNC's. Still doesn't work.
Except one user, Who has all the same secuirty settings.
I have even tried copying that users contents of the
profile to the other users but to no avail. When the user
that can log in loads TS client to says connecting to
192.168.0.1 and then says unable to log on to TS. I have
checked his permission to log onto TS and it is ticked.
When I tried logging the users on at the server
everything works as it should.
Click to expand...

When the users can't logon to their local clients, check
the eventlog on the server/domain controller and on the
clients to see a more detailed message about what is going
on there. When the users can't logon to terminal
services, what error message do they get? From the
client, can they ping the terminal server and/or telnet ro
port 3389 on the terminal server?
Problem no. two is that when the users including the
administrator account tries to log on to the client
machines it takes up to five minutes to log on.

Incidently I have logged onto the clients as
administrator and then Run TS client and logged the
technicains on succesfully where all the proper security
settings are applied.
Click to expand...

You might want to check your event logs to see what is
going on and to make sure DNS is setup correctly. I've
seen DNS problems cause all sorts of long logons and
whatnot.
Thirdly a bit of information is is possbile to make the
clients go straight into TS without logging on locally???
Click to expand...

I would use group policies to set the shell on the XP
machines to be the mstsc.exe application. That way when
they start up the machine, it goes directly to the TS
client and nothing else occurs.
 
Back
Top