Re: local devices in a terminal session problem
- From: "Looksmart5000" <looksmart@xxxxxxxxxxxxxxxx>
- Date: Wed, 7 Mar 2007 22:16:05 -0000
Hi,
When the user asks me to solve the problem, I access remotely to their PC
(workstation connected to ADSL router in a station and provided with
terminal connection) and he opens the terminal connection and puts the
authentication info to login on it. The problem occourred in my computer
application. I shutdown his session and open the terminal in that computer
with my credentials and the problem not occours. It shows the units in the
"other" section normally and I can access it. I ask to the user to give me
the password and I tried in my pc that has fulll access to network without
terminal access being needed. Then I open a terminal session with their
account and the problem remains. So I concluded that the problem is an user
account problem in the terminal server. My company only has one Terminal
server. The number of users using it is not very much since many could
access in one of 6 enterprise headquarters. The main problem is that since
the user accesses the account, I couldn't goes into "Documents and settings
folder\user" and delete the whole directory forcing create a new profile
when entered next time, because the windows give an accessing error of
NTUSER could not be deleted. My supervisor doesn't want that the terminal
was restarted because of users that use it all the time. One time I restart
the terminal and deleted the account and it works, so it's a file in the
accound that maybe corrupted or with incorrect information. If I know what
is that file/folder I can delete and then recreate the drives access without
restart the PC. I have tried editing the connection preferences, uncheck the
local drives option and start a session without it. The drives doesn't
appear as expected. Then I reactivate the option and the problem returns.
The suggestion 1 is out because we only have one terminal server.
The suggestion 2 is out because it only occours with 2 or 3 users, not with
all users, so it's not a service problem, I think.
Tomorrow I will try install the ner application. In my Home PC I have it
already.
The suggestion 4 I have searched the event log before.
Thanks for your help
With best regards,
Looksmart
"Mike Luo [MSFT]" <v-miluo@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:pnHZUzJYHHA.1576@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
Thank you for using newsgroup!
From your post, we didn't determine what the problem is. I have the
following suggestions to narrow dow this problem:
Suggestion 1
===========
Use the problematic user to logon other Terminal Server, logon from the
normal computer where the user logon normally, to see if the prolbem
occurs.
Suggestion 2
===========
Go to the problematic computer, perform a clean boot, check if the problem
go away. please refer to the following steps:
A. Click Start, click Run, type "msconfig" (without the quotation marks)
and click OK.
B. Select "Selective Startup" and remove the check box for "Load Startup
Items".
C. On the "Services" tab, click Enable All.
D. Check "Hide all Microsoft Services", click Disable All and clear "Hide
all Microsoft Services".
E. Click the OK button and then Click Yes to restart your computer.
Suggestion 3
============
Install Remote Destop client 6.0 on the problematic computer. Here is the
Web link for downloading:
http://www.microsoft.com/downloads/details.aspx?familyid=43C0EAE9-6B64-428F-
A9DC-F97F5A1B4493&displaylang=en
suggestion 4
============
Check the Application and system event log on terminal server and client,
find out the event related to terminal service and post the detailed event
log to newsgroup, so we perform a further troubleshooting.
Please update me with above results. If you have any concerns, please feel
free let me know.
Mike Luo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
.
- Follow-Ups:
- Re: local devices in a terminal session problem
- From: Mike Luo [MSFT]
- Re: local devices in a terminal session problem
- References:
- local devices in a terminal session problem
- From: Looksmart5000
- RE: local devices in a terminal session problem
- From: Mike Luo [MSFT]
- local devices in a terminal session problem
- Prev by Date: Re: What to add to Terminal Services to allow file transfer?
- Next by Date: RE: Licenses allocated longer than 90 days
- Previous by thread: RE: local devices in a terminal session problem
- Next by thread: Re: local devices in a terminal session problem
- Index(es):
Relevant Pages
|