Posted by Razvan Socol on 12/05/05 21:50

Hi, Erich

An easy solution may be to use the Named Pipes protocol instead of
TCP/IP: run CLICONFG.EXE and make sure that Named Pipes is at the top
of the enabled protocols list (this is one of the solutions described
in KB 811899).

Razvan

[Back to original message]