When connecting to sql 2000 Enterprise manager opens multiple ports.
For example
Proto Local Address Foreign Address State
TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
How can I force sql to connect only at 1433 or other single port. I facts
is there such posibility?
Hi -
If you analyze the entries in the SQL Server error log file, you can verify
that the instance of SQL Server is listening on the correct IP address and on
the correct port. By default, a default instance of SQL Server listens on the
port 1433. You can also use Server Network Utility to verify the protocol
settings for SQL Server and to change the properties in SQL Server, including
the protocols that can connect to SQL Server and the ports that can be used.
For more information about using Server Network Utility, see the "SQL Server
Network Utility" topic in SQL Server Books Online.
Sometimes, SQL Server 2000 may not bind to port 1433 or any other specified
port. This problem may occur if the port is being used by another application
or if you are trying to connect by using an IP address that is not correct.
Therefore, the TCP/IP connections to SQL Server may not be successful and you
may receive the following error message in the SQL Server error log file:
2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433.
Please check the below link :
http://support.microsoft.com/default.aspx?kbid=307197
Let me know if it helps you.
"Radin" wrote:
> When connecting to sql 2000 Enterprise manager opens multiple ports.
> For example
> Proto Local Address Foreign Address State
> TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
> TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
> TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
> How can I force sql to connect only at 1433 or other single port. I facts
> is there such posibility?
>
Showing posts with label exampleproto. Show all posts
Showing posts with label exampleproto. Show all posts
Sunday, 11 March 2012
Connect at only One port
Connect at only One port
When connecting to sql 2000 Enterprise manager opens multiple ports.
For example
Proto Local Address Foreign Address State
TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
How can I force sql to connect only at 1433 or other single port. I facts
is there such posibility?Hi -
If you analyze the entries in the SQL Server error log file, you can verify
that the instance of SQL Server is listening on the correct IP address and o
n
the correct port. By default, a default instance of SQL Server listens on th
e
port 1433. You can also use Server Network Utility to verify the protocol
settings for SQL Server and to change the properties in SQL Server, includin
g
the protocols that can connect to SQL Server and the ports that can be used.
For more information about using Server Network Utility, see the "SQL Server
Network Utility" topic in SQL Server Books Online.
Sometimes, SQL Server 2000 may not bind to port 1433 or any other specified
port. This problem may occur if the port is being used by another applicatio
n
or if you are trying to connect by using an IP address that is not correct.
Therefore, the TCP/IP connections to SQL Server may not be successful and yo
u
may receive the following error message in the SQL Server error log file:
2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433
.
Please check the below link :
http://support.microsoft.com/default.aspx?kbid=307197
Let me know if it helps you.
"Radin" wrote:
> When connecting to sql 2000 Enterprise manager opens multiple ports.
> For example
> Proto Local Address Foreign Address State
> TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
> TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
> TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
> How can I force sql to connect only at 1433 or other single port. I facts
> is there such posibility?
>
For example
Proto Local Address Foreign Address State
TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
How can I force sql to connect only at 1433 or other single port. I facts
is there such posibility?Hi -
If you analyze the entries in the SQL Server error log file, you can verify
that the instance of SQL Server is listening on the correct IP address and o
n
the correct port. By default, a default instance of SQL Server listens on th
e
port 1433. You can also use Server Network Utility to verify the protocol
settings for SQL Server and to change the properties in SQL Server, includin
g
the protocols that can connect to SQL Server and the ports that can be used.
For more information about using Server Network Utility, see the "SQL Server
Network Utility" topic in SQL Server Books Online.
Sometimes, SQL Server 2000 may not bind to port 1433 or any other specified
port. This problem may occur if the port is being used by another applicatio
n
or if you are trying to connect by using an IP address that is not correct.
Therefore, the TCP/IP connections to SQL Server may not be successful and yo
u
may receive the following error message in the SQL Server error log file:
2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433
.
Please check the below link :
http://support.microsoft.com/default.aspx?kbid=307197
Let me know if it helps you.
"Radin" wrote:
> When connecting to sql 2000 Enterprise manager opens multiple ports.
> For example
> Proto Local Address Foreign Address State
> TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
> TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
> TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
> How can I force sql to connect only at 1433 or other single port. I facts
> is there such posibility?
>
Subscribe to:
Posts (Atom)