Re: SQLCMD fails with login timeout expired.

No Im sure I have the 2000 one selected and why would no protocols be listed
then? since 2005 is listening on tcp 1900.

Im doing a reinstall of SQl2000 to see if that fixes it.

--
Thanks
Morris


"Rick Byham, (MSFT)" wrote:

One possibility - When you open the Server Network Utility, you may be
looking at the SQL Server 2005 instance. In the Instance(s) on this server:
box, select the SQL Server 2000 instance.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"Morris Neuman" <Morris@xxxxxxxxxxxxx> wrote in message
news:E66041B1-DB37-485C-8E9B-F2CC39D69FD6@xxxxxxxxxxxxxxxx
OK that worked for SQl2005. BTW you can't have spaces in the sqlcmd
parameter so its tcp:dell4600c\sqlexpress,1900

But the ques. now is I used the SQL2000 server network utility and on the
General tab there are no protocols listedin either the Disabled or Enabled
protocols. I gues thats why itsnot listening on TCP. How can I fix that
to
get TCP listed and enabled?
--
Thanks
Morris


""Peter YangMSFT]"" wrote:

Hello Morris,

Thank you for your reply and additional information!

From SQL 2000 error log, it's not listening on TCPIP:

2007-07-18 16:02:06.51 server SQL server listening on Shared Memory,
Named Pipes.

From 2005 Express instance log, it listens on port 1900:

2007-07-18 16:06:17.62 Server Server is listening on [ 'any' <ipv4>
1900].
2007-07-18 16:06:17.62 Server Server local connection provider is
ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2007-07-18 16:06:17.62 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2007-07-18 16:06:17.62 Server Server is listening on [ 127.0.0.1
<ipv4> 2107].


I suggest that you try the following sqlcmd command to connect to the SQL
Express instance:

sqlcmd -S tcp: DELL4600C\SQLEXPRESS, 1900

If above command works, please make sure SQL browser service is started
and
running properly.

Also You may want to run SQL Configuration manager if it's installed on
your machine:

Under SQL native client configuration->Client Protocols, and make sure
TCPIP is enabled.

Best Regards,


Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================


This posting is provided "AS IS" with no warranties, and confers no
rights.






.

Relevant Pages

  • RE: SQLCMD fails with login timeout expired.
    ... General tab there are no protocols listedin either the Disabled or Enabled ... I gues thats why itsnot listening on TCP. ... I suggest that you try the following sqlcmd command to connect to the SQL ...
    (microsoft.public.sqlserver.tools)
  • Re: SQLCMD fails with login timeout expired.
    ... One possibility - When you open the Server Network Utility, you may be looking at the SQL Server 2005 instance. ... General tab there are no protocols listedin either the Disabled or Enabled ... I gues thats why itsnot listening on TCP. ...
    (microsoft.public.sqlserver.tools)
  • Re: VAX COBOL and TCP/IP
    ... but the COBOL programmer does know how to do an interative read ... > don't necessarily know where a packet starts or ends, ... There have certainly been a great many record-oriented protocols ... applications using straight TCP have to do some sort of framing. ...
    (comp.lang.cobol)
  • FreeBSD Security Advisory FreeBSD-SA-01:39.tcp-isn
    ... TCP network connections use an initial sequence number as part of the ... incoming connection is being established, ... Systems running insecure protocols which blindly trust a TCP ... requiring other authentication of the originator are vulnerable to ...
    (FreeBSD-Security)
  • Re: Stand Alone DHCP Servers and Windows 2000
    ... On our network the clients are allowed to talk to the domain controller ... Kerberos-Sec (UDP) ... Microsoft CIFS (TCP) ... which segments and which computers use specific protocols. ...
    (microsoft.public.windows.server.networking)
Quantcast