Problem with remote connections and error 1326

  • Hello,

    I recently set a new server. I have 3-05 named instances on it (all working fine and dandy) and a new 08 default instance on it. I can connect to the 08 instance locally but cannot hit it remotely.

    I have enabled remote connections and I do NOT have a firewall set up. It does accept named pipes as well too. As far I as I can tell, everything in config manager is the same for the all the instances.

    I am trying to connect to this server (which is on a different domain, same network) that is in a data center from my office computer and keep getting the awesome "provider: Named Pipes Provider, error:40 - could not open a connection to SQL SErver)(Microsoft SQL Server, Error: 1326)

    I even opened the port up on the firewall that is turned off. Same error.

    Oh yea, I CAN connect to all the 05 named instances. No problems there. Only with this 08 instance.

    Ideas?

  • Turns out I did set up the instance correctly. I RDCed into the staging server on the same domain and was able to hit the default instance.

    I am guessing it has to do with something with my desktop being on a different domain as the server.

    I looked up as much as I can on this with little luck. Any help would be great.

  • what port. are you mentioning port number in connection string.

    also try this. instead of server name uset this

    ipaddress,port number

    or

    instance name,port number.

    make sure you setup port static many ppl leave it as dynamic on sql 2005 and 2008. go to configuration manager and change it to all ip = lets say 50000

    you have to recycle sql server services after it and then try to connect again.

    :crazy: :alien:

    Umar Iqbal

  • Sorry, I should have mentioned it before.

    I have tried hitting it via IP (and port) with no luck.

    I have tried static and dynamic ports. I am able to telnet through the port that it is set up as but can't remote into the machine.

    If you research error 1326 it says that it isn't a SQL error but a network error. I am having the IT Networking guys look at the issue but am also tapping my resources for information as well.

    Thanks.

  • try ping from your machine.

    just a stupid idea but make sure your id is in sql server.

    you can try one thing. try connecting osql from your machine

    :crazy: :alien:

    Umar Iqbal

Viewing 5 posts - 1 through 4 (of 4 total)

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