Dots


I have developed a client server application using SQL Server 2005 Express and VB.Net. I will be distributing it to my customers. I am putting together a System Requirement document. I am wondering what kind of Server (o/s) and network configuration customers need to have. I know they cannot use a pier to pier network setting. What kind of network setting do they need to have Does the server machine need to have a server o/s (such as Win 2003 Server) or is Windows XP fine Any help will be appreciated.




Re: Server/Network Requirement

Andrea Montanari


hi,

actually a peer to peer scenario, that's to say a "workgroup" and not a staight domain controller based network, is ok.. no such a restriction exists.. and a "server" running XP sp2 is ok as well..

as regard network setting... just a traditional network is "required", with a working lan, using all supported network protocols, and you'll be fine using tcp/ip...

regards







Re: Server/Network Requirement

Dots

Thank you for your response. I use Windows Authentication. Do you mean to say it does not require a domain controller based network scenario Doesn¡¯t SQL Server verify the user (client) who tries to access it How can the user security be setup on a Workgroup I am not that familiar with network settings. Any help will be appreciated.






Re: Server/Network Requirement

Andrea Montanari

hi,

SQL Server accepts 2 kinds of authentication, Windows authentication where you tipically require a domain controller and SQL Server only "gets" the actual sid of the connecting login to be matched against the registered logins, and the mixed security authentication, where you can connect via a SQL Server login and you have to provide both login credentials and the corresponding password to be matched against the registered standard SQL Server logins.. so the authentication always is checked..

mixed security is usually used in peer to peer (workgroups) scenario, where no DC is available..

regards