Re: Server not listening on 1433
- From: "Shri.DBA" <tbalajiprabhu@xxxxxxxxxxx>
- Date: Fri, 26 Aug 2005 23:06:54 +0530
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
"Greg New" <Greg New@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EBEC2E41-F72E-43CD-BCD2-28B8E7284128@xxxxxxxxxxxxxxxx
> 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
.
- Follow-Ups:
- Re: Server not listening on 1433
- From: Greg New
- Re: Server not listening on 1433
- References:
- Server not listening on 1433
- From: Greg New
- Server not listening on 1433
- Prev by Date: Server not listening on 1433
- Next by Date: Re: Server not listening on 1433
- Previous by thread: Server not listening on 1433
- Next by thread: Re: Server not listening on 1433
- Index(es):
Relevant Pages
|
Loading