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
