Terminal server limiting CUPC connections to 10

I recently setup a new terminal server in our VM to replace an existing older server running 2008 Enterprise. It is using CUPC 7.1. the new server 2008 R2 Datacenter. It has CUPC 8.6 which matches the current version on Call Manager. After moving new users to the new server I discovered that the CUPC quit working after 10 connections. The app flashes on the screen for a second and quits. I don't have any issues on the old server and checked all the licenses to verify we are covered. What can I do? Please help! Thanks

So, WTS is not a supported environment. The closest the CUPC client ever got to this was:
Virtual Desktop Infrastructure (VDI) SupportCisco Unified Personal Communicator Release 8.5(5) and later is supported on the following hosted virtual desktop applications:•VMware View 4.5•Citrix XenDesktop 4.0 Note In a virtualized desktop environment, full audio and video capabilities are only available on Cisco Unified Personal Communicator when you are using the desk phone for phone calls. If you are using the phone on your computer, only the voicemail features are supported in a virtualized environment.
Secondly, CUPC was a massive Java-breathing, DirectX-dependant resource hog. Even if it did work, it would be silly to run on a Terminal Server because of how much overhead it would add. Thankfully Cisco scrapped the code base and rebuilt it off of C# (or C-something). The VDI solution support has expanded but still does not include WTS.
It's difficult for us to provide guidence when you're off the path well travelled. Maybe someone will chime in though..
Please remember to rate helpful responses and identify helpful or correct answers.

Similar Messages

10.7.5 Lion Server limiting AFP connections to 10

I have an Intel XServe, Late 2006 2 x 2 GHZ Dual-Core Xeon with 20GB DDR2-DIMM RAM running Mac OS X Server Lion 10.7.5 (11G63) that has started to limit AFP connections to 10. This is a problems as we use this server to host Network Home Directories for 1/3 of our students (approximately 100 student directories are hosted on this server via a fiber channel XServe RAID).
I know that OS X Server can handle thousands of simultaneous AFP connections...I'm using two other 10.7.5 XServes to host the other 200 student accounts (1 XServe is an Early 2008 2 x 2.8 Quad Core Xeon with 24 gb of RAM running the same OS Build and the other is an early 2009 2 x 2.26 Quad Core with 24 GB of RAM running the same OS X Server build). Both of those XServes currently have between 40-80 AFP connections. Before last week, the oldes XServe was functioning normally, allowing 20-60 connections. For some reason last week, AFP crashed on this system and when I rebooted the server it now refuses to allow more than 10 AFP connections (confirmed by an error message from clients attempting to connect). I know that this behavior is more indicative of OS X client which only allows 10 simultaneous connections. The only messages in the AFP error logs are:
AppleFileServer[172] <Info>: TCP Listener returned error on accept
repeated over and over again.
Anybody have any thoughts on why this might be happening? After everybody leaves today I'm thinking of disconnecting the RAID from this Server and then attaching it to one of the other two XServes and then re-mapping the the student accounts to the other servers, but I'd hate to decrease my load-balancing as this is already a fairly slow solution as it is.
Thanks,
Christopher

I've done some more digging and it looks like the three packages included in the update have about 4000 files that didn't get installed. A good number of them are .png or .icns files, but there are whole applications (e.g. VNCServer) that didn't get updated.
The system is currently in a state where it cannot install software via Software Update or via Installer.
Any ideas?

Cisco 2611 Terminal Server

