Slowness when connecting to RemoteApp configured in Windows 2008 R2 Server using RDP file

Dear All,
When connecting to a RemoteApp configured in Windows 2008 R2 with less privileged user it takes ~20 seconds to connect.
Initial connection to
application takes about 20-30 seconds and once loaded, subsequent RemoteApp connection takes
2-3 seconds. i.e. if there is a disconnected session available in the server it connects quickly otherwise it takes long time.
I am seeing this issue with Windows 2008 Server, when I connect to a Windows 2012 Server RemoteApp gets
connected quickly. Also if I try with higher privileged user (like RemoteAdmin) connection is quick. The user I am trying is having lot of group policies set to limit user access to file system, desktop and registries.
If I keep UAC settings to minimal level connection happens quickly(i.e. solves this issue). But I am
not supposed to change the server UAC setting. It seems this has something to do with the list of group policies set for the user.
Any suggestion to avoid this first time connection delay for less privileged users for connecting to RemoteApp (in Windows 2008 Server).
Thanks
Bachuu

Hi Bachu,
Thank you for posting in Windows Server Forum.
First of all, if you are using RD Gateway serve then I would like you to
uncheck the “Bypass RD Gateway server for local address” under RemoteApp Manager Checkbox and notify the result.
Configure Remote Desktop Gateway Settings
Also like you to update the RDP client version to RDP 8.1 and then check the result. In addition,
I will suggest you to check that you have proper certificate in place. You can enable certificate revocation checking on RD Gateway client. Might due to this, you are facing issue. Please notify that you find any certificate related warning. Refer below article
for information.
How to Enable Certificate Revocation Checking on a Remote Desktop Gateway Client
Hope it helps!
Thanks.
Dharmesh Solanki

Similar Messages

Downloading files on a Windows 2008 R2 server using IE 9

Hi.
Trying to download some fiels from Microsoft download center, but receiving the following message: "Your current security settings do not allow this file to be downloaded"
Have tried the following in IE 9:
Turned off Protected mode.
The page is added to Trusted site.
         Trusted site is configured as follows:
                         Dowloads is Enablet
                        Font download is Enablet
           Under Miscellaneous has the following settings:
                        Allow META REFRESH, enablet
                         Allow webpages to use restrict3ed protocols for active content, Prompt
                         Allow webpages tgo open windows without address or status bar, enablet
                         Launching applications and unsafe files, Pompt
                         Launceing programs and files in an IFRAME Promt
Still not possible to download a security patch from Microsoft download senter.
Looking forward to a solution.
Thank you in advance.
Kind regards
DagN

Hi,
Please check the following blog to
see whether you can resolve the issue.
http://jaredheinrichs.com/your-current-security-settings-do-not-allow-this-file-to-be-downloaded.html
Important Note: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to
you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.
Best Regards,
Vincent Hu

Wyse Thin client not connecting to Windows 2008 R2 server

Configuration
SBS 2011 Server
Windows 2008 R2 server with Remote Desktop Services installed, License Manager installed.
WYSE WT3125SE thin clients with Windows CE 5
I setup the Windows 2008 with Remote Desktop Services and was able to successfully connect the Thin client. Then I installed the License Manger and applied my Open license using User Cals. Was able to login. Next day I get the following
error-"Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again" I still can connect fine from other machines even Windows Home Ed.
I remove license server and still was unable to connect. Built a second Windows 2008 R2 server with RDS on it. Was able to connect without issue. Pointed it to the first RDS server license manager and have still been able to connect with
the Thin Client. The thin client can rdp to the SBS server without issue in admin mode, can connect to RDS2 server but not RDS1 with the license manger. So my issue is with the license and so my question is what is it with the license server
running on that server that is keeping thin client from connecting. I even did a reload of RDS1 and tested connecting throughout the process and it worked up until I applied the license and then it stops. And then if I uninstall the license, rds, remove
from domain still not able to connect. Any help would be appreciated.

We had the same problem with older terminals after cloning a 2008R2 rds server and sysprep it.
The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error : Because
of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again"
After reading all of the postings about this issue and tried the reactivate solution of the license server,
I was sure that it had something to do with the x509 certificates that are generated the first time you connect to a valid license server.
What I did, I installed a new license server activate it but did not install licenses on it.
I pointed the defective rds server to the newly installed license server and deleted the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
Certificate
X509 Certificate
X509 Certificate ID
X509 Certificate2
Then reboot.
After the reboot all old terminals can connect fine again. As final step I pointed the rds server to the same license server as the other ones,
reboot and all worked fine.
So conclusion is that when you pont a rds server to a license server that has the new type of licenses on it it will generate the wrong x509 certificates
that are not supported by the older clients, by pointing it first to 1 without any rds calls on it, it generates the older x509 certificates which are compatible with the older rdp clients then the switch to new license server will then not regenerate the
x509 certs so it keeps working.
I hope this helps someone
This issue was driving me crazy so very happy that it is resolved now
Cheers Frits

HT4972 I am trying to update ipod touch from ios 4.3.2 to ios 6.1.3. I have it connected to my computer, and the summary in itunes indicates the update is available. However, when I click "update", it opens Windows Explorer and waits for a file name to

I am trying to update ipod touch from ios 4.3.2 to ios 6.1.3. I have it connected to my computer, and the summary in itunes indicates the update is available. However, when I click "update", it opens Windows Explorer and waits for a file name to open.

I am not at that computer now, but I did check via windows update & with the check updates menu choice in the itunes program - neither indicated a newer version of itunes is available. (it is a vista computer).
The itunes software on the computer displays my ipod & the current ios (4.3.2), and indicates a newer ios is available (6.1.3). When I choose "update", I am taken to Windows Exploer and prompted to choose a file to open. it is as if the "update" button has the incorrect code attached to it.
The ipod is working, but there are several app I would like to install, but I can't with the current ooperating system.

Solaris nis client can't connect to Windows 2008 NIS Server across subnets

I have been using Microsoft Windows Server for NIS for years to centralize some accounts accessing Solaris and Linux OS.
Windows 2003 R2 Indentity Management for UNIX version of Server for NIS was last working version with Solairs.
After upgrading Domain to Windows 2008 all Solaris clients that are on different subnets fail to bind and connect to NIS servers now.
These servers already were setup using ypinit -c to manually add the NIS servers to connect to and prior to Windows 2008 this worked.
Now no Solaris nis clients on different subnets (no firewall between) can connect , but other Unix/Linux OS connect fine.
Is this a known issue and can we get a resolution as it seems only Solaris is affected?

