Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Robwhittaker
Yak Posting Veteran
85 Posts |
 Posted - 2002-11-25 : 08:20:29
|
| Hi, we deploy sqlserver over a citrix server, client/server network (does that make sense) running windows 2000.I'm logged on to sqlserver 2000 as SA, using password authentication, and tried to set up my windows 2000 login as a sqlserver login, using enterprise manager.I hit the browse button and picked my userid off of the list that came up for the network domain, but when I tried to save this login I got the following message error 15401: Windows NT domain/user not found. Am I missing something somewhere, do I need a specific type of access on the windows 2000 network to do this?Rob |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-11-25 : 08:29:32
|
| I believe that SQL Server will be authenticating to the Citrix server, not the Citrix client. I'm sure there is a way to pass the client authentication to SQL Server, but you'll have to talk to the Citrix admin about how that needs to be set up.Client/server applications like SQL Server are actually fairly poor candidates for use with Citrix; unless you're absolutely required to access SQL Server that way, you should consider dumping the Citrix client and connect to SQL Server directly. And you can forget developing useful database apps that need to connect via Citrix; if they work at all, the performance will blow.<edit> CLARIFY: if the application is written to access SQL Server directly, then the app itself can be run via Citrix and it will perform as if it was run directly on the client machine. </edit>Edited by - robvolk on 11/25/2002 08:34:42 |
 |
|
|
Robwhittaker
Yak Posting Veteran
85 Posts |
Posted - 2002-11-25 : 08:35:21
|
| It's really just for our developers, to write sql queiries etc through query analyser. (Their apps wont be running like that) We'd rather just stick them all in to a developer group and not have to worry about managing there accesses individually. |
|
|
|
|
|
|
|
|
Setting up windows 2000 authentication