Terminal Server Freezing

I have several Terminal Servers that run Windows 2008 R2 that have been having issues recently. We just started requiring Smart Card Authentication on the server. Logon works with both username
and password and smart card logon. The smart card is required for Exchange services. A little after we changed to this, our terminal servers have begun freezing. By "freezing", I mean that when the users log on via their Thin Clients or Remote Desktop,
they are stuck at the "Group Policy Client is updating" screen. They are not able to log on to another terminal server (we have them all set in round robin for load
balancing) unless we log them off. When we log into the server, we must log on via the local machine by going into XenCenter because we get stuck when trying to just remote into them. Once this begins to happen though, we are not able to log the user off. We
can open Task Manager and click log off the user but they never get logged off. RDSM also stops reporting users logged into the servers as well. The only way we have been able to clear the users and fix the problem has been to restart the server and that logs
off dozens of users. <o:p></o:p>
This is an unacceptable situation here that's causing a lot of problems for our users and we tried a last ditch effort of rebuilding all of the servers. After rebuilding them all and getting
them online. They were acting fine for a few days. Now they are starting to do the same thing as the older servers and have the same problems. I have been googling fixes for this issue for a week with no solutions working so far. Any help would be amazing
since we are all out of ideas here. Thank you.<o:p></o:p>

Unless you're running 32bit terminal servers as VMs in Virtual Server 2005, this is the wrong forum for help.
Try reposting in the terminal server forum.
https://social.technet.microsoft.com/Forums/en-US/3655b7da-08df-4c11-b170-42f6acd4d6c6/session-on-terminal-server-freezing?forum=winserverTS
https://social.technet.microsoft.com/Forums/en-US/1a416400-824d-4333-aac9-900b41915f1a/2008-terminal-server-sessions-freezing?forum=winserverTS

Similar Messages

Problem with Photoshop hangs/freezing for users on a terminal server

Dear Forum!
I'm having some trouble with Photoshop freezing over a period of ~20 minutes when you (1.) user the eraser with special brushes and (2.) copy and paste material from a PDF to Photoshop. As you might notice by the size of this post i'm getting quite depserate over here and need some help.
A Little background information...
Photoshop CS6 is installed on a terminal server with ~25 Active users where 3 of them are using Photoshop.
The operating system on the server is Windows Server 2012 R2.
There are no additional add-ons just a plain installation of Photoshop in that matter.
The server uses 40-60% of the memory most of the time (mostly a bit less, some times a bit more but never 100%) and 40% of the CPU.
There's enough space free on the disc.
The problem in detail...
There are two occasions where the freezing has occured most of the time. After it hangs for the first time, it will happen everytime you do any of the operations over a period of ~20 minutes and it's Mutual for all users. When it freezes, the whole terminal session freezes but the program i still responding (it's not getting set to "not responding") when viewed from Another user through the task manager. Ending the process as an administrator sometimes work, although from the moment i end he proces it takes about 10-60 seconds Before the program actually Closes and the user gets back Control. The easiest thing to do most of the time is if an administrator forces them to log out.
1. The first occasion is when you use the eraser with a brush that's not standard but manually added. The names of the brush packages used are:
Extacy__Elemental
KKC_Fractal
Kornkid's_Grunge_Set
and the problem is with all brushes inside those packages. The way i evoke the problem is the following:
     1. Start Photoshop
     2. Create new
     3. Fill the background with any color
     4. Select the eraser tool
     5. Change the brush to one of the ones mentioned above
     6. Program freezes
2. The second scenario when the problem occurs is when the users copy something from a PDF to Photoshop. The way i evoke this is:
     1. Open a PDF
     2. Select area and copy it
     3. Open Photoshop
     4. Create new
     5. Paste into Photoshop
     6. Program freezes
Solutions we have tried so far...
I've been working on this for several round now and i'm not entirely sure on what exactly i have done. I will try and do the following solutions once more but i'm pretty sure that i have tried most of them.
Update graphic card drivers.
Resetting all Tools:
     1. Select options for a tool
     2. choose "Reset all Tools"
Resetting presets:
     1. Hold ctrl + shift + alt while Photoshop is starting
     2. select "yes"
Tested if it matters if i have a pen connected or not, which it doesn't.
Removed the special brushes (but it still freezes when copy/paste from PDF)
Removed "save in background" and "automatically save recovery information" options
Updated to latest version.
Turned off OpenGL
Solutions i haven't, but will try...
Reinstall Photoshop
Change font preview size
     1. Go to "type"
     2. select "Font prview size"
     3. select "none"
Delete system font cache
Close all Adobe applications including the Creative Cloud desktop app (if installed).
Navigate to \Windows\ServiceProfiles\LocalService\Appdata\Local
Delete the *FNTCACHE*.DAT or *FontCache*.dat files.
NOTE: The asterisk (*) indicates various numbers, letters, or words, such as FontCache-S-1-5-21.dat or COFFfntCache.dat.
Delete Photoshop font cache
Exit Photoshop and the Creative Cloud desktop app (if installed).
Navigate to the appropriate folder
Photoshop CS6 and earlier.
Windows XP: \Documents and Settings\Local Settings\Application Data\Adobe
Windows 7: \Users\[user name]\AppData\Local\Adobe
Photoshop CC and CC 2014
Windows 7 and 8: \Users\[user name]\AppData\Roaming\Adobe\Adobe Photoshop CC or CC 2014
     3. Delete the TypeSupport folder (Photoshop CS6 and earlier) or the CT Font Cache folder (Photoshop CC and CC 2014), and empty the trash.
Some links i have been using...
http://blogs.adobe.com/crawlspace/2012/07/photoshop-basic-troubleshooting-steps-to-fix-mos t-issues.html
http://helpx.adobe.com/photoshop/kb/photoshop-cs6-gpu-faq.html#troubleshoot
http://helpx.adobe.com/photoshop/kb/troubleshoot-fonts-photoshop-cs5.html

Hi Mylenium!
Thanks for your reply but since the users work on the terminal server via remote dektop the only data sent through the network is a "Picture" of what is happening on the server. All the operations are handled on and by the server and nothing is executed on the users local machine. Also all files are stored on the server therefore the load on the network is minimum.
We are not the first in the World to run this setup and i know that this is possible to do since i've read about others running PS like this.
Kind Regards,
J. Alm

Terminal Server - Opening & closing attachment freezes GW

Hello,
we are running a Terminal Server Farm on Windows 2008 R2 with GroupWise 2012 SP2.
All of our users have problems when opening an attachment (PDF, DOC, XLS...) from a mail and closing the opened Application (Word, Acrobat Reader, Excel....). After closing the Application GroupWize freezes for some seconds. If you click anything in GroupWise in this time, GroupWise crashes.
You've to wait up to 10-15 seconds until you can do something in GroupWise.
Our Users are really "nerved" about this situation. This problem still exists an all of our Terminal Servers.
Any Ideas what we can do ?
Regards.

Originally Posted by konecnya
In article <[email protected]>, DavudOeden wrote:[color=blue]
I don't see this on the single Windows 2008 R2 Standard TS with GroupWise
2012 SP2, client build 108211.
This does feel more like a Windows/ Windows app (GW client or other)
issue, so I would certainly check the Windows event logs for any clues.
- If you are at the primary console of any of the servers (i.e. Physically
at the box or vm equivalent), does the same problem still happen?
- Doe the POA logs show anything when this happens? Especially if you turn
up the logging to verbose.
- Try disabling the anti-virus for a test in case it is part of this.
- Make sure the TEMP folders are getting cleared periodically.
- To eliminate the issue of crud collecting in profiles, setup a new user,
both GW and on the Terminal Server, and see if it can be reproduced with
those ID.
[color=blue]
Hello,
thanks for you're reply.
- The Problem still happens on the "physical" console.
- The Windows Event Logs does not show anything. It's only a freeze which
can take up to 10 seconds and more. After this time, GroupWise works fine again.
Most times it takes only a few seconds.
- The Temp Folders are cleaned at logoff ("C:\Users\USERNAME\AppData\Local\Temp\xxxxxxx" ).
There are up to 4 GroupWise Directorys (XPgrpwise, XPGWSync, XpGWViews & XPNotify). They are not roaming.
- I've tested this with an absolutely new created user. Same Problem.
- Tested on an absolute new TerminalServer. Same Problem.
But what I figured out, if there are only a few users connected to the server, the problem is not noticeable.
The more users are connected to the server, the higher the possibility that this freeze problems occur.
I'm going to check the groupwise POA logs, but I dont think that there will be log entrys about this problem.
I've installed yesterday the groupwise client build 112764. I'm going to test today if the newer build
makes the same problem. At the moment there are not enough users logged in to test it.
Kindest regards for your tips,
I hope we're going to figure out the problem :-)
D. Oeden

Terminal Server Session Freezes/Hangs

Hi,
Just a little background info, I have a terminal server farm running Windows 2003 R2 Enterprise behind a hardware load balancer and I am utilizing the session directory service.
The issue I am running into is users’ terminal sessions will freeze up when they reconnect to their existing session. There are two scenarios that this happens. When a user moves from one desk to another and they log into the terminal server and reconnect
to their session or after a period of inactivity their session will lock them out and then they log in. All the user gets is usually only a partial display or just the desktop backgroup and the session doesn't respond. I used to just kill their session and
have them log back in but now I have narrowed it down to the OUTLOOK.EXE process. If I log into the server they are on and kill their Outlook process their session starts to respond. I have noticed that Outlook will be utilizing 2% to 10% CPU when it is occurring.
We are running Office 2010. It seems to be random and very frustrating.
Any help would be greatly appreciated.
Thanks

Hi,
Thanks for your posting.
According to your issue, I can let you know some solutions but before that want information from your side.
a. How many clients are logged in TS session at a time?
b. Have you tried by disabling Offloads?
   Information regarding Offloads:
   http://support.microsoft.com/default.aspx/kb/951037
c. You check the performance of your server by using Performance Monitor tools and can capture logs.
   http://technet.microsoft.com/en-us/library/cc749115.aspx
Please install the required hotfixes available for the issue.
1. Terminal Server and connected Terminal Services clients pause when a Terminal Services client logs on or logs off (KB 324446):
   http://support.microsoft.com/kb/324446
2. A Windows Server 2003-based or Windows Server 2008-based terminal server stops accepting new connections, and existing connections stop responding (KB 956438):
   http://support.microsoft.com/kb/956438
Might This Helps!
Thanks.

Adobe Acrobat X Pro - Windows Terminal Server 2008

Hi All,
Im hoping some one maybe able to help me on this, We have recently purchased the Adobe Acrobat X Pro for one of our clients and have just installed it onto their Windows 2008 x32 Terminal server. Inatall appeared to be fine, no errors reported and nothing logged into the event viewer. However we seem to be having issues with it... I did read a PDF guide early last week that said the X Pro should work fine on a Server 2008 - The install instructions where rather straight forward and I thought their would have been more to it than just installing it via the control panel.
The issue we have is the program opens up ok and is usable for about a min and it then crashes with no obvious reason, From looking in the event log it appears to report issues with the PDApp.exe and the Kernel32.dll - Has anyone come across any similar issues?
Many Thanks

Hi,
You can also send the crash dump by following the below mentioned steps:
Install WinDbg from http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
Launch WinDbg via the shortcut
Click File->Open Executable
Select Acrobat.exe from "C:\Program Files\Adobe\Acrobat 10.0\Acrobat\Acrobat.exe" and hit "OK"
Remember to press "g" and hit enter when you encounter the first breakpoint and then you will see a text "Debuggee is running" and Acrobat will be launched
Open whatever file is it that produces the crash in Acrobat.
When you have successfully reproduced the sceanrio causing the crash/freezing of Acrobat X, enter the below command in the WinDbg terminal
.dump /ma c:\temp.dmp (Hit enter)
This will produce the crash dump at C:\ by the name of temp.dmp
After that please upload the dump (compress the dump using WinZip or likewise) at some third party sites and provide the link for the same. Also, if it’s possible could you share the PDF as well, for which your application crashes on a consistent basis.

