Post reply

Not able to connect SQL Server 2000 remotely.

  • January 8, 2010 at 1:30 am

    #1100737

    How are you connecting. Windows or SQL authentication.. Does the user have relevant permissions?

    blog: http://sarveshsingh.comTwitter: @sarveshsing

  • January 8, 2010 at 1:53 am

    #1100743

    Connecting with SQL Authentication.

    Account : sa account and sysadmin account.

    Cheers,
    - Win.

    " Have a great day "

  • January 8, 2010 at 2:31 am

    #1100752

    See if this help:

    http://support.microsoft.com/kb/328306

    blog: http://sarveshsingh.comTwitter: @sarveshsing

  • January 8, 2010 at 3:19 am

    #1100761

    Gone through already

    Cheers,
    - Win.

    " Have a great day "

  • January 8, 2010 at 12:04 pm

    #1101130

    Try adding an alias woth the port number

    or

    try using the servername:port in QA or your EM registration

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • January 8, 2010 at 9:59 pm

    #1101304

    Did you try using a command line tool instead to connect, like: osql -E -S tcp:servername\instancename?

    Also, under network configuration-->TCP/ip, did you check and see if it is holding the latest IP addresses of the server?

  • January 8, 2010 at 10:17 pm

    #1101306

    Did you try rebooting server?

    Sometimes starting and stopping sql server services wont help.

  • January 10, 2010 at 9:40 pm

    #1101605

    Tried already.

    Added alias with the port, but it still the same issue.

    Cheers,
    - Win.

    " Have a great day "

  • January 10, 2010 at 9:42 pm

    #1101606

    Yes done.

    Rebooted, twice. Not able to figure out. Iam able to connect my local instance in the server. Still, the server instance is not able to in remote.

    Cheers,
    - Win.

    " Have a great day "

  • January 10, 2010 at 10:22 pm

    #1101613

    Did you try using a command line tool instead to connect, like: osql -E -S tcp:servername\instancename?

    Also, under network configuration-->TCP/ip, did you check and see if it is holding the latest IP addresses of the server?

    _______________________________________________________________________________

    When i tried using command tool : osql -E -S tcp:servername\instancename , remotely.

    1,

    It trown an error :

    [DBNETLIB]Invalid connection.

    [DBNETLIB]ConnectionOpen (ParseConnectParams()).

    2,

    In the server:

    [SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance

    Specified [xFFFFFFFF].

    [SQL Native Client]Login timeout expired

    [SQL Native Client]An error has occurred while establishing a connection to

    the server. When connecting to SQL Server 2005, this failure may be caused by

    the fact that under the default settings SQL Server does not allow remote

    connections.

    Here it shows as SQL Server 2005 and the command ran is for 2000 instance with the port of sql 2000.

    Confused !!!

    ____________________________________________________________________________

    Yes

    Under network connections its using latest IP.

    _____________________________________________________________________________

    One small query:

    Under SQL Server Network Utility , instance Port number : 3759

    Under SQL Cleint network Utility TCP/IP : 1433

    and there "enable shared memory protocal" is enabled.

    Any other changes t be done ?

    Am i missing any settings?

    Cheers,
    - Win.

    " Have a great day "

  • January 10, 2010 at 10:43 pm

    #1101617

    Dears,

    Finally I found one solution to connect the instance remotely.

    "servername\Instance,portnumber"

    It worked fine.

    Thanks for all of your support.

    Cheers,
    - Win.

    " Have a great day "

Viewing 11 posts - 16 through 25 (of 25 total)

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