Post reply

connect remort server

  • March 14, 2011 at 4:43 am

    #72073

    Hi,

    I have application server and database server are individual.

    Application server is accessible by everybody in network.while database server is accessible only on application server.

    Database server is not accessible in network.

    now I have an utility that updates some data in my database situated on database server. this utility will run from any client from network.

    I am getting ping of database server through database server's IP Address.

    In this scenario i am not able to connect database. What do i do ?

    I have administrative rights of both servers.

    Thanks:(

  • March 14, 2011 at 8:28 am

    #1298355

    Ensure tcpip port 1433 is only on the firewall.

    Start the SQL Browser service using the Configuration Manager (and ensure 1434 is open).

    If this doesn't help, please post the error message that you are receiving so we can help without guessing.

    Thanks,

    Jim

    Jim Murphy
    http://www.sqlwatchmen.com
    @SQLMurph

  • March 15, 2011 at 10:56 pm

    #1299210

    Hi Jim,

    Thanks for reply

    i saw configuration settings in my sql server, Default TCP/IP port is 1433.

    but i am not able to find 1433 port on firewall.

    i tried the following procedure (from http://support.microsoft.com/kb/308127):

    # Click Start, and then click My Network Places.

    # Under Network Tasks, click View Network Connections. (Or, right-click My Network Places on the desktop, and then click Properties.)

    # Right-click the connection that you use for the Internet, and then click Properties.

    # Click the Advanced tab, and then click Settings.

    Note If the Settings button is unavailable, ICF is not enabled on this connection, and you do not have to open any ports (because they are all already open).

    # Click Add to open a new port.

    # In the Description box, type a friendly name. For example, type File Sharing : Port 445.

    # In the Name or IP address of the computer hosting this service on your network box, type 127.0.0.1.

    Note You can specify the IP address of an internal computer. But you typically will use 127.0.0.1.

    # In the External port and Internal port boxes, type the port number. Generally, this number is the same.

    # Click either TCP or UDP, and then click OK.

    --------------------------------------------------------

    and to confirm that whether port is available or not i tried

    NETSTAT command on dosprompt. but it not showing here in dos.

  • March 15, 2011 at 11:12 pm

    #1299214

    Maybe this is too obvious, but you did ensure that the SQL server is configured to allow remote connections, right? This is in sql server properties on 2008.

    Also, you'd need to ensure a network protocol is enabled, like tcp and not just shared memory. This is in the SQL server configuration tool. From here, if you pick tcpip, you can specify the port to be used. Default is 1433 for a default instance. If a named instance, it could be anything - hence ensuring sqlbrowser is running so the instance and it's probably dynamic port is found properly. You can make a named instance have a static port in the network config area for the tcpip server protocol.

    Then, a netstat run on the server will show if the SQL server is listening on the proper port.

    That's some of the server pieces. For the network itself, use telnet or a port scanner to ensure the client computer can connect to the desired SQL server port (1433 by default). If not, and you have done the above config settings, you likely have a network firewall issue where the firewall device (not the software firewall as part of windows), is blocking the port or filtering the traffic based on IP or Mac address or something. This is a network problem.

    There are lots of articles at Microsoft.com which explain how to configure all of these settings.

    Jim

    Jim Murphy
    http://www.sqlwatchmen.com
    @SQLMurph

  • March 24, 2011 at 3:04 am

    #1302835

    Hi, Jim.

    replying after bit of time. but it was due to my IT (Networking) personnel who is not able to open port.

    is there any other thing to see ? or is there any other way to access my database ?

    :doze:

  • March 24, 2011 at 9:37 am

    #1303064

    A port of some sort is mandatory to be open for one computer to communicate to another; that's how the network works. Therefore, the best port they can open is 1433/1434. If they refuse, you can do a few things.

    Figure out what ports are already open and use one of those. Use the SQL server configuration manager to set the port number for SQL server to listen on. Run the SQL browser service or configure the client connections to use the same port as the server is configured to use.

    Or, the network folks may already allow the far less secure 135-139 and 445 port for general network connectivity. Ironically, some network admins feel that these ports are somehow safer than 1433. If this is the case, you can enable the Named Pipes protocol in the SQL server configuration manager. There are limitations to using this protocol though, like that you must be on the same network to use it. But that may not be a problem for you.

    Jim

    Jim Murphy
    http://www.sqlwatchmen.com
    @SQLMurph

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

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