Installing Acrobat Pro 9.2 in a Terminal Server Environment

Hi everyone,
we're facing massive problems in our attempts to install Acrobat Pro 9.2 in a terminal server environment. It seems to be impossible to convert for example a .doc-file into a pdf via the adobe pdf-printer using a restricted user-account. It causes an "Access denied"-popup. We solved this subproblem by granting the user write-permission in the respective registry-key (HKLM\Software\Adobe). By now everytime we try, the application freezes after the "copy-status-bar" is filled. Using a power user instead of a normal user solves this problem. So the question is what's the relevant difference between the rights of those user groups.
Thanks for your help!

You can also try to update your Acrobat by applying patches one by one.
to update upto latest version of Acrobat i.e 9.5, you need to apply the following updates
9.3.0   download location: < http://www.adobe.com/support/downloads/detail.jsp?ftpID=4605 >
9.3.2   download location < http://www.adobe.com/support/downloads/detail.jsp?ftpID=4654 >
9.3.3   download location < http://www.adobe.com/support/downloads/detail.jsp?ftpID=4695 >
9.4      download location < http://www.adobe.com/support/downloads/detail.jsp?ftpID=4851 >
9.4.2   download location < http://www.adobe.com/support/downloads/detail.jsp?ftpID=4931 >
9.4.5   download location < http://www.adobe.com/support/downloads/detail.jsp?ftpID=5118 >
9.4.6   download location < http://www.adobe.com/support/downloads/detail.jsp?ftpID=5237 >
9.5     download location < http://www.adobe.com/support/downloads/detail.jsp?ftpID=5330 >
You can download the above mentioned patches from the corrosponding download link and apply one by one in same order as mentioned above.
This is a bit lengthy process, but I hope you will be able to update your Acrobat.
Thanks.

Terminal Server Locking Up

I have several Terminal Servers that run Windows 2008 R2 that have been having issues recently. We just started requiring Smart Card Authentication on the server. Logon works with both username
and password and smart card logon. The smart card is required for Exchange services. A little after we changed to this, our terminal servers have begun freezing. By "freezing", I mean that when the users log on via their Thin Clients or Remote
Desktop, they are stuck at the "Group Policy Client is updating" screen. They are not able to log on to another terminal server (we have them all set in round robin for load balancing) unless we log them off. When we log into the server, we must
log on via the local machine by going into XenCenter because we get stuck when trying to just remote into them. Once this begins to happen though, we are not able to log the user off. We can open Task Manager and click log off the user but they never get logged
off. RDSM also stops reporting users logged into the servers as well. The only way we have been able to clear the users and fix the problem has been to restart the server and that logs off dozens of users.
This is an unacceptable situation here that's causing a lot of problems for our users and we tried a last ditch effort of rebuilding all of the servers. After rebuilding them all and getting
them online. They were acting fine for a few days. Now they are starting to do the same thing as the older servers and have the same problems. I have been googling fixes for this issue for a week with no solutions working so far. Any help would be amazing
since we are all out of ideas here. Thank you

I'd like to tell you that this worked before so we should be able to make it work again. But I can't honestly look in the mirror and convince myself I am good at my job when I don't make my clients upgrade.
That will have to be the fix; Newest version of Adobe on the TS!

DS XI 3.0 on Terminal Server

Hi All,
We setup DS XI 3.0 on a Windows 2003 Terminal Server. 6 developers are now using the designer tool. For each of them a MySQL Database has been setup and local repositories were created.
One problem occurs: when one developer opens the Designer he always sees the repository information that was last used from ANY of them. Is there any way to solve this issue?
Thanks and Kind Regards,
Ingo Taraske

