如何访问另一台电脑的数据库？ （在任何地方）
好吧，我需要做2个应用程序，一个是用户自己注册（服务器在哪里），另一个是管理员可以看到谁注册了，但他没有时间去（服务器在哪里），所以他需要观看其他地方的信息，我无法做到这一点，我的另一个想法是使用网络服务，但我不知道如何在互联网上公开网络服务以供其他电脑使用，那么对于应用程序2，如何是连接字符串？我喜欢 ip，但是在 你的 ip 地址是什么 中，我看到 ip 是动态的，并且它会随着轮流变化在电脑上（服务器在哪里），那么我该怎么做呢？ （我无法与ip建立连接，也无法与计算机名称建立连接）
well I need to do 2 applications, one to users registers theirself (where the server is) and the another application is for the administrador can see who has register, but he doesn't have time to go (where the server is) so he need watch the information since other place, I haven't could do it, my another idea is using web services, but i dont know how to public the web service in internet for consum it since anothers pc's, then for application 2, how will be the connection string? i thoung with ip, but in what is your ip address i watched the ip is dinamic, and it change with turn on the computer (where is the server), then, how can i do it? (i coulnd't to have a connection with ip, and i couldn't with name of computer)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您的服务器必须保持可用，则必须以某种形式的主机名查找服务（例如 DNS）注册它们。大多数人通过维护企业内部网、使用托管服务为其数据库/应用程序提供服务或使用动态 DNS 服务（例如 DynDNS）来实现此目的。
如果这些信息仅供人类使用阅读：
您可以简单地创建此信息的共享源，例如内部 Wiki、Windows 网络共享上的 Excel 文档或 Microsoft Sharepoint 站点，并让用户向其写入新条目。管理员只需阅读该文档即可查找信息。这是更轻量级的，并且可以重复用于许多其他目的。
您可以安装和使用许多现有的免费 wiki/CMS 软件来实现此目的。
如果您需要其他程序（而不仅仅是人类读者）可以访问它：
您将必须创建某种数据库，并且可能需要创建一个网络服务来访问它。不幸的是，您需要更多信息才能为您提供满足这些需求的良好答案。任何答案都会做出很多假设，并且可能会让您在可扩展性、性能、安全性或可靠性方面处于不利地位。
一些帮助您入门的基本问题（当然不是完整列表） - 有多少用户？它们相对于您的服务器（您正在编写的此应用程序以及该应用程序似乎提供相关信息的服务器）将位于何处？信息必须有多安全？有多少数据？但即使有了这些数据，在不了解您的所有需求的情况下，也很难推荐任何类型的应用程序设计或网络拓扑。
如果您需要它可靠且安全（例如，您支持的不仅仅是您自己和几个用户），您可能需要将其变成一个严肃的项目，并投入业务研究、设计、开发和 IT 资源到它。这些资源都可以由一个人负责，但如果您不希望它成为一团难以维护、不安全的混乱，那么您确实应该完成所有动作。
If you have servers that must remain available, they must be registered in some form of hostname lookup service, such as DNS. Most people do this by maintaining a corporate intranet, using a hosting service to serve their database/application, or using a dynamic DNS service such as DynDNS.
If this information is just for humans to read:
You could simply create a shared source of this information, such as an internal Wiki, or an Excel document on a Windows network share, or Microsoft Sharepoint site, and let users write new entries to it. The admin would simply read that document to find out the information. This is much more light-weight, and could be reused for many other purposes.
There is a lot of existing free wiki/CMS software you could install and use for this purpose.
If you need this to be accessible by other programs, rather than just human readers:
You'll have to make some sort of database, and possibly a web service to access it. Unfortunately, you'll need a lot more information for anyone to give you a good answer for these needs. Any answer will make a lot of assumptions, and might put you in a bad spot in terms of scalability, performance, security, or reliability.
Some basic questions to get you started (certainly not a complete list) - How many users? Where will they be located with respect to your servers (both this application you are writing, and the servers that the application seems to provide information about)? How safe must the information be? How much data? But even with this data, it is hard to recommend any sort of application design or network topology without knowing all of your requirements.
If you need this to be reliable and secure (e.g. you're supporting more than just yourself and a couple users), you'll probably need to turn this into a serious project, and devote business research, design, development, and IT resources to it. These resources can all be one person, but you should really go through all the motions if you don't want it to be an unmaintainable, insecure mess.