Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Setup / August 2005

Tip: Looking for answers? Try searching our database.

Server not listening on 1433

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Greg New - 26 Aug 2005 18:01 GMT
Hi All,

Very strange problem here! Installed SQL 2000 on my Windows Server 2003 with
SP1. All went well. Got my DB working and clients connecting fine.

Went to connect a box in the DMZ via ODBC using TCP/IP on 1433 and it failed
to connect. Tried another box on the LAN and that wouldn't connect. Had a
look on the server and it seems that the server isn't listening on 1433
netstat -a

I've checked the Network properties, client network and server network in
SQL and all is set as I would expect it. Nothing else is listening on those
ports. I can connect fine by named pipes but the DB vendor would prefer me to
use TCP/IP.

Has anyone got any ideas? The SQL is SP3. It's a Compaq server that was
rebuilt from scratch only a few days ago.

If a client connects using dynamic ports what would i see when i do a
netstat -a or -b or -an ?

Many thanks,

Greg
Shri.DBA - 26 Aug 2005 18:36 GMT
Hi Greg,

As you doubt, sql server may be listening in a different port. Check SQL
Server error log. SQL Server records in SQL Server error log, to which port
it is listening to...

Regards
Shri.DBA

> Hi All,
>
[quoted text clipped - 20 lines]
>
> Greg
Greg New - 26 Aug 2005 20:23 GMT
Hi,

I found this in the log which makes me think that it's just not listening on
TCP
"SQL server listening on Shared Memory, Named Pipes."
Any ideas?

Thanks for your help.
Cheers,
Greg

> Hi Greg,
>
[quoted text clipped - 33 lines]
> >
> > Greg
Vikram Vamshi - 26 Aug 2005 23:32 GMT
Run the SQL "Server Network utility" (svrnetcn) and make sure that TCP/IP is
in the Enables list of protocols.

Also can you post your errorlog, that would give us some more information
...

hth
Signature

Vikram Vamshi
Database Engineer
Eclipsys Corporation

> Hi,
>
[quoted text clipped - 49 lines]
>> >
>> > Greg
io - 30 Aug 2005 12:01 GMT
DMZ means that you have two firewalls, right? Are they set to allow the port?

Second, do you have a named instance or not? My wild guess here is to enable
multiprotocol, since it listens on all the protocols at hand

> Run the SQL "Server Network utility" (svrnetcn) and make sure that TCP/IP is
> in the Enables list of protocols.
[quoted text clipped - 56 lines]
> >> >
> >> > Greg
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.