Re: TCP/IP Connection - Can only connect to the 'Dynamic Port'

Tech-Archive recommends: Fix windows errors by optimizing your registry

It may be bad form to reply to ones own post, but I have now been able to
connect to port 1433 via JDBC (and telnet).

To do this, I had to:
- Open SQL Server configuration manager
- Open the TCP/IP Protocol Properties dialog under Network Configuration
- Under IPAll, TCP Port field, add 1433
- Restart SQLEXPRESS

As a further test, I added port 6666 to the TCP Port field and was then able
to connect to port 6666 (JDBC and telnet) even though this port was/is not
defined on the IP1, IP2 definitions given in the initial question.

The following SQL Server Books On Line article helped:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/8e955033-06ef-403f-b813-3d8241b62f1f.htm

Does not make sense to me...

-brad

"brad" wrote:

David,

Thank you for the query. The results show that SQLEXPRESS is NOT listening
on the 1433 (or 1432) port. The results make a messy cut-n-paste, but shows
that two ports are being listened upon:

Dedicated Admin Connection
TSQL Default TCP

Both are started (state_desc = STARTED) and both are marked as dynamic
(is_dynamic_port = 1).

I know the obvious is that I have configured the protocols incorrectly, but
I do not think this is the case.

Using 'SQL Server Configuration Manager' and viewing the 'Protocols For
SQLEXPRESS' show that the ports listed below have properties "Active = Yes"
and "Enabled=Yes". This seems in direct contradiction of the query results.

Thank you for answering.




"David Browne" wrote:


"brad" <brad@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:51CADB6F-BB36-41D9-8A55-F352DD2254E8@xxxxxxxxxxxxxxxx
Hello,

I have TCP/IP enabled as a supported SQLExpress protocol.
There are three Active, Enabled IP addresses defined, and they are:
IP1: The DHCP assigned address on port 1433
IP2: The 'Default' localhost address (127.0.0.1) port 1432 (changed to
this
by me)
IPALL (the dynamic port) currently assigned as 1132.

Using MS JDBC I am failing to connect with either timeout or connection
refused messages EXCEPT when using port 1132.

Using telnet, I am able to connect to ONLY the IPALL port of 1132.


If SQL Server is listening on the port, then you will be able to telnet to
that port. Check the SQL Server logs, or run

select * from sys.tcp_endpoints

To see what addresses and ports SQL Server is listening on. And if you are
connecting directly to a port you shouldn't need the instance name. The
instance name is used by the browser service to find the dynamic port for
you.

David



.

Relevant Pages

  • Re: Telnet port 25
    ... Subject: Telnet port 25 ... is the sole responsibility of the customer and depends on the customer's ... Configuring sendmail 8.11.0 for Anti-Relay ...
    (AIX-L)
  • Re: Suggestion for a lexical (login mode via TCPIP)
    ... Not sure of it is the right one to modify or to add another one, but it would be useful to be able to get information on whether the user us coming in via FTP, TELNET, etc. ... This would also allow a LOGIN.COM to check if someone is coming in through a secure/SSL port for instance. ... For the HP SSH server, it seems to be undefined. ... forget about the possibility of virtual terminals. ...
    (comp.os.vms)
  • Re: Sql Remote Connection issue
    ... Remote access is set to 1. ... Sql Server is listening on 127.0.0.1:1433. ... The above would indicate it's using the default port. ... To verify the connection I'm using telnet to verify communications is ...
    (microsoft.public.sqlserver.connect)
  • Re: Cannot telnet to port 25 from Windows 2003 SBS server to itself
    ... XFOR: Telnet to Port 25 of IMC to Test IMC Communication: ... Microsoft is providing this information as a convenience to you. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: RWW fails from Internet
    ... on port 4125: Connect failed" when you telnet to 4125. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)