Post reply

Remote access to separate versions

  • August 5, 2010 at 9:27 am

    #99349

    Hi,

    I've posted this here but it really relates to both 2000 and 2008. I have a copy of sql2000 on my remote server that I connect to via TCP/IP. So in enterprise manager I can put the IP address of the server in and it connects straight to the default instance.

    However I also have sql 2008 express on there as I want to experiment with migration. I can't figure out how I can connect to the 2008 instance through IP as the IP address and the port on the server connect right into 2000.

    I've looked through the IP settings on both the 2000 server utiility and the configuration manager for 2008 but I cant' see a way to allow connections to both servers through IP.

    Can anyone help?

    Thanks

  • August 5, 2010 at 9:35 am

    #1202864

    You need to reference the named instance in the connection like this: host\instance.

    John Rowan

    ======================================================
    ======================================================
    Forum Etiquette: How to post data/code on a forum to get the best help[/url] - by Jeff Moden

  • August 5, 2010 at 9:41 am

    #1202869

    I've tried that but if I set the 2000 and 2008 servers to the same port and IP, the 2008 server won't even start. It just comes up with event ID 7024:

    The SQL Server (SQLEXPRESS) service terminated with service-specific error 10048 (0x2740).

  • August 5, 2010 at 10:14 am

    #1202905

    You cannot share ports among services. Doesn't matter if it's SQL, IIS, etc. Each service needs it's own port.

    For named instances, they run on another port. The error log will tell you which port it's listening on, but if you don't set a specific port in Configuration Manager, you might get a new port on restart.

    When you connect with server\instance, you send out a 1434UDP packet, and SQL Server responds with a port, and your client then connects to that. If you determine the port, you can connect with

    IP, port

    as in.

    192.168.0.12, 4000

    To connect on port 4000.

  • August 6, 2010 at 1:52 am

    #1203285

    Thanks Steve that worked perfectly. I had a feeling that they wouldn't be able to share the same port but I couldn't figure out how to specifiy the port on the connection.

    I can now connect to both instances remotely.

    Thanks

  • August 6, 2010 at 10:00 am

    #1203643

    Good to hear.

    Note that you can use an FQDN, like "sql.mycompany.com, 4000" or a server name "SalesDBServer, 4000" as well.

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

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