Hi,
I have one of the 16 spider cables from my 2611 Terminal Server plugged into a console port of a device that exists behind the firewall. But, it does not appear to be working.
Config of 2611 Terminal Server below and output of show line when an attempt is made to connect the remote cisco router. I already have this solution working for other routers and all works.
Config of line 33 48 on terminal server:-
line 33 48
session-timeout 5
timeout login response 15
no exec
transport input telnet
transport output all
BunkerA_2nd_TS#sh host
Default domain is not set
Name/address lookup uses static mappings
Codes: UN - unknown, EX - expired, OK - OK, ?? - revalidate
temp - temporary, perm - permanent
NA - Not Applicable None - Not defined
Host Port Flags Age Type Address(es)
XIT 2041 (perm, OK) 0 IP 10.64.8.40
BunkerA_2nd_TS#
BunkerA_2nd_TS#sh line 41
Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int
* 41 TTY 9600/9600 - - - - - 15 0 0/0 -
Line 41, Location: "", Type: "SUN-CMD"
Length: 34 lines, Width: 80 columns
Baud rate (TX/RX) is 9600/9600, no parity, 2 stopbits, 8 databits
Status: Ready, Connected, Active
Capabilities: EXEC Suppressed
Modem state: Ready
Modem hardware state: noCTS DSR DTR RTS
Special Chars: Escape Hold Stop Start Disconnect Activation
^^x none - - none
Timeouts: Idle EXEC Idle Session Modem Answer Session Dispatch
00:10:00 00:05:00 none not set
Idle Session Disconnect Warning
never
Login-sequence User Response
00:00:15
Autoselect Initial Wait
not set
Modem type is unknown.
Session limit is not set.
Time since activation: 00:01:51
Editing is enabled.
History is enabled, history size is 20.
DNS resolution in show commands is enabled
Full user help is disabled
Allowed input transports are telnet.
Allowed output transports are pad v120 telnet rlogin udptn.
Preferred transport is telnet.
No output characters are padded
No special data dispatching characters

Mary
I wonder about this line of output:
Status: Ready, Connected, Active
and wonder what happens if you issue the command clear line 41 from privilege mode of the terminal server?
The output shows that it has been used 15 times. Has it worked before or has it ALWAYS failed?
If you remove the terminal server cable and connect directly to the router console port with a PC does it work?
If you connect a different cable from the terminal server to the router and attempt access with the different reverse telnet port does it work?
If you can provide answers to these we might be closer to having answers to your issue.
HTH
Rick

Outlook 2010 on Terminal Server, default timezone resetting to Central America time on log of

First, thanks for reading!
We have a user that travels frequently and uses Terminal Server often to connect. In his Outlook profile on the Terminal Server we have a default and secondary time zone set for him, as he travels through time zones often and wants to know what is when even
in other parts of the country. Just about every time he logs off and back on, his primary time zone is set to (UTC -06:00) Central Time (US & Canada) which is wrong, and his previous, correct, default time zone is then set to his secondary time zone. The
previous secondary time zone is of course wiped out.
His laptop is fine and does not do this under any circumstances. Has anyone seen this behavior before? I have already blown out the local profile on the Terminal Server, I'm at a loss here.
Thanks in advance for any and all help.

Are you in Citrix environment? Take a look at this article:
http://support.citrix.com/article/CTX303498
Do you have the 'use local client time' applied?
We're unfortunately in a stock Terminal Server environment, but I'll take a look! Thanks for the link.
We do have Terminal Server pulling time form clients when they connect, so ill take a hard look.

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.

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

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

Can't connect to terminal server via Mac RDC

Users can't log in to our terminal server (Server 2008) from Mac using RDC 2.1. After typing in the server name, the client asks the user to login. The user fills in their username, password and domain but receives and error stating "The credentials
that were used to connect to [server_name} are incorrect".
Any user, including myself who am a Domain Admin, get this error. When I log in using the domain's Administrator account, however, I can log in just fine.
None of this occurs when trying to login from a Windows client. The Mac I tested on is running OS X 10.5.8. Any help would be greatly appreciated. Thanks.

Hi,
For remote desktop in MAC OS, you can try to update the new Remote Desktop Connection. New Multiple Session Support gives Mac users simultaneous access to multiple
Windows-based PCs or to a network server that hosts remote applications and files. Since it is a Universal application, Remote Desktop Connection Client 2 is compatible with the latest technologies on Windows and Mac platforms.
Please refer to the following link:
Microsoft Remote Desktop Connection Client for Mac 2.1.1
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18140
Setting 'Allow connections from computers running any version of Remote Desktop (less secure)' in the Terminal server to sees if it’s work well.
Technology changes life……

