$ 0 0 I would run C:\windows\system32\cliconfg.exe and see if somehow a bad alias has been setup .. I ran into something similar a little while back and that was the cause.