无法本地或远程telnet sql端口1433

发布于 2024-11-05 07:39:30 字数 739 浏览 0 评论 0原文

我需要从 SQL Server 2008 连接到 SQL Server 2000。但我无法连接到它。 它说我的服务器名称或实例不正确。 错误消息:

Cannot connect to dpsobhanxxx-xxx.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

但是,当我在运行 SQL Server 2000 的计算机上运行 telnet 127.0.0.1 1433 时,它告诉我连接失败。 我在 Windows 服务中启动了 telnet。 当我运行 netstat -an 时,没有 1433 端口

我在 SQL Server 客户端网络实用程序中使用 1433 端口启用了 TCP/IP 端口。但不起作用。

I need to connect to a SQL server 2000 from SQL server 2008. but I can not connect to it.
It says me server name or instance are incorrect.
error message:

Cannot connect to dpsobhanxxx-xxx.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

however when I run telnet 127.0.0.1 1433 in the computer running SQL server 2000 it tells me connection failed.
I started telnet in windows services.
when I run netstat -an there is no 1433 port.

I enabled TCP/IP port in SQL server Client network utility with 1433 port. but doesn't work.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

夜司空 2024-11-12 07:39:30

检查两台计算机上以及它们之间的防火墙(如果有)。

如果此端口被阻止,您所看到的行为正是我所期望的。

Check your firewalls - on both computers and between them (if any).

If this port is blocked, the behavior you are seeing is exactly what I would expect.

硬不硬你别怂 2024-11-12 07:39:30

两天后我找到了解决方案,所以我将其分享在这里:
只需将 SQL Server 2000 升级到 SQL Server 2000 SP3

After two days I found the solution so I'll Share it here:
Just upgrade your SQL server 2000 to SQL server 2000 SP3

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文