dcsimg
Page 2 of 3 FirstFirst 123 LastLast
Results 16 to 30 of 34

Thread: Probs in connection

  1. #16
    Join Date
    Sep 2002
    Posts
    5,938
    Ya, you are right. Is the problem on all client machines or just some of them?

  2. #17
    Join Date
    Oct 2002
    Posts
    123
    actually it is on client machines which are not in this building (where the server is located)!!
    everyone in this building can connect...

  3. #18
    Join Date
    Sep 2002
    Posts
    5,938
    What's network link between buildings? Blocked any port or traffic on the network?

  4. #19
    Join Date
    Oct 2002
    Posts
    123
    I will check with my network people… & see if any port is blocked.

    Is there any way to check what port the client is opening (when set as dynamically determine port) ? Then we can check to see if that particular port is blocked…
    Again, since it is dynamically determined – cant the port number be any number over 1024 & it can keep changing too?

  5. #20
    Join Date
    Sep 2002
    Posts
    5,938
    The port 1434 has to be open when client talk to sql server via dynamic port number.

  6. #21
    Join Date
    Oct 2002
    Posts
    123
    yes, thats what i read in BOL too...
    Default instances of SQL Server use TCP port 1433 by default. Named instances, however, dynamically assign an unused TCP port number the first time the instance is started. The named instance can also dynamically change it's TCP port address on a subsequent startup if the original TCP port number is being used by another application. SQL Server only dynamically changes to an unused TCP port if the port it is currently listening on was dynamically selected. That is, if the port was statically selected (manually), SQL Server will display an error and continue to listen on other ports. It is unlikely another application would attempt to use 1433 since that port is registered as a well-known address for SQL Server.

    When using a named instance of SQL Server with a firewall, use the Server Network Utility to configure the named instance to listen on a specific TCP port. You must pick a TCP port that is not used by another application running on the same computer or cluster. For a list of well-known ports registered for use by various applications, see http://www.iana.org.

    Have the network administrator configure the firewall to forward the IP address and TCP port the instance of SQL Server is listening on (using either 1433 for a default instance, or the TCP port you configured a named instance to listen on). Also configure the firewall to forward requests for UDP port 1434 on the same IP address. SQL Server 2000 uses UDP port 1434 to establish communications links from applications.

    For example, consider a computer running one default instance and two named instances of SQL Server. The computer is configured such that the network addresses that the three instances listen on all have the same IP address. The default instance would listen on TCP port 1433, one named instance could be assigned TCP port 1434, and the other named instance TCP port 1954. You would then configure the firewall to forward network requests for UDP port 1434 and TCP ports 1433, 1434, and 1954 on that IP address.

  7. #22
    Join Date
    Sep 2002
    Posts
    5,938
    No, don't use port 1434 since it's management port used by sql2k.

  8. #23
    Join Date
    Oct 2002
    Posts
    123
    you mean not to have a named instance on port 1434 right?
    but 1434 should be open on the server side right?

    but then again i read this article
    http://www.sqlmag.com/Articles/Index...ticleID=39447&

    & i got all confused again.

    Also,Microsoft posted this article in May:
    http://www.microsoft.com/sql/techinf...n/port1434.asp
    And this one in July:
    http://www.microsoft.com/technet/tre...n/MS02-039.asp
    so what do i interpret of this ? is still a risk to keep port 1434 open (after the patch available from MS)?

  9. #24
    Join Date
    Sep 2002
    Posts
    5,938
    That's right, have to open port 1434 on your network if you use dynamic port for named instance.

  10. #25
    Join Date
    Oct 2002
    Posts
    123
    okies... thanks a bunch for all your help !

  11. #26
    Join Date
    Oct 2002
    Posts
    123
    ok port 1434 is now open for those clients.. but they still cannot connect (

  12. #27
    Join Date
    Sep 2002
    Posts
    5,938
    Then which port the instance is listening on?

  13. #28
    Join Date
    Oct 2002
    Posts
    123
    Sorry for the late reply…
    In the Server Network Utility, default port is set to 1433…should this be changed?

  14. #29
    Join Date
    Sep 2002
    Posts
    5,938
    That fine, but ensure only one instance uses that number. Each instance on the server should use different port number.

  15. #30
    Join Date
    Oct 2002
    Posts
    123
    Yes only 1 instance is using that port….

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •