How to connect to Windows 2008 VPN server with certificate support

Unfortunatelly if I select any Windows 2008 server compatible protocol (PPTP, L2TP) I cannot select PKI certificate, its only available for Cisco VPN. Yet my company has 1000 laptops and utilizing Windows 2008 Server for VPN (Cisco is too expensive and unnecessary because VPN is part of Windows Server). PKI certificate is required for connection security.
Any plans to enable certificates for PPTP or L2TP in 2.1 firmware? Even better would be to add SSTP protocol with certificate support, because it takes only one standard TCP connection (https) per user (uses least possible NAT resources for heavy loaded NATed WiFi spots). Also in some public places https is the only option to connect as PPTP and L2TP are filtered.

Hi Shahzad,
>>how to connect sql server 2008 r2 sp2 with visual studio 2013 ultimate?
Based on your issue, if you wan to connect the sql server 2008 r2 sp2 from VS2013 IDE. I suggest you can try the Ammar and darnold924's suggestion to check your issue.
In addition, I suggest you can also refer the following steps to connect the sql server 2008 r2 sp2 with visual studio 2013 ultimate.
Step1: I suggest you can go to VIEW->SQL Server Object Explorer->Right click SQL Server->Add SQL Server.
Step2: After you connect the SQL Server 2008 r2 sp2 fine, I suggest you can go to VIEW->Server Explorer-> right click the Data Connection->Add Connection.
And then you can create the connect string in the Add Connection dialog box.
Hope it help you!
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.
Click
HERE to participate the survey.

Similar Messages

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

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

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.

SAP support Windows 2008 x64 server

Hi,
SAP 2007 supports the Windows 2008 x64 server? If support, what I need to do to run the sap add on at this Server.
Please give me any suggestiong.
Thanks and regards,
Lei Nandar Myint

Hi,
You may check this link: https://websmp203.sap-ag.de/smb/sbo/platforms (S-Number logon)
Regards, Yatsea

Control key not working on MB Pro while connected to windows 2008 server through 2x client. Any ideas? Works on windows through parallels.

Control key not working on MB Pro while connected to windows 2008 server through 2x client. Any ideas? Works on windows XP through parallels desktop.

Hello...
It seems I got it fixed!! I had been trying the Fixit tool from
http://support.microsoft.com/kb/306759 while typing up there :))))
This tool is for changing RDP port but running it fixed my problem (I kept the port 3389 intact)!!
Hope it helps someone.

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

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

Add Windows 2008 Terminal Server to RWW/RWA

I would like to add our Windows 2008 Terminal Server (not R2) to RWW in Windows 2012R2 Essentials. The connect computer wizard did not work on the Windows 2008 server, returning Win32 error.
How do I add the 2008 TS to the devices listing in RWW without using the connector wizard (as it does not work). The Windows 2008 server has been join to the same domain manually.

You cant add it as a tile device in the way you could in SBS 2011 Standard.
You can create an RDP file, and save that so it is accessible via the RWA then add a link to the RWA to that file.
You may need to tweak IIS to allow .rdp files.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

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

BO XI 3.1 SP2 error while installing in Windows 2008 ENT Server 32 Bit

Hi
We have windows 2008 enterprise edition 32 Bit SP2 , While installing BO 3.1 SP2 we are getting the following error.
"Some files could not be created.
Please close all applications, reboot Windows and restart this installation."
1.we do have enough space as well as we are installing it through administrator account.
2.I increase the virtual memory size from 2 GB to 4 GB, still same error.
3.we downloaded the software in two diffrent machines. We tried extracting the "exe" file in two machine but still getting the same error.
4.We dont have any firewall connected and windows firewall is off.
Is there BO 3.1 Sp2 is available for windows 2008 ent server 32-Bit?
Because In the download site there is Windows Server on IA32 32-bit.
is it the correct version?
Please help us to solve this problem
Thanks

We have opened a ticket for this. After subsequent discussion with the forum support person we have installed BO Enterprise 3.1 SP2 fixed pack 2.5 on the server (Windows Server 2008 SP2). On the client side, we have also installed BO Enterprise 3.1 SP2 fixed pack 2.5 and Live Office SP2 fixed pack 2.5.
Once we tried to use the Web Intelligence document based on OLAP Universe in excel through Live Office it gives the following error.
"Failed to get the document information. (LO 26315) A database error occured. The database error text is: Failed to set properties (The component Microsoft® OLE DB Provider for Analysis Services returned server error (Database 'Sales' does not exist.)). (WIS 10901)(6315)".

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.

SAPSprint installation on Windows 2008 R2 Server 64-bit

Dear Gurus,
as we change our print server to Windows 2008 R2 Server 64-bit I need to install SAPSprint for SAP printing with connection type 'S' out of a NW7.0 based system on HP-UX.
Till now we used SAPlpd on a 32-bit Windows Server......
1) Do I simply need to install the xSPrint.exe or can this happen only in combination with the whole SAPGui?
2) According to note 66971 for Windows 2008 R2 Server 64-bit only SAPGui 7.20 is supported.
Does this mean that I also have to use SAPSprint release 7.20 or can I use any other release as well.
On our Windows clients we run SAPGui 7.10.
Is there any correlation between the SAPGui running on the clients and the SAPGui / SAPSprint release running on the print server or can I simply install the highest SAPSprint release 7.20 on the print server to be sure that it will work with WK8 R2 64-bit?
I hope I could explain my problem and I am looking forward to your reply.
Thanks a lot in advance!
Günter

Dear Günter.
Your question is spread over some different areas. Let me point out some tracks to follow:
There is only a 32-bit version of SAPSprint but that one works also under 64-bit; please refer to SAP note 894444.
Regarding SAPgui, in general it is recommended to have the last version as it is downwards-compatible with older versions.
But specially, let me highlight that Windows 2008 R2 is not yet listed in the PAM - and hence not yet supported. The technical prerequisites are met (with a special kernel patch) but not all software is released.
In fact, and just to provide you further details it is not possible to expect the 710 products released for Windows Server 2008 R2 before around four weeks; 700 products will be released even after 710.
See SAP note 1383873 ("Windows Server 2008 R2 Support").
You can be always up to date with the latest Windows news at:
--> Support of Microsoft Windows Server 2008 R2
Cheers!

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

How to connect to Windows 2008 VPN server with certificate support

Similar Messages

Maybe you are looking for