Hi Mid.Hudson-IT,
Before we begin ,we should ensure we have configured the printer server correctly .
Here is a link for reference of configuring the printer server .
Print server role: Configuring a print server
https://technet.microsoft.com/en-us/library/cc775791(v=ws.10).aspx
"I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via DNS"
From this sentence ,I can`t figure out whether you have tried to ping the server both with the IP adress and name adress from the client ?
If we can ping the print server from the client,we can ensure the connection to the printer server is good .
Then we can try to install the printer driver directly to have a check .In the adress bar of Windows Explorer ,input "\\server name \the printer name"
If we cannot ping the print server ,we should troubleshoot the network issue firstly.
We also can check the event viewer for more information to troubleshoot this issue .
Best regards

Remote Access to Windows 2008 R2 Server configured with local IP

Hello,
I have a Windows 2008 R2 Server configured with local IP (e.g. 192.168.1.115).
Please how can I access it remotely outside its local domain through (remote desktop connection).
Thank you.
Tony.

Hi Tony,
Based on your description, you would like to connect to the Windows 2008 R2 server via remote desktop connection.
So you need to enable remote desktop on the Windows 2008 R2 server if it is not already.
1.Install and configure the Remote Desktop Session Host role service in the Windows 2008 R2 server.
2.Add related user to the Remote Desktop Users group in the Windows 2008 R2 server.
3.Configure remote desktop connection in the Client.
Also, due to you would like to access it remotely outside the domain, so you will need a VPN connection or a port forward to connect through.
For more details, please refer to the guide below,
Installing and Configuring Remote Desktop Session Host
http://technet.microsoft.com/en-us/library/dd883253.aspx
Allow Remote Desktop connections from outside your home network
http://windows.microsoft.com/en-IN/windows7/allow-remote-desktop-connections-from-outside-your-home-network
Best Regards,
Tina

When I try to print using Windows 2008 print server I have to use the generic print drivers supplied. If I use the OEM driver the printer locks up. I have tried a HP 4 plus and a Canon Copier.

When I try to print using Windows 2008 print server I have to use the generic print drivers supplied. If I use the OEM driver the printer locks up. I have tried a HP 4 plus and a Canon Copier.

A number of vendor drivers written for OS X cannot be used when connecting via SMB to a printer that is shared by Windows. This is due to limitations of the driver.
In some cases, if you were to enable the LPD Print Service in Windows, you can connect to the share using the same syntax as SMB but on the Mac you would use the LPD as the protocol.
If you can reply with the brand and model of printer you have then we may be able to provide more information.

When connecting to the public wifi cannot receive mails, either use internet

when connecting to the public wifi cannot receive mails, either use internet

I believe I may have solved this
When you can't log into public WiFi ...
with an iDevice…
because the Server times out ...
or the login/registration page just won't load ...
********Simply do this***********
Go into settings> WiFi and tap the little info icon for the network you are trying to join
If you see two slider buttons, these are the cause of your woes
One says "Auto Join" (or similar) - you can leave this ON
The second button is "Auto Login" - you must turn this OFF (slide it left so it is grey not green)
Now go back and reselect the network.
If the login page doesn't come up automatically, open a Safari window and enter any address
Bingo!
I have reproduced this issue and solution in 100% of the public WiFi spots which I could previously not access. Please not that I also have "Block Pop-Ups" turned OFF in Settings> Safari, though I do not know if this is a necessary step.
I have filed a bug report with Apple. Feel free to contact them yourselves if this workaround works for you.
Peace y'all
<Edited by Host>

Got exception when running CrystalReportViewer on 64 bit Windows 2008

We have a client/server app built with c#, .NET2, CR2008 .net runtime SP2, and VS2008. The smart client hosts a CrystalReportViewer, which consumes the ServerFileReportService.
The client on XP, 2003, Vista, and 32 bit Windows 2008 works fine with 32 bit Windows 2008/2003 server. But the client on 64 bit Windows 2008 throws the following exception,
EXCEPTION >>
IndexOutOfRangeExceptionMessage: Index was outside the bounds of the array.
Source: CrystalDecisions.Windows.Forms
TargetSite: System.String GetResourcePath()
StackTrace:
   at CrystalDecisions.Windows.Forms.ParameterPromptControl.GetResourcePath()
   at CrystalDecisions.Windows.Forms.ParameterPromptControl.BuildPromptingRequestContext(PromptingHTMLFeedback feedback)
   at CrystalDecisions.Windows.Forms.ParameterPromptControl.BuildPromptingRequestContext()
   at CrystalDecisions.Windows.Forms.ParameterPromptControl.StartPromting()
   at System.Windows.Forms.Control.OnVisibleChanged(EventArgs e)
   at System.Windows.Forms.Form.OnVisibleChanged(EventArgs e)
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Edited by: Frank88 on Oct 9, 2009 8:55 PM

Hi Jonathan,
Currently the .NET solution contains over 70 assemblies, and only one assembly has reference to CR2008 .Net runtime SP2. All the 70 projects for each assemblies are compiled with Platform Target set to Any CPU. We build an installer with InstallShield, which deploys the runtime by CRRuntime_12_2_mlb.msi.
If we resolve all the parameters, and donu2019t prompt user for the parameters, then the same report runs fine on 64-bit Window 2008. Otherwise we always get the error on prompting parameters.
We resolved the issue by recompiling the exe with Platform Target set to (x86). And all the 70 assemblies are still compiled with Any CPU.
Regards,
Frank
Edited by: Frank88 on Oct 12, 2009 11:07 PM
Edited by: Frank88 on Oct 13, 2009 9:30 PM
Edited by: Frank88 on Oct 14, 2009 3:28 AM

Unable to login to Report Service on Windows 2008 R2 server

I have reporting services installed on a Windows 2008 R2 server, When I make and RDP connection to the server and go to http://servername/Reports everything works fine. When I try to connect from another client to the web service, it asks for username and
password. it fails 3 times and the shows a blank page.
When I see the Event Viewer in the server (Windows Logs --> Security, I can see an Audit Failure:
Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          9/4/2014 11:46:25 AM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      MI-SWACO-DB.houston.livequest.net
Description:
An account failed to log on.
Subject:
   Security ID:       NULL SID
   Account Name:       -
   Account Domain:       -
   Logon ID:       0x0
Logon Type:           3
Account For Which Logon Failed:
   Security ID:       NULL SID
   Account Name:       Administrator
   Account Domain:       HOUSTONLQ
Failure Information:
   Failure Reason:       An Error occured during Logon.
   Status:           0xc000035b
   Sub Status:       0x0
Process Information:
   Caller Process ID:   0x0
   Caller Process Name:   -
Network Information:
   Workstation Name:   MI-SWACO3
   Source Network Address:   -
   Source Port:       -
Detailed Authentication Information:
   Logon Process:
   Authentication Package:   NTLM
   Transited Services:   -
   Package Name (NTLM only):   -
   Key Length:       0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
   - Transited services indicate which intermediate services have participated in this logon request.
   - Package name indicates which sub-protocol was used among the NTLM protocols.
   - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>4625</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-04T16:46:25.247229500Z" />
    <EventRecordID>8917</EventRecordID>
    <Correlation />
    <Execution ProcessID="504" ThreadID="1344" />
    <Channel>Security</Channel>
    <Computer>MI-SWACO-DB.houston.livequest.net</Computer>
    <Security />
</System>
<EventData>
    <Data Name="SubjectUserSid">S-1-0-0</Data>
    <Data Name="SubjectUserName">-</Data>
    <Data Name="SubjectDomainName">-</Data>
    <Data Name="SubjectLogonId">0x0</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName">Administrator</Data>
    <Data Name="TargetDomainName">HOUSTONLQ</Data>
    <Data Name="Status">0xc000035b</Data>
    <Data Name="FailureReason">%%2304</Data>
    <Data Name="SubStatus">0x0</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">
    </Data>
    <Data Name="AuthenticationPackageName">NTLM</Data>
    <Data Name="WorkstationName">MI-SWACO3</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x0</Data>
    <Data Name="ProcessName">-</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>
</EventData>
</Event>
The firewall is OFF in both client and server.
I saw a similar question and the answer is related to firewall which is not may case.

Hi Mario,
According to your description, when you try to access the Report Manager in another client, a login dialog prompt. After typing a valid username and password 3 times, a blank page displays.
Generally, the issue is always caused by the Report Server is configured to use Kerberos authentication, while the Service Principal Name(SPN) is not configured correctly. To fix this issue, please refer to the following methods:
Register an SPN for the Report Server service under the domain user account.
Change the service account to run under a built-in account such as Network Service.
Remove RSWindowsNegotiate and ensure RSWindowsNTLM is specified in the rsreportserver.config file.
Besides, the issue can also be caused by the Internet Explorer (IE) didn't pass the user's credential to the Report Server automatically or the IE is not Windows Integrated enabled. For more detail steps about how to address this issue, please refer to the
following steps:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/184c4f6c-b292-4f9a-beca-80b70f4392fe/report-manager-prompts-3-or-4-times-for-usernamepassword-before-letting-users-in?forum=sqlreportingservices
Reference:
Resolving Kerberos Authentication Errors When Connecting to a Report Server
Solving the Reporting Services Login issue in the February CTP of SQL Server 2008
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Unable to list SFTP Directory on windows 2008 r2 server from internet

Hi experts,
I have configured a SFTP on windows 2008 r2 server. And i am using the Filezilla on client machine to connect to SFTP server.
The connection works properly on internal network but it displays error when i connect from internet.
Error: GnuTLS error -53: Error in the push function.
Response: 550 Data channel timed out.
Error: Failed to retrieve directory listing
This machine is publish with public IP and port22. The connection and authorization process gets complete but stops are Directory Listing.
PLease suggest the troublshooting steps..
Let me know if any more info is rquired.

Hi,
Do you also use the Filezilla to configure SFTP server? Since you use Filezilla on client machine to connect to SFTP server, I would suggest you ask for help from Filezilla forums for better and accurate answer.
https://forum.filezilla-project.org/
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Oracle 11g ODAC 11.1.0.6.21 on Windows 2008 Standard server gives TNS error

Hi,
I have Oracle 11g ODAC 11.1.0.6.21 installed on my Application server that has 32 bit Windows 2008 Standard. The Oracle database 10g is installed on another 2008 server. On database server I can connect using SQLPlus. But on application server I cannot connect using ODAC SQLPlus. I have given correct service name in tnsnames.ora file.
Error is ORA-12154 TNS: Listener cannot resolve service name
What's wrong? Is 11.1.0.6.21 not meant for Windows 2008? I did not get any errors while installing.
This 11.1.0.6.21 works perfectly for me on XP machine.
I have browsed this forum but not getting clear steps to peform.
Can someone guide me what is needed?
Thanks
Shrini

Hi,
The request to connect from the client is reaching the server but it seems the parsing of the service name is either wrong or the information is correct. Here are a couple of suggestions.
If you have a good known set of sqlnet.ora and tnsnames.ora files on another client where the same connection descriptor works, then backup the curreny client network config files and copy the good known files to the Windows 2008 web server where you see the error. Make sure you recycle the worker processes once the files have been copied.
Try to connect via Ezconnect and by pass the config files to see if you get the same error.
//hostname:port/servicenameofdb
where hostname is the machine where the target database is running
port is the port on the DB machine where the tns listener is running and listening
service name is the service name of the target DB
Use this syntax in the connect string box when attempting to connect from SQL PLUS out of the ODAC home.
You can also run lsnrctl utility on the server and vertify there is a handler for the service name or instance that is the target,
HTH
Jenny B.

Cannot TYPE in Windows 2008 remotre server.

I cannot TYPE in Windows 2008 remotre server.
I can open, close, save and ctrl+alt+delete to open the task manager, but that's it because I cannot type.
When I close the remote connection everything else works just fine.

Hi Amanda,
In addition, you can also try to update RDP edition and NIC driver on problematic machines to see if it works.
Best Regards,
Amy

Installing CR VS2010 on Windows 2008 Core Server

Hello,
We are attempting to re-build our web servers and reduce their footprint. In this effort we have chosen to use Windows 2008 Core Server with all of the web server installation features. In addition we upgraded our application to CR for VS2010 after finding that it supported Windows Server 2008. However, while trying to deploy the MSI packages to the server we are encountering the following error.
MSI PACKAGE
CRRuntime_32bit_13_0_1.msi
ERROR
Error 1904. Modeule C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\pageobjectmodel.dll failed to register. HRESULT -2147024770
SYSTEM INFORMATION
OS Name:                   Microsoft Windows Server 2008 R2 Standard
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Member Server
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:
Product ID:                00477-001-0000421-84205
Original Install Date:     4/27/2011, 10:12:31 AM
System Boot Time:          9/27/2011, 9:47:41 AM
System Manufacturer:       Microsoft Corporation
System Model:              Virtual Machine
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 44 Stepping 2 GenuineInt
el ~3058 Mhz
BIOS Version:              American Megatrends Inc. 090004 , 3/19/2009
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume4
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC-08:00) Pacific Time (US & Canada)
Total Physical Memory:     1,536 MB
Available Physical Memory: 1,031 MB
Virtual Memory: Max Size: 3,840 MB
Virtual Memory: Available: 3,316 MB
Virtual Memory: In Use:    524 MB
Hotfix(s):                 32 Hotfix(s) Installed.
                           [01]: KB2425227
                           [02]: KB2446710
                           [03]: KB2476490
                           [04]: KB2478662
                           [05]: KB2503665
                           [06]: KB2506014
                           [07]: KB2506212
                           [08]: KB2506223
                           [09]: KB2507618
                           [10]: KB2507938
                           [11]: KB2508429
                           [12]: KB2509553
                           [13]: KB2510531
                           [14]: KB2511455
                           [15]: KB2518869
                           [16]: KB2524375
                           [17]: KB2525694
                           [18]: KB2533552
                           [19]: KB2534366
                           [20]: KB2536275
                           [21]: KB2536276
                           [22]: KB2539635
                           [23]: KB2552343
                           [24]: KB2555917
                           [25]: KB2556532
                           [26]: KB2560656
                           [27]: KB2563894
                           [28]: KB2567680
                           [29]: KB2570791
                           [30]: KB2570947
                           [31]: KB2616676
                           [32]: KB976902
INSTALLED PACKAGES
Name=Microsoft ASP.NET 2.0 AJAX Extensions 1.0
Name=SolarWinds Log Forwarder for Windows
Name=Microsoft Visual C++ 2005 Redistributable
Name=Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022
Name=Microsoft .NET Framework 4 Extended
Name=Microsoft .NET Framework 4 Client Profile
Any insight you can provide on the issue would be appreciated.
Thanks,
Phil

The DLLS that fail to register are:
pageobjectmodel.dll
reportrenderer.dll
PageObjectModel.dll is missing the following dependencies:
MSVCR80.DLL
OLEDLG.DLL
DEVMGR.DLL
EFSADU.DLL
NETPLWIZ.DLL
RASAPI32.DLL
RASDLG.DLL
SHDOCVW.DLL
TAPI32.DLL
ReportRenderer.dll is missing the following dependencies:
MSVCR80.DLL
OLEDLG.DLL
DEVMGR.DLL
EFSADU.DLL
NETPLWIZ.DLL
RASAPI32.DLL
RASDLG.DLL
SHDOCVW.DLL
TAPI32.DLL
If I ignore the registration errors the installer completes. When I run my application I get the following error:
The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception. >>> Could not load file or assembly 'CrystalDecisions.ReportAppServer.CommLayer, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
Do we need to run the full version of Windows Server 2008 for this to work? I have installed the required VC++ run-time dependencies and still no luck.

Windows 2008 Terminal Server issue after swapping modem/router

Hi, I have a problem I just can't crack.
Windows 2008 Terminal Server, all patched and up to date. The IP Address is 192.168.1.11 (on a teamed intel controller). Terminal services enabled and working ok.
TP-Link Modem 192.168.1.1, RDP Port forwarded ok.
Set the Windows gateway to 192.168.1.1 and external access to RDP is not a problem.
We had some modem speed issues, so we got a much faster connection, but it can't be used for incoming RDP, so left the TP-Link in place. So added a 3G modem at 192.168.1.5 and set that as the gateway.
External RDP access still works perfectly, and now users have much faster internet.
The TP-Link is giving some reliability issues, so I swapped it over for another modem, a Billion modem. Same 192.168.1.1 IP address, same port forwarding. External RDP access is no longer possible.
Swap back to the TP-Link and everything is fine. Test the modem on another site, everything works as expected.
If I set the gateway on the terminal server to 192.168.1.1 with the Billion attached then external RDP access is no problem. If I set it to 192.168.1.5 then it stops working again.
I tried with a new TP-Link modem of the same model with exactly the same settings and this also had the same problem. External RDP access will only work the existing TP-Link modem, which is a problem as the modem appears to be faulty.
It's almost like it hasn't worked out that it's a new network, and when Windows does that it seems to lock down RDP. That is only my assumption from experience of moving computers to new networks and RDP won't work until windows prompts you with the new
network screen to select home, office or public.
Has anyone experienced anything like this before or can shed some light on the problem?
Thanks.

Hi,
How is the issue going now? Is there any update?
Thanks.
Jeremy Wu
TechNet Community Support

Slowness when connecting to RemoteApp configured in Windows 2008 R2 Server using RDP file

Similar Messages

Maybe you are looking for