Hi Ingo,
As discussed in this forum recently, Designer is not supported for use by multiple concurrent users via Terminal Services -- the application was never designed to support this. The application was designed to support Citrix, though. Please install the Designer tool on individual Windows installations for each of your users.
Thanks,
~Scott

How do I connect to a terminal server with my mac book pro

How do I connect to a terminal server with my mac book pro

Use the Remote Desktop icon on the tray and make sure to use the Fully Qualified Domain Name (FQDN) on the 'name of server' field. If that does not work then use the IP address to connect.

Audio lag in video while on Terminal Server

Hi Everyone,
We are having an issue with audio being out of sync when viewing flash video on a terminal server. The terminal server is running Windows 2008r2. The audio seems to lag behind the video by about 1 sec. We are planning to rollout training videos
and about half our users are on Terminal servers.
Here are some of the things we tried:
http://blogs.msdn.com/b/rds/archive/2009/05/11/what-s-new-in-remote-audio-for-windows-7.aspx?PageIndex=2#comments
On the server policy:
Computer Configuration ? Administratrative Templates ? Windows Components ? Remote Desktop Dession Host ? Device and Resource Redirection ? Limit Audio Playback Quality (Enabled, Audio Quality: Medium)
In the RDP file add a line that says:
audioqualitymode:i:1
thanks...
Mark

Hi Mark,
Thank you for posting in Windows Server Forum.
Can you please check which version of RDP client installed on your system? For better feature suggest you to install RDP 8.1.
Remote Desktop Protocol 8.1 Update for Windows 7 SP1 released to web
http://blogs.msdn.com/b/rds/archive/2013/11/12/remote-desktop-protocol-8-1-update-for-windows-7-sp1-released-to-web.aspx
Meanwhile go through beneath article for information.
Multimedia Redirection Improvements in Windows 7 and WS2008 R2 – Part 1
http://blogs.msdn.com/b/rds/archive/2009/07/24/multimedia-redirection-improvements-in-windows-7-and-ws2008-r2-part-1.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

I have a new install of Windows 2012.  I have two physical servers. One is a W2012 std Domain Controller ("DC"). The Second is configured as W2012 HyperV  ("HV"). Under HV I have
two VMs. One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS"). All systems are behind a firewall appliance. Exchange is working via Outlook and OWA internally and externally. The self
created SSL must be installed manually on external machines since it comes up as an untrusted certificate. Once installed remote outlook works and OWA works. I have configured the terminal server and I am able
to login remotely as various users under my "TS group". The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
for alias@ domain, then fails the logging on to the mail server) The error reads: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The
connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC. I have
tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command. I have also tried to use the guid via "Get-Mailbox
ALIAS | fl name, exchangeguid. Keep in mind all desktop users on the network are connecting to Outlook without issue.
I would appreciate any thoughts on solving this issue.

Hi,
According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
Regards,
Winnie Liang
TechNet Community Support

Unable to Copy File From Terminal Server to Client Share

Hi
For years client have been able to copy files from our Windows 2003 Terminal Server to their local workstation using:
copy myfile \\tsclient\mydrive\myfolder
However we upgraded to Windows 2012 Server R2 and now Windows 7 Pro clients cannot copy files. The copy function creates the file name in their local folder but no content is sent after maybe 20 minutes or so the copy function times out and they get an
error message saying that the application was unable to write to the file. I have tried this function with my Windows 8.1 workstation and the file copies properly and it works fine for older Windows XP clients. Does anyone know why Windows 7 clients
are experiencing this issue.
Thanks
Simon

Hi Simon,
Initially please use latest RDP version 8.1 for windows 7 and check result.
What’s the file size which you are copying?
Does this happens for all users and on all computers?
You can try below method might resolve your case.
1. Login to remote computer using Remote Desktop (RDP).
2. Open Task Manager in the remote machine
3. Click the "Process" tab
4. Locate a program called "rdpclip.exe"
5. Right click and select "End process" to kill this program
6. Click on "File" menu in the task manager and select "New Task (Run)"
7. Type rdpclip.exe and press the button to start the process.
By killing existing instance of the rdpclip.exe and restarting the program, you can get your copy paste work again in your remote desktop.
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Copy File from Terminal Server to Workstation Failure

