Named Pipes vs TCP/IP in Citrix environment

[CathodeRay]

We have about 20 users that connect remotely to our Great Plains using Remote Desktop and Citrix server. When they log in to Great Plains, the login screen, of course, asks them for the server name... the server name they use is an ODBC that we have set up actually on the Citrix server, and it is defined to use TCP/IP.

However, when we go into Enterprise Manager on the SQL Server, and view Process Info, every one of these remote connections says it is connected via Named Pipes instead of TCP/IP (like our local users are). Named Pipes IS one of the options available on the server-side in SQL's Server Network Utility.

Why would Process Info be saying Named Pipes? Could they be connecting to the SQL Server *prior to* or *outside of* the ODBC server connection that is being prompted for by Great Plains?

 

[Dukester0122]

Let me just clarify your statement, when you go to ODBC Data Source Administrator in your Citrix server and open the DSN then go to Client Configuration. Under Network Libraries its currently setup as TCP/IP not Named Pipes,right?

 

[CathodeRay]

That's correct... but we now have more information.

We solved the problem by simply changing it to Named Pipes, then turning right around and changing it back to TCP/IP.

We wanted to do this during off hours due to the high volume of people connecting throughout the day, so we did it at night, and Bingo, SQL Server started showing the CORRECT configuration of TCP/IP again in its process monitor.

We later learned that the connection between the Citrix server and the SQL server had become disconnected inadvertently a day or two prior, so apparently that whole ODBC definition had gotten hosed.

Thanks for your interest.

 

[Dukester0122]

I thought that's what you need to do first and it worked. Good for you guys.