named pipes connect error

  • Inherited an estate.

    Just trying to logon to one of the SQL servers.  It's not a named instance.  Trying to connect via SSMS & osql (local to the SQL box) - connecting with either:

    SSMS (windows user onto hostname, hostname,1433 or hostname\mssqlserver).  It's windows auth only.

    osql -S. -E

    osql -S hostname -E

    osql -S hostname\mssqlserver -E

    osql -S hostname\mssqlserver -U x -P x (just to try and get a logon failure in the log but no joy).

    Server is up and running, can see the service & the error log.

    Port is default, 1433. Named pipes is enabled as is TCP/IP.

    Anything else to try or look at?

    Thank you.

     

     

     

     

  • what is the actual error and error message you are receiving ?

     

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • Oosh, my mistake.  It was a SQL cluster with a virtual SQL server name.  I'll leave it here in case there are any other stressed out dummies.  Thanks for answering Johan.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply