Questions[linked-server](server)

We're trying to access Foxpro file-based database files via MSSQL Server's linked server feature, using Foxpro ODBC driver.

For this, we've

• installed the latest Foxpro ODBC Driver from Microsoft,
• made a System DSN which is using this driver
• chose the "Visual FoxPro database (.DBC)" option under Database type, instead of "Free table directory"
• specified the path to our dbc file (on local machine)
• installed MSSQL Server 2008 R2 Express
• installed MSSQL Server Management Studio 2008
• tried to create a new linked server by using a GUI wizard like this:

But the last step never completes (Executing is displayed forever). When Management Studio is forcibly closed and restarted the new linked server is there but only contains Catalogues subitem. If we try to expand it, Management Studio goes into loop yet again.

I'm trying to set up the following scenario. I have 3 servers, they are all in same domain.

• Server A has web application which runs under (domain) service account, dom\web.
• Server B has instance of SQL Server 2008 R2 which runs under (domain) service account, dom\sql.
• Server C has instance of SQL Server 2008 R2 which runs under (domain) service account, dom\sql.

Servers B and C are in SQL Cluster. Instances of B and C are linked servers.

When I run SQL Server Management Studio from A and connect to B using my domain account (dom\usr) I try to execute the query which selects data from B and C and it works.

When I try web application which tries the same I get the error:

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

I see that connection in SQL has auth_scheme KERBEROS for user dom\web so it's not NTLM.

Also, dom\web domain account doesn't have selected "account is sensitive and cannot be delegated" option in AD.

I also think that SPN is correctly set up because double hop wouldn't work in the first case.

This is error on server C:

Source Logon

Message Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 10.65.10.53]

Source Logon

Message Error: 18456, Severity: 14, State: 11.

As per standard procedure we've been using for years for previous versions of both Oracle and SQL Server, I have installed Oracle's latest ODAC package, which includes the Oracle OLE driver onto our new SQL Server 2008 R2 x64 nodes. I have done the recommended system reboot, but OraOLEDB.Oracle does not show in the Linked Servers\Providers node in SSMS. The only difference between this installation and previous SQL Server installations is that I am now using SQL Server x64 (on Windows 2008 R2). Should this make any difference?

Note that I am able to connect to Oracle servers using SQL*Plus from the SQL Server nodes directly. The only thing I am missing is that Provider. Anyone know what I am missing? There are many posts around the web, but there seems to be a lot of confusion and outdated links to Oracle's download page.

The ONLY thing I need to be able to do is create a linked server to Oracle, and run select queries against it. I don't need to do anything through Visual Studio.

I have a Linked Server which was made using SQL Server Management Studio 2008.

If the linked server destination changes, I will have to change the properties of it to direct to the right place.

But I cannot - there is no edit option!

Am i missing something, or can Linked Servers not be altered?

Background I have two environments, TEST and STAGE. I use Microsoft Distributed Transaction Coordinator (MS DTC) with two linked 2008 SQL servers. A SQL job runs every couple of minutes and everything works fine on TEST. The SQL job does not run on STAGE. The only difference I have been able to pinpoint is that ping resolves to an IPv6 address on STAGE, but an IPV4 address on TEST. I suspect that MS DTC does not support IPv6.

Question I have three computers: testServer, stageServer, and productionServer. If I ping productionServer from testServer I get a reply from 192.168.1.2. If I ping productionServer from stageServer I get a reply from a long IPv6 address. Both testServer and stageServer have IPv6 and IPv4 enabled. Both testServer and stageServer use the same DNS servers, listed in the same order in the DNS tab. Why are the ping resolutions of IP's different?

TEST nslookup:
C:\Computer\me>nslookup
Default Server: dnsServer.domain.net
Address: 192.168.1.47

> productionServer
Server: dnsServer.domain.net
Address: 192.168.1.47

Name: productionServer.domain.net
Address: 192.168.1.2
>

STAGE nslookup:
C:\Computer\me>nslookup
Default Server: dnsServer.domain.net
Address: 192.168.1.47

> productionServer
Server: dnsServer.domain.net
Address: 192.168.1.47

** dnsServer.domain.net can't find productionServer: Server failed
>