SharePoint site connection with Office Professional Plus 2013 on Terminal Server

Hi,
Background info:
We use multiple Office 365 E3 subscriptions (12 now) and also have an Windows Server 2008 R2 Terminal Server.
The users may install Office 365 Pro Plus on their local machines and are able to connect to SharePoint online with the Office applications. Now not everyone has a PC so they log in to one of the two Windows Server 2008 R2 Terminal Servers. I do
however want one big happy family working with SharePoint so I installed Office Professional Plus 2013 and tweaked the Group Policies so that the start up screen and movie arent beeing showed.
When I log in with my test user on the Terminal Server (who has a E3 subscription) I miss the feature to add a location (to connect to the SharePoint site). I just do not have that feature. When I log in with my domain administrator account who also
has an E3 subscription, I am able to add a connection.
There is SO much info on the web about Office 365/Terminal Servers etc but I am not able to find what I was looking for.
Question:
What do I need to do so our Domain Users who log in to the Windows Server 2008 R2 Terminal Server are able to open/save files directly to the SharePoint site? How do I add the SharePoint location as shown in the image:

Hi,
SharePoint would not exist when Office 2013 initial installed. After you save a file to a SharePoint library for the first time, you can click
Save as you do for any file. Please try the following steps:
1) Add the document (Word file) to a document library on a SharePoint 2013 site
2) Click on the file within the SharePoint document library.
3) Click open in Excel
4) Save the file
5) Close Excel
6) Open Excel, select new Blank Workbook, File, Save As, "SharePoint" should now appear.
Regards,
George Zhao
TechNet Community Support

SQL2012: Internal Error: The operation terminated unsuccessfully. The connection timeout was exceeded. Server: The operation has been cancelled

When rendering a SSRS native mode report based on a query to SSAS the report with fail with the following error:
An error has occurred during report processing. (rsProcessingAborted) Cannot read the next data row for the dataset. (rsErrorReadingNextDataRow). The connection either timed out or was lost. Unable to read data from the transport connection:
An existing connection was forcibly closed by the remote host.
Putting a trace on the SSAS instance, I get an error:
Internal error: The operation terminated unsuccessfully. The connection timeout was exceeded. Server: The operation has been cancelled.
I've modified the IIS (6) application pool timeouts, the SSRS rsreportserver.config timeouts, and the SSAS timeouts. Restarted services, rebooted, and still I get this error.
The report will render if I select a shorter time period (less data, shorter query time).
Running SQL2012 (11.0.5058.0), SSAS and SSRS on separate servers, same subnet.
Any help or suggested troubleshooting greatly appreciated.

Please check the links below.
http://www.symantec.com/business/support/index?page=content&id=TECH186577
https://support.microsoft.com/kb/2200755?wa=wsignin1.0
http://msdn.microsoft.com/en-IN/library/ms155782.aspx
http://blogs.msdn.com/b/dynamicsaxbi/archive/2013/02/14/how-to-addressing-ssrs-session-timeouts.aspx

Mac Client that can connect to Terminal Server Gateway

Anyone know of a Mac app that can connect to a remote computer via a Terminal Server Gateway? The Windows version of MS Remote Desktop will do this but of course that is Windoz only.

You could try CoRD. I don't know if it has the TS gateway option either, but it is an RDC client.
CoRD (Microsoft RDC Screen Sharing)
<http://www.macupdate.com/info.php/id/22770/cord>

Word 2010 - "Connecting to printer" message when opening documents at Server 2008 R2 Terminal server

Our users experience sometimes the message "connecting to printer" while they open a document in Word 2010 (32-bit) on our Server 2008 R2 Terminal Server. This is behavior
isn't consequent but random. The default printer in this environment is a Net2Printer-printerdriver (1.16) which redirects the print jobs (in PDF-format) to the local client's default printer. This feature works well. We don't want to change the default printer
because this is the right one to use by our users.
After a long seeking trip on the internet I've found the Microsoft hotfix KB974991 which can fix this issue for Word 2007. My question is, is this also usable for Word
2010 (32-bit) and if not, is there maybe another fix for the 2010 version available?
Any other suggestions or workarounds are welcome!