Hi
For years client have been able to copy files from our Windows 2003 Terminal Server to their local workstation using:
copy myfile \\tsclient\mydrive\myfolder
However we upgraded to Windows 2012 Server R2 and now Windows 7 Pro clients cannot copy files. The copy function creates the file name in their local folder but no content is sent after maybe 20 minutes or so the copy function times out and they get
an error message saying that the application was unable to write to the file. I have tried this function with my Windows 8.1 workstation and the file copies properly and it works fine for older Windows XP clients. Does anyone know why Windows 7
clients are experiencing this issue.
Thanks
Simon

Hi Simon,
The copy command should also work on the Windows 7 clients. Please provide the detailed error message when run the command on the Windows 7 clients.
You could also use robocopy command to achieve this.
Robocopy
https://technet.microsoft.com/en-us/library/cc733145.aspx?f=255&MSPPError=-2147217396
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

User gets "This network connection does not exist" when she tries to log on to Terminal Server (2008 R2)

User gets "This network connection does not exist" when she tryes to log on to Terminal Server (2008 R2)
I got more than 100 users. Shes the only one getting is. We tried four computers (All Windows 7 Pro)
Nothing useful in event viewer to mention.

Hi,
Thank you for posting in Windows Server Forum.
Does that user able to login previously?
From your comment, it seems that there is some permission issue with that user. As you have checked that user with different system also. Please check that user is added under “Remote Desktop User” local group and also allowed “Allow log on through
Remote Desktop service” permission under group policy. Also please check that when user tries to login it uses “Domainname\Username” format.
In addition for a try, also check by disabling firewall on one particular system.
To add users and groups to the Remote Desktop Users group by using Local Users and Groups snap-in:
1. Click Start > Administrative Tools, Open Computer Management.
2. In the console tree, click the Local Users and Groups node.
3. In the details pane, double-click the Groups folder.
4. Double-click Remote Desktop Users, and then click
Add.
5. In the Select Users dialog box, click Locations to specify the search location.
6. Click Object Types to specify the types of objects you want to search for.
7. Type the name you want to add in the Enter the object names to select (examples) box.
8. Click Check Names.
When the name is located, click OK.
More information:
Remote Desktop disconnected or can’t connect to remote computer or to Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2
http://support.microsoft.com/kb/2477176/en-us
Hope it helps!
Thanks,
Dharmesh

VPN Client and Terminal Server

We have several clients that allow us to vpn into their systems and it has come to the point that we are getting software incompatabilities. What I am trying to do is set up "compatable" connections on a Terminal server box and let our people access this from their workstations. The problem is when the acuall connection thru the vpn client is made they loose connection to the terminal server. I have tried putting in 2 nic's into the terminal server and am able to allocate one for the terminal server but can not find a way to allocate the other to the VPN CLient. Is this possable or is there another way to accomplish this?
Thanks

Close,
What I have is one machine with 2 nic's
NIC #1 = Terminal Server Access (local lan only) Locked in via registry settings to use ONLY this NIC
NIC #2 = I would like to "LOCK" the Client software to use ONLY this nic (has a dynamic IP for local lan and access to the Inet via a router.
Problem: When you connect to the T-Server all is fine UNTIL you start up the client software to access our clients systems via the web connection to the T-Server on the local side stops and gives the appearance of a frozen screen.
manualy disconnect person from the T-Server and kill the cisco client software then you can re-connect to the T-Server (and it all starts over again)
The Cisco software acualy makes the connection to our clients system but we can not tell because it want BOTH the NIC's for itself and stops access via NIC#1 to the T-Server.

Terminal Server Freezing

Similar Messages

Maybe you are looking for