Note When connecting to a SQL Server running on Windows NT using Named Pipes, the user must have permission to connect to the Windows NT Named Pipes IPC, \\<computername>\IPC$. If the user does not have permission to connect, it is not possible to connect to SQL Server using Named Pipes unless either the Windows NT guest account on the computer is enabled (disabled by default), or the permission "access this computer from the network" is granted to everyone.
Well I did not touch anything, however, I do not grant permission for everyone to access this computer from the network nor do I have any guest account enabled. So how in the heck was this running on named pipes in the first place. According to the on-line books, it should not have been possible. Wait a minute (brain fart). If I read this closely, it says "If the user does not have permission to connect" they can't "unless" there is a guest account or access this computer from the network yada yada.
So how come do my users suddenly not have permission via named pipe? And if that is the case, how do I change the permissions back. I am all over SQL and can't find where named pipe permissions are changed. I did not even know that you can have separate permissions via TCP/IP or named pipes.
And which is better anyway? I ran in multi for quite a while ago and I remember changing it to named pipes, but don't remember why...
I appreciate any feedback here.
Thanks!!!!
did the patch close ports needed to connect to you db server on machine 2?
1st machine Windows 2000 server IIS 5 Tango 2000 all patches, sps and fixes
2nd machine Windows 2000 server MSQL 7 all patches, sps and fixes
Something strange just happened to me. I applied the latest critical update to 2nd machine and rebooted. Suddenly all db queries resulted in "named pipes access denied". I changes the client configuration in MSQL to TCP/IP connections and switched client configuration in ODBC on 1st machine to the same. Now it works, but the client configuation on 2nd machine shows named pipes as the default and 1st machine shows TCP/IP for odbc.
What gives? Any help appreciated as this is on a production machine.
Which is the better connection anyway, I remember this discussion in the past but would like to get it right.
Thanks
-- ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
Bill Conlon
To the Point 345 California Avenue Suite 2 Palo Alto, CA 94306
office: 650.327.2175 fax: 650.329.8335 mobile: 650.906.9929 e-mail: mailto:[EMAIL PROTECTED] web: http://www.tothept.com
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
-- ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