Hi,
Please change following options test if it works:
Ÿ
Print proofs quickly
Enable the Draft output option. When you use this option, the document prints with minimal formatting. Therefore, the document
may print faster. This option is ideal for printing proofs.
To enable the Draft output option, follow these steps.
Note Some printers may not support this option.
Start Word.
Click File, and then click
Word Options.
In the Word Options dialog box, click Advanced, and then scroll down to the Printing
section.
Click to select the Use draft quality check box, and then click OK.
Ÿ
Use the background printing option that best fits your requirements
When background printing is enabled, you can continue to work in Word while your document prints in the background. Background printing uses additional
memory, and your document may print more slowly.
When background printing is disabled, your document prints faster. However you cannot work in Word until the print job is completed. If you do not have
to continue to work in Word while your document prints, disable background printing to speed up printing.
To do this, follow these steps:
Start Word.
Click File, and then click
Word Options.
In the Word Options dialog box, click Advanced, and then scroll down to the Printing
section.
Click to clear the Print in background check box, and then click OK.
Best regards
William Zhou
TechNet Community Support

Adobe Connect Add-in problems on terminal server

Windows 2003 Terminal server, IE7 and Flash version 10,0,12,36 using the Adobe hosted service
Were having problems with the add-in prompting to install though it has been. The add-in was “pre-installed” using the standalone package from the console as an Administrator.
The problem is that having launched a meeting the Administrator can use the add-in, but all other users are prompted to download \ install the add-in (again). Attempting to download the add-in fails with “A download error occurred, try downloading again”. There are no related errors recorded in the event logs on the server.
I've made calls to numerous Adobe support tel #s in an attempt to get support, or at least some response. Other than giving me another number to call, no one seems interested .

Rob, it sounds like port 1935 is being blocked. Can you verify that that port is open?
Have you gone to the Test Your Computer page for your connect account. After the diagnostics run, choose to send and email and then click on the details... link to see the results of the test.
Here is a link to that page for our hosted account, if that makes it easier: http://realeyesconnect.adobeconnect.com/common/help/en/support/meeting_test.htm
If needed, Connect only requires FP 10.3 or newer. If it comes to it, an older version of the Flash Player can be tested.

WSA S160 Support for Terminal Servers (How are terminal server connections handled?)

We have a terminal server environment with a mixture of computers and laptops. Currently we have multiple proxy servers and would like to considate down to one. Our current solution does not work well in a terminal server environment. We are looking for a way to integrate all equipment with one soluton and I was curious as to how the S160 handled users connecting via a terminal server.

Edadios thanks for the response. I was reading over this document (see attached), and it looks to me like the connection would be tracked via a cookie surrogate. My bigger concern is that we are looking to be able to track usage per user even though they are on a terminal server. Our current solution (Barracuda) is not able to perform this function. I am hoping to have a S160 on site this week to do some testing but was hoping to gather some intel in the forums prior to implementation.
The response helps clear up what protocols are in use but I am still wondering how terminal server connections are handled by the WSA and if they are truly handled and tracked per user instead of by the device they are connecing to.

Connecting to Terminal Server though RDP or CoRD?

I am running 10.9.1.
I have used RDP and CoRd successfully in the past prior to the latest OS upgrade. Neither program will connect to the terminal server and no one can connect to my Mac using TeamViewer or any other remote in.
Any ideas for troubleshooting?
Thank you,
Jeff

Peter--
Welcome to the Apple Discussions.
I actually don't know anything about this, but, like you, I'd expect you to need an application for the connection. Microsoft has a Remote Desktop Client for Mac that might well be what you're looking for. My guess would be that the .rdp file they gave you is probably the configuration for your network.
HTH,
charlie

Terminal server limiting CUPC connections to 10

Similar Messages

Maybe